Use Screenshot.fyi from Claude
Add the Screenshot.fyi connection to a Space that runs Claude, then use it from every channel in that Space.
ConnectorScreenshot.fyi
Screenshot.fyi integration for Claude and Codex
Connect Screenshot.fyi once, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
CategoryDeveloper Tools & IT
Use Screenshot.fyi from Codex
Add the Screenshot.fyi connection to a Space that runs Codex, then use it from every channel in that Space.
Use Screenshot.fyi from Sidekick
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
Developer Tools & IT
What the Screenshot.fyi connector can do
Screenshot.fyi turns a URL into a rendered image with a single API call, handling the browser and viewport so a team does not have to run one. In type.com, an agent with a Screenshot.fyi connection can capture a page on request and share the image directly in the thread for design review, QA, or a quick visual check.
One connection, many Spaces
Connect Screenshot.fyi once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Use Screenshot.fyi from Claude Code, Codex, and automations
Use Screenshot.fyi from Claude Code or Codex
Once Screenshot.fyi is connected in type.com, install the type.com CLI, and Claude Code or Codex can call its tools with type-cli integrations call. Calls run with your type.com access, and the credentials stay on type.com's servers.
Automate Screenshot.fyi on a schedule or webhook
In a Space with Screenshot.fyi connected, describe the job, and type.com proposes an automation with its trigger, schedule, and destination. Runs can start on a schedule or from a webhook, Slack, GitHub, Linear, email, or RSS, and each run leaves a thread the team can read.
What teams do with Screenshot.fyi in type.com
Capture a page for design review
Ask the agent to screenshot a live page before a review call, so the team can compare it against the design without opening a browser.
Take a screenshot of our pricing page with Screenshot.fyi and drop it in this thread.
Archive a page before changes ship
Grab a visual record of a page right before a deploy, so there is a before-and-after reference if something looks off.
Use Screenshot.fyi to capture the current homepage before we push today's changes.
Check a competitor page visually
Instead of describing what a competitor's landing page looks like, have the agent capture it so the team can see the real layout.
Screenshot this competitor's signup page with Screenshot.fyi so we can see their current flow.
Representative actions
- Take Screenshot
Captures an image of a given URL, with the target page and viewport options supplied when the agent calls it.
Connection
API and auth details
Screenshot.fyi provides a screenshot API for capturing high-quality website images. Public endpoint-level documentation is limited, so integrations should describe URL screenshot capture, viewport and rendering options, automation for previews, archives, QA, social cards, and marketing assets conservatively.
- Source
- type.com catalog metadata
- Auth schemes
- API key
- API docs
- https://screenshot.fyi/
- Official site
- https://screenshot.fyi/
FAQ
Questions people ask before connecting Screenshot.fyi
Can Claude take screenshots of web pages through Screenshot.fyi?
Yes. With a Screenshot.fyi connection shared to a Space, ask the agent to capture any URL and it returns the image in the thread for the team to view.
How does Screenshot.fyi authenticate in type.com?
Screenshot.fyi uses an API key, added once when an admin sets up the connection. Spaces that need it are granted access without anyone handling the key directly.
Can Screenshot.fyi captures run on a schedule?
Yes. Set up a type.com automation that captures a page daily or weekly, such as a homepage check, and the agent posts the image to a channel each time.
Can Claude Code or Codex use Screenshot.fyi?
Yes. Once Screenshot.fyi is connected in type.com, install the type.com CLI, and Claude Code or Codex can call its tools with type-cli integrations call. Calls run with your type.com access, and the credentials stay on type.com's servers.
Can I automate Screenshot.fyi on a schedule?
Yes. In a Space with Screenshot.fyi connected, describe the job, and type.com proposes an automation with its trigger, schedule, and destination. Runs can start on a schedule or from a webhook, Slack, GitHub, Linear, email, or RSS, and each run leaves a thread the team can read.
Is this the same as an MCP server for Screenshot.fyi?
Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
More developer tools & it connectors
All Developer Tools & IT integrationsConnect Mailtrap to Claude in type.com to clean test inboxes, manage contacts, and export contact data from a thread.
Connect Mapbox to Claude in type.com to batch geocode addresses, look up single places, and run permanent geocodes for stored records.
Connect Mapulus to Claude in type.com to find locations, review maps, and check map details in a shared thread.
Connect Marketstack to Claude in type.com to pull stock prices, dividends, and exchange data in a shared thread.