Screenshots By Snapshot Site

Give your agent eyes: capture screenshots, detect visual changes between two page versions, and analyze pages with AI. Hosted, OAuth, free tier.

Official MCP server for the Snapshot Site API

These tools are annotated for MCP clients as:

They also include richer titles, category metadata, and example intents to improve tool selection in Claude Desktop and Cursor.

Local, with an API key— run the package yourself over stdio and provideSNAPSHOT_SITE_API_KEY. The server calls the Snapshot Site API directly.

Either way, calls count against the same plan quota as direct API calls. Nothing is metered differently because it came through MCP.

For local stdio mode you need a Snapshot Site API key.
-

Sign up for aSnapshot Site Consoleaccount.

Not sure which options to use? Preview a capture and its parameters in theScreenshotconsole playground before wiring them into a tool call.

1. Discovery Claude -> GET https://mcp.snapshot-site.com/.well-known/oauth-protected-resource MCP -> responds: authorization_servers = https://mcp.snapshot-site.com

2. Authorization Claude -> must know client_id -> opens: https://mcp.snapshot-site.com/oauth/v2/authorize ?client_id=... &redirect_uri=https://claude.ai/api/mcp/auth_callback &response_type=code &code_challenge=...

3. Token Claude -> receives an access token -> calls the MCP server: POST https://mcp.snapshot-site.com/ Authorization: Bearer <access_token>

curl -s https://mcp.snapshot-site.com/.well-known/oauth-protected-resource | jq curl -s https://mcp.snapshot-site.com/.well-known/openid-configuration | jq curl -i https://mcp.snapshot-site.com/ curl -i -X POST https://mcp.snapshot-site.com/mcp -H 'content-type: application/json' --data '{}'

export SNAPSHOT_SITE_API_KEY=ss_live_xxx export SNAPSHOT_SITE_BASE_URL=https://api.prod.ss.snapshot-site.com

export SNAPSHOT_SITE_API_KEY=ss_live_xxx snapshot-site-mcp

{ "mcpServers": { "snapshot-site": { "command": "node", "args": ["/absolute/path/to/snapshot-site-mcp/build/server.js"], "env": { "SNAPSHOT_SITE_API_KEY": "ss_live_xxx", "SNAPSHOT_SITE_BASE_URL": "https://api.prod.ss.snapshot-site.com" } } } }

{ "mcpServers": { "snapshot-site": { "command": "node", "args": ["/absolute/path/to/snapshot-site-mcp/build/server.js"], "env": { "SNAPSHOT_SITE_API_KEY": "ss_live_xxx" } } } }

This package also supports a hosted MCP endpoint for clients usingmcp-remote.

export PORT=3000 export HOST=0.0.0.0 export MCP_PATH=/mcp export HEALTH_PATH=/healthz export MCP_ALLOWED_HOSTS=mcp.snapshot-site.com export SNAPSHOT_SITE_BASE_URL=https://api.prod.ss.snapshot-site.com

Remote client configuration with direct API key header:

{ "mcpServers": { "Snapshot Site MCP": { "command": "npx", "args": [ "mcp-remote", "https://mcp.snapshot-site.com/mcp", "--header", "x-snapshotsiteapi-key: ss_live_xxx" ] } } }

The hosted server is stateless. Each request authenticates withx-snapshotsiteapi-key, which makes the service safe to run on multiple replicas without session affinity.

The remote HTTP server also supports OAuth bearer tokens validated against an OIDC issuer such as Zitadel.

export OIDC_ISSUER_URL=https://auth.snapshot-site.com export OIDC_AUDIENCE=snapshot-site-mcp export OIDC_REQUIRED_SCOPE=claudeai export OIDC_DISCOVERY_CLIENT_ID=366546620977775166 export RESOURCE_SERVER_URL=https://mcp.snapshot-site.com export ALLOW_API_KEY_AUTH=false export SNAPSHOT_SITE_API_KEY=ss_server_side_xxx

In bearer-token mode, the MCP server validates the incoming access token against the issuer JWKS and then uses the server-side Snapshot Site API key to call the backend API.

GET /.well-known/oauth-protected-resource GET /.well-known/openid-configuration GET/POST /oauth/v2/ GET /ui/ GET/POST /oauth/register

so MCP clients can discover the authorization server metadata automatically.

WhenOIDC_DISCOVERY_CLIENT_IDis set, the protected resource metadata also includes:

{ "resource_name": "Snapshot Site MCP", "preferred_client_id": "366546620977775166", "oauth_client_metadata": { "client_id": "366546620977775166", "token_endpoint_auth_method": "none" } }

This is an experimental compatibility hint for clients that can infer the OAuth public client automatically. Manualclient_identry remains the reliable fallback.

The MCP server also exposes a lightweightregistration_endpointcompatibility shim at:

POST https://mcp.snapshot-site.com/oauth/register

This shim currently returns the preconfigured public PKCE client instead of provisioning a brand-new Zitadel client per installation. It validates and reflects theredirect_urisrequested by the client, as long as they are valid HTTPS URLs. It is meant to improve compatibility with clients that expect DCR-style discovery, while keeping the existing manual flow as fallback.

Headless browser with SHA-256 hash-chained audit trails and Ed25519-signed proof bundles. MCP server for AI agents.

The 1Password MCP server creates a bridge that allows MCP clients such as Codex and Kiro to manage your 1Password Environments with secure authorization prompts.

Remote MCP server (streamable HTTP, OAuth 2.1) for AdMake AI. Generate Facebook, Instagram and TikTok ad creatives and UGC-style video ads, research competitor ads from the Meta Ad Library, and publish finished ads to Meta via the Marketing API. Connect at https://admakeai.com/api/mcp

ALTER - identity infrastructure for the AI economy

Salesforce integration using OAuth2. Write operations disabled by default per integration. 700+ tools covering SOQL, SOSL, REST, and CRUD, individually selectable. Requires a DataGrout account.

Model Context Protocol server for Skycloak managed Keycloak. Manage clusters, realms, applications, SSO and users from any MCP client.

Turns the Agent into a vLEI/KERI protocol expert

AI traffic control plane (chaos governor): Redis prompt replay, compliant web ingest, SSO org ledger, Agent Shell. BYOK OpenAI-compatible ingress. Cursor optional; MCP is a compatibility client.

Securely retrieve credentials from 1Password for use by Agentic AI.

Agent-native forum for the x402/A2A ecosystem. The hosted MCP server exposes the whole forum as tools — threads, comments, votes, USDC bounties (Coinbase x402 on Base), provider reviews, and search. Endpoint: https://api.achivx.com/mcp/ (HTTP, OAuth 2.1).