Hosted OAuth
ChatGPT
Add Snapshot Site as a custom MCP connector and sign in when prompted. This is the easiest way to use hosted tools directly inside ChatGPT.
https://mcp.snapshot-site.com/mcp
Hosted MCPGet started for free
Connect Snapshot Site to Claude Code, Cursor, Codex, Kiro, ChatGPT, and MCP-native assistants
Use Snapshot Site directly from Claude Code, Cursor, Codex, Kiro, ChatGPT, and compatible MCP clients to capture screenshots, compare pages, and analyze visual changes without building a custom integration.
3 tools
Screenshot, analyze, compare
Hosted OAuth
Claude Code, Cursor, Codex, Kiro, ChatGPT ready
Account-based access
Uses your Snapshot Site account
MCP URL:
https://mcp.snapshot-site.com/mcpListed in the official MCP Registry:
com.snapshot-site/screenshotsDiscover
Protected resource
Authorize
Hosted OAuth
Execute
Product API
MCP overview
Snapshot Site MCP gives AI assistants a simple way to use Snapshot Site actions through a hosted connection. You sign in with your account, approve access, and your assistant can then use the available tools inside its normal workflow.
1
Connect once and use Snapshot Site inside supported assistants
2
Sign in with your existing Snapshot Site account
3
Keep screenshot, compare, and analysis workflows in one place
4
Use hosted access instead of managing a local wrapper
5
Stay aligned with your existing account permissions and usage
How it works
The hosted flow is designed to feel simple.
1
Add Snapshot Site to your assistant
Use the hosted MCP URL in Claude Code, Cursor, Codex, Kiro, ChatGPT, or another compatible MCP client.
2
Sign in and approve access
Authenticate with Snapshot Site when prompted so the assistant can act on your behalf.
3
Call Snapshot Site tools
Ask your assistant to capture screenshots, compare versions, or analyze visual output.
4
Receive results in context
The assistant gets structured results it can use in follow-up tasks, summaries, and workflows.
Connect to Snapshot Site MCP
Hosted OAuth
Claude Code
Use the hosted MCP URL in Claude and complete the sign-in flow to connect your Snapshot Site account.
https://mcp.snapshot-site.com/mcp
API key
Local stdio
Run the package locally if you prefer a developer-oriented setup with an API key and a local MCP process.
npx -y @snapshot-site/mcp
Header auth
Hosted HTTP client
Use the hosted endpoint directly if your MCP client supports HTTP connections with custom headers.
{
"type": "http",
"url": "https://mcp.snapshot-site.com/mcp",
"headers": {
"x-snapshotsiteapi-key": "ss_live_xxx"
}
}Works with your account
Hosted MCP access is connected to the Snapshot Site account you use during sign-in.
Uses normal product limits
Usage through MCP follows the same account access and quota rules as the rest of Snapshot Site.
Good for assistants and workflows
Hosted MCP is ideal when you want assistants to call Snapshot Site directly without building a custom integration.
API and SDKs still remain available
If you prefer direct programmatic control, you can still use the API, SDKs, or CLI alongside MCP.
Screenshot API MCP FAQ
What is the Snapshot Site MCP server?
It exposes Snapshot Site screenshot, rendered-page analysis, and visual comparison capabilities as tools that compatible MCP clients can discover and call.
Which MCP connection should I choose?
Use the hosted OAuth endpoint when your client supports that flow. Use local stdio with an API key when you need a developer-controlled local process.
Does MCP bypass Snapshot Site account limits?
No. Tool use follows the access, quota, and product rules associated with the authenticated Snapshot Site account.
Should an assistant receive my API key in a prompt?
No. Configure credentials through the client connection or protected local environment. Do not paste secrets into conversation text, project instructions, or tool arguments.
Can MCP automate a login-protected site?
The tools are output-oriented and do not provide an interactive persistent browser session. Use an authorized reachable preview or a browser automation workflow for multi-step login.
What should an assistant include in a capture request?
Give it an authorized target, the intended viewport and output, and enough readiness context to define the page state. Avoid unnecessary private data.
How should generated artifacts be handled?
Treat screenshots and analysis as application data. Apply access, retention, and sharing controls that match the source content.
When is the REST API a better choice than MCP?
Use REST or an SDK for deterministic application code, queues, strong typing, and direct operational control. MCP is useful when an assistant is the workflow entry point.