Screenshot.fyi
Take stunning, premium quality screenshots of any website with one API call.
Verdict
Common use cases
- Archive homepage design before each deploy
- Document UI bugs with timestamped screenshots
- Compare landing page versions across sprints
- Capture competitor sites for design research
- Log visual regressions during QA reviews
Integration
- Vendor
- Screenshot.fyi
- Category
- developer-tools
- Auth
- API_KEY
- Composio slug
screenshot_fyi
Tools
Setup
Setup guide
- 11. Open your Switchy workspace settings and navigate to the MCP Integrations panel. 2. Search for Screenshot.fyi and click Connect. 3. You'll be prompted to paste an API key — generate one from your Screenshot.fyi dashboard under API Settings. 4. Copy the key and paste it into Switchy, then click Authorize. 5. Switchy confirms the connection and lists available tools (capture, retrieve, compare). 6. Open any Space, type @Screenshot.fyi followed by a URL, and ask it to capture a screenshot. 7. The MCP returns a stored image link within seconds — verify you see the thumbnail inline to confirm the integration works.
What teammates see: by default, memories from Screenshot.fyi 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
Starter prompts
Capture Current Homepage
@Screenshot.fyi capture a screenshot of https://example.com and label it 'Homepage - Jan 2025'.Open in a Space →
Compare Two Page Versions
@Screenshot.fyi compare the screenshot from December 15 with today's capture of https://example.com/pricing.Open in a Space →
Document Bug Visually
@Screenshot.fyi take a screenshot of https://app.example.com/dashboard showing the layout bug on mobile viewport.Open in a Space →
Archive Competitor Landing Page
@Screenshot.fyi capture https://competitor.com and save it to the 'Design Research' folder.Open in a Space →
Retrieve Past Screenshot
@Screenshot.fyi retrieve the screenshot labeled 'Checkout Flow - Sprint 12' from last month.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Screenshot.fyi capture the staging environment at https://staging.acme.io/dashboard and save it to our design review folder
Screenshot captured and saved. The staging dashboard shows the new navigation layout with the updated color scheme. Image stored at screenshot.fyi/acme/staging-dashboard-2024-01-15.png (1920×1080). The page loaded in 2.3s; all assets rendered successfully. You can view or share the screenshot directly from the link.
This example shows the core capture workflow. Screenshot.fyi requires the target URL to be publicly accessible or behind auth that the service can reach. If your staging environment is IP-restricted, you'll need to allowlist Screenshot.fyi's capture servers or use a different approach.
@Screenshot.fyi compare the homepage design from last week to today's production version and highlight any visual differences
Comparison complete. Two changes detected: (1) Hero section CTA button changed from blue (#2563EB) to green (#10B981). (2) Footer layout shifted from three-column to four-column grid. Side-by-side diff image generated at screenshot.fyi/acme/homepage-diff-jan15.png. No layout shifts or broken images found in either version.
Visual regression detection is useful for catching unintended UI changes during deployment. This example assumes Screenshot.fyi has historical snapshots stored; if you haven't captured the 'before' state previously, the comparison won't work. The service identifies pixel-level differences but won't interpret design intent.
@Screenshot.fyi take screenshots of our checkout flow across Chrome, Firefox, and Safari on desktop, then summarize any rendering inconsistencies
Cross-browser captures complete. Chrome and Firefox render identically. Safari (macOS 14) shows two issues: (1) Payment form input borders appear 1px thicker due to default -webkit-appearance styling. (2) Submit button font renders slightly bolder (system font fallback difference). Screenshots saved to screenshot.fyi/acme/checkout-xbrowser/. No functional blockers detected, but the Safari button styling may warrant a CSS adjustment for brand consistency.
Multi-browser testing helps catch browser-specific CSS or JavaScript issues before users report them. This example requires Screenshot.fyi to support multiple rendering engines; verify your plan includes cross-browser capture. The AI's 'summary' here interprets visual data the service returns — actual output format depends on how Screenshot.fyi structures its response.
Use-case deep-dives
When Screenshot.fyi closes the loop on visual bug reports
A 5-person product team gets 20 bug reports a week from QA and customers. Half arrive as vague descriptions ('the button looks weird') with no screenshot. Screenshot.fyi lets the team capture, annotate, and attach visual context directly in Switchy threads without leaving the workspace. The MCP handles upload and retrieval through API key auth, so anyone can pull the latest screenshot into a conversation. This works best when your team already uses Screenshot.fyi for internal tooling and wants to centralize bug discussion in Switchy. If your team doesn't have a Screenshot.fyi account or prefers Slack-native screenshots, skip this and use built-in file uploads. For teams that live in Screenshot.fyi, this MCP turns visual bug triage into a one-click workflow.
Screenshot.fyi for async design feedback loops
A 3-person design team ships Figma mockups to engineering twice a week. Engineers need annotated screenshots to understand spacing, hover states, and edge cases that don't translate in static frames. Screenshot.fyi lets designers capture annotated views and reference them in Switchy threads during handoff. The MCP pulls those screenshots into the conversation so engineers can ask clarifying questions without switching tools. This scenario assumes your designers already use Screenshot.fyi for annotation and your team prefers async handoff over live meetings. If your team does synchronous design reviews or uses Figma comments exclusively, this MCP adds friction instead of removing it. For teams that document design decisions in screenshots, this MCP keeps handoff context in one place.
When Screenshot.fyi speeds up support-to-engineering escalation
A 6-person support team escalates 10 tickets a week to engineering. Customers send screenshots of errors, broken layouts, or unexpected behavior. Screenshot.fyi lets support reps upload and tag those screenshots, then reference them in Switchy threads when escalating to engineers. The MCP retrieves the tagged screenshots so engineers see exactly what the customer saw without digging through email attachments or Zendesk threads. This works when your support team already uses Screenshot.fyi for ticket management and your engineers work in Switchy. If your support team uses a different screenshot tool or your engineers prefer to stay in the ticketing system, this MCP is overkill. For teams that escalate visual issues frequently, this MCP cuts the back-and-forth by half.
Frequently asked
What does the Screenshot.fyi MCP do in Switchy?
It lets your AI agents capture screenshots of websites and web apps on demand. Instead of manually taking screenshots or writing Puppeteer scripts, your team can ask an agent to grab a visual snapshot of any URL. Useful for design reviews, bug reports, or archiving UI states before deployments.
Do I need a Screenshot.fyi account to use this MCP?
Yes. You'll need an active Screenshot.fyi account and an API key. Paste the key into Switchy's connection settings. The MCP authenticates each screenshot request with that key, so make sure it has sufficient quota for your team's usage.
Can it capture screenshots of pages behind a login?
Not directly. Screenshot.fyi renders public URLs in a headless browser. If your page requires authentication, you'll need to generate a temporary shareable link or use a staging environment with auth disabled. The MCP can't pass session cookies or login credentials.
How is this different from using Screenshot.fyi's dashboard?
The dashboard is manual — you paste a URL, click a button, wait. The MCP embeds screenshot capture into your agent workflows. An agent can take a screenshot mid-conversation, compare two versions of a page, or batch-capture a list of URLs without you leaving Switchy.
Does screenshot usage count against my Switchy plan limits?
No. Screenshot.fyi bills separately based on your account tier with them. Switchy doesn't meter or charge for MCP tool calls. If you hit Screenshot.fyi's quota, the MCP will return an error and your agent will tell you to upgrade your Screenshot.fyi plan.