developer-toolsapi_key

Apiflash

ApiFlash is a website screenshot API that allows users to capture high-quality screenshots of web pages programmatically.

Verdict

Apiflash captures website screenshots programmatically — full pages, specific viewports, or batch jobs. @mention it in a Space to grab visual snapshots of URLs without leaving the conversation. Designers verify responsive layouts, QA teams document bugs with pixel-perfect context, and marketers archive campaign landing pages before they change. The MCP exposes four tools: single screenshot (POST for form data), batch capture for multiple URLs at once, quota checks to avoid rate limits, and metadata retrieval for dimensions and file size. You'll need an API key from Apiflash's dashboard; free tiers exist but batch jobs and high-resolution captures burn quota quickly.

Common use cases

  • Document UI bugs with full-page screenshots
  • Archive marketing pages before campaign ends
  • Verify responsive design across viewport sizes
  • Capture competitor landing pages for analysis
  • Generate visual reports from URL lists

Integration

Vendor
Apiflash
Category
developer-tools
Auth
API_KEY
Tools
4
Composio slug
apiflash

Tools

  • Batch Capture Screenshots

    Tool to capture screenshots for multiple urls in a single request. use when you have a list of pages to snapshot in batch.

  • Capture Website Screenshot (POST)

    Tool to capture a screenshot of a website via http post. use when you need to post form data parameters.

  • Get Quota Information

    Tool to retrieve current api quota usage and limits. use after authentication to monitor usage and reset times.

  • Get Screenshot Metadata

    Tool to retrieve metadata for a previously captured screenshot. use when you need details like file size and dimensions after capture.

Setup

Setup guide

  1. 11. Open your Switchy workspace and navigate to Settings > Integrations > Browse MCP Servers. 2. Search for Apiflash and click Connect. 3. You'll be prompted to paste an API key — log into your Apiflash account at apiflash.com, go to the API Keys section of your dashboard, and copy the key shown there. 4. Paste the key into Switchy's prompt and click Authorize. 5. Switchy confirms the connection and displays your current quota limits. 6. Open any Space, type '@Apiflash check my quota' and send — if you see usage stats in the reply, the integration works. 7. To capture your first screenshot, try '@Apiflash grab a screenshot of https://example.com' and watch the image appear in the thread. 8. For batch jobs or POST requests with form data, reference the tool names directly in your prompt.

What teammates see: by default, memories from Apiflash are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

Check Quota Usage

@Apiflash show me my current quota usage and when it resets
Open in a Space →

Single Page Snapshot

@Apiflash capture a screenshot of https://news.ycombinator.com at 1920x1080 resolution
Open in a Space →

Batch Competitor Pages

@Apiflash capture screenshots for these URLs in batch: https://stripe.com, https://square.com, https://paypal.com
Open in a Space →

Mobile Viewport Test

@Apiflash screenshot https://myapp.dev/checkout at 375x667 mobile viewport
Open in a Space →

Retrieve Screenshot Metadata

@Apiflash get metadata for the screenshot I just captured of example.com
Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@Apiflash capture screenshots of our homepage, pricing page, and docs landing page at 1920x1080 resolution

Output

I've queued batch screenshot captures for all three URLs at 1920x1080. The API returned job IDs for each request. Typically these complete within 10-15 seconds depending on page load times. Once processed, you'll have PNG files showing exactly how each page renders in a standard desktop viewport. I can retrieve the final image URLs or metadata once the captures finish.

Notes

Batch capture is ideal for auditing multiple pages at once (design reviews, QA checks). Requires an API key with sufficient quota. Each URL counts toward your monthly screenshot limit, so check quota first if you're running large batches regularly.

Prompt

@Apiflash check my current quota usage and let me know how many screenshots I have left this month

Output

Your Apiflash account shows 847 screenshots used out of 5,000 in the current billing cycle, which resets on March 1st. That leaves 4,153 captures available. Your plan also includes 10 GB of storage, with 2.3 GB currently used. Based on this usage rate, you're on track to stay well within limits for the month.

Notes

Quota checks are read-only and don't consume API credits. Useful before running large batch jobs to avoid mid-workflow failures. The reset date depends on your billing cycle, so factor that into planning if you're near the limit.

Prompt

@Apiflash grab a screenshot of example.com with a mobile viewport and dark mode enabled, then tell me the file size

Output

I've captured example.com using a 375x667 mobile viewport with dark mode CSS media query applied. The screenshot completed successfully. Retrieving metadata now: the final PNG is 184 KB, dimensions are 375x667 as requested, and the capture timestamp is 2025-01-15T18:42:33Z. The image URL is available for 30 days under your account's storage policy.

Notes

This example chains two tools: first the POST capture (with viewport and CSS parameters), then metadata retrieval. Useful for responsive design testing or accessibility audits. The 30-day storage window means you should download or archive screenshots you need long-term.

Use-case deep-dives

QA visual regression testing

When Apiflash beats headless browsers for small-team QA

A 3-person dev team shipping a marketing site twice a week needs visual regression checks but doesn't want to maintain Playwright infrastructure. Apiflash wins here because the Batch Capture Screenshots tool handles 10-20 URLs in one call, the quota endpoint keeps you under API limits, and you skip the Docker container mess. The trade-off: if you need to test authenticated flows or click through modals, Apiflash can't do it—screenshots are static page loads only. If your QA is mostly public landing pages and you're under 500 captures a month, this MCP turns visual checks into a 5-minute Switchy workflow instead of a CI pipeline project.

Client design approval snapshots

Fast screenshot delivery for agency feedback loops

A 6-person design agency presents staging sites to clients every Friday and needs timestamped snapshots for each review round. Apiflash's POST endpoint lets you pass viewport sizes and custom CSS to match client device specs, and the metadata tool confirms file dimensions before you drop screenshots into Figma or Notion. The limitation: if clients want to see hover states or scroll interactions, you're back to Loom. But for static page approvals across 3-5 breakpoints, this MCP cuts screenshot prep from 20 minutes of manual browser resizing to a single Switchy prompt. Best fit when you're billing hourly and screenshot time is pure overhead.

Competitor landing page monitoring

When batch capture beats manual competitor research

A solo product marketer tracks 15 competitor homepages monthly to spot messaging shifts and new feature launches. Apiflash's batch tool snapshots all 15 URLs in one request, and the quota check keeps you from burning through your plan mid-month. The catch: if competitors gate their best content behind login walls, Apiflash only sees the logged-out view. This MCP is the right call when you're monitoring public-facing pages and your research cadence is weekly or monthly—anything more frequent and you'll want a dedicated monitoring tool with diff alerts. For ad-hoc competitive audits in Switchy, it's faster than opening 15 tabs and screenshotting by hand.

Frequently asked

What does the Apiflash MCP do in Switchy?

It lets your team capture website screenshots programmatically through Switchy's AI workspace. You can snapshot single pages, batch-process multiple URLs at once, and retrieve metadata like file size and dimensions. Useful for design reviews, QA workflows, or archiving page states without manual browser work.

Do I need an Apiflash account to use this MCP?

Yes. You'll need an Apiflash API key, which means signing up for their service and choosing a plan. Switchy authenticates via API_KEY — paste your key into the connection settings. No OAuth dance, but you're subject to Apiflash's quota limits based on your plan tier.

Can the Apiflash MCP capture screenshots of password-protected pages?

Only if you use the POST method tool and send form credentials as parameters. The MCP itself doesn't handle session cookies or OAuth logins to third-party sites. For pages behind complex auth, you'll need to handle login separately or use Apiflash's custom headers feature if your plan supports it.

Why use this MCP instead of Apiflash's API directly?

The MCP wraps Apiflash's API so your team can trigger screenshots through natural language in Switchy, without writing curl commands or managing API keys per person. You also get quota monitoring built in. If you're already scripting against Apiflash elsewhere, the direct API gives you more control over advanced parameters.

Who on the team should connect the Apiflash MCP?

Whoever owns your Apiflash account and API key. That person's quota applies to all screenshots taken through Switchy. If multiple people need screenshot access, consider a shared service account or upgrade your Apiflash plan to avoid hitting limits mid-sprint.

Data last verified 607 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.