screenshots-snapshot-site

Name: screenshots-snapshot-site
Author: snapshot-site

Official

by snapshot-site

Overview Schema Source Related Servers Score Discussions Admin

TypeScript

Hybrid

Snapshot Site MCP

npm Node License

Official MCP server for the Snapshot Site API

Tools

screenshot
analyze
compare

These tools are annotated for MCP clients as:

read-only
idempotent
open-world

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

Related MCP server: PagePixels Screenshots MCP Server

Two ways to connect

Hosted, with OAuth — point your client at https://mcp.snapshot-site.com/mcp and sign in. There is no local process to run and no API key in your client config; the server resolves your account from the OAuth session.

Local, with an API key — run the package yourself over stdio and provide SNAPSHOT_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.

Credentials

The hosted server needs no credential — you sign in through OAuth and the server resolves your account from the session. Skip this section unless you run the server yourself over stdio.

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

Sign up for a Snapshot Site Console account.
Create an API key on the API Keys page.
Pass the key to the server as the SNAPSHOT_SITE_API_KEY environment variable.
Leave SNAPSHOT_SITE_BASE_URL at its default (https://api.prod.ss.snapshot-site.com) unless you're pointed at a self-hosted or staging instance.

Compatibility

Requires Node.js 20.9 or later. Built against @modelcontextprotocol/sdk v1.28 and tested with Claude Desktop and Cursor over stdio, and with any client that speaks the streamable HTTP transport against the hosted endpoint.

Usage

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

Snapshot Site Console — Screenshot playground

OAuth discovery flow

What a client does when connecting to the hosted server:

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>

The server then validates the token against the issuer and resolves the account it belongs to before running the tool.

Verifying the deployment

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 '{}'

Manual vs implicit client_id

The client_id is only needed for the authorization step.
If your client cannot discover that client_id beforehand, enter it manually in the connector UI.
It cannot be injected later once the OAuth flow has started.
The server can publish an experimental implicit mode by exposing a preferred_client_id in /.well-known/oauth-protected-resource.
Clients that read this metadata may then skip the manual entry. Clients that ignore the field still require a manual client_id.

Environment

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

Build

pnpm install
pnpm run build

Local stdio mode

export SNAPSHOT_SITE_API_KEY=ss_live_xxx
snapshot-site-mcp

Claude Desktop configuration

{
  "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"
      }
    }
  }
}

Cursor configuration

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

Remote HTTP mode

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

Start the HTTP server:

pnpm start:http

or:

npx snapshot-site-mcp-http

Environment variables:

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 with x-snapshotsiteapi-key, which makes the service safe to run on multiple replicas without session affinity.

Zitadel / OAuth

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

Environment variables:

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.

It also exposes and proxies:

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.

When OIDC_DISCOVERY_CLIENT_ID is 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. Manual client_id entry remains the reliable fallback.

The MCP server also exposes a lightweight registration_endpoint compatibility 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 the redirect_uris requested 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.

Available Tools

3 tools

analyzeAnalyze WebpageA

Read-onlyIdempotent

Inspect

Capture and analyze a webpage with Snapshot Site. Useful for content summaries, SEO metadata inspection, headings extraction, and quality signals such as blank pages or captcha detection.

ParametersJSON Schema

Name	Required	Description	Default
`url`	Yes
`hide`	No
`delay`	No
`width`	No
`format`	No
`height`	No
`fullSize`	No
`language`	No
`hideCookie`	No
`waitForDom`	No
`forceRefresh`	No
`enableQuality`	No
`enableSummary`	No
`javascriptCode`	No

TDQS

A3.5/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, covering the safety profile. The description adds behavioral context like captcha detection and blank-page signals but does not disclose execution-related behaviors (e.g., javascriptCode execution) or output details. This adds some value without contradicting annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description consists of two concise, front-loaded sentences that convey the purpose and use cases without redundancy. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having 14 parameters and no output schema, the description remains at a high level, omitting essential details about parameter behavior, required inputs beyond URL, and return values. This is insufficient for correctly invoking the tool in varied scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain any of the 14 parameters. It only mentions high-level use cases without mapping them to parameters like enableSummary, enableQuality, or format. This leaves agents without crucial parameter-level guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool captures and analyzes a webpage, with specific use cases (content summaries, SEO metadata, headings, quality signals). This distinguishes it from sibling tools like screenshot and compare, which likely focus on different operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool (summaries, SEO inspection, headings extraction, quality detection) but does not explicitly mention when not to use it or compare it with alternatives. The context is sufficient for basic selection guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

compareCompare Page StatesA

Read-onlyIdempotent

Inspect

Compare two live webpage states or two PNG captures and return before, after, diff, plus mismatch metrics. Useful for QA, release review, and visual regression workflows.

ParametersJSON Schema

Name	Required	Description	Default
`after`	Yes
`before`	Yes
`threshold`	No

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint, openWorldHint, and idempotentHint. The description adds value by explaining that it accepts live webpage states or PNG captures and returns before/after/diff/metrics, which is not covered by annotations. No contradiction is present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is exactly two sentences, front-loaded with the core purpose and followed by use cases. Every word contributes, with no repetition or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite the nested object complexity and lack of output schema, the description covers the main function and return value structure. Strong annotations compensate for safety, but the description would benefit from explaining threshold and capture sub-properties to be fully self-sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It clarifies that 'before' and 'after' can be either live URLs or PNG captures, but it does not explain the 'threshold' parameter or the many sub-properties like hide, delay, width, etc., leaving gaps in understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states 'Compare two live webpage states or two PNG captures and return before, after, diff, plus mismatch metrics.' This clearly identifies the verb (compare), the resource (two webpage states or PNG captures), and the outputs, distinguishing it from sibling tools like 'screenshot' and 'analyze'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says 'Useful for QA, release review, and visual regression workflows,' which provides clear contexts for when to use the tool. However, it does not explicitly mention when not to use it or contrast it with alternatives, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

screenshotCapture ScreenshotA

Read-onlyIdempotent

Inspect

Capture a live webpage with Snapshot Site. Use this for screenshots, PDFs, HTML capture, device-sized renders, cookie hiding, custom JS injection, and export retrieval.

ParametersJSON Schema

Name	Required	Description	Default
`url`	Yes
`hide`	No
`delay`	No
`width`	No
`format`	No
`height`	No
`convert`	No
`country`	No
`fullSize`	No
`language`	No
`hideCookie`	No
`javascriptCode`	No

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate read-only, idempotent, and open-world behavior. The description adds useful behavior context like 'live webpage', 'cookie hiding', and 'custom JS injection' without contradicting annotations. It does not detail all edge cases, but the annotations cover the core safety profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, tightly packed sentence that front-loads the primary action and then lists supported features. Every word adds value, with no redundant filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description gives a broad overview of tool capabilities and pairs with a rich input schema, but it does not explain ambiguous parameters or output retrieval behavior. For a 12-parameter tool with no output schema, this is adequate for selection but not fully sufficient for correct invocation without additional inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description's list of capabilities (e.g., 'device-sized renders', 'cookie hiding', 'HTML capture') indirectly maps to parameters like width/height, hideCookie, and format. However, many parameters (hide, delay, convert, country, language, fullSize) remain ambiguous and uncompensated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool captures a live webpage and lists specific use cases (screenshots, PDFs, HTML capture, etc.). It does not explicitly distinguish from sibling tools 'analyze' and 'compare', but the capture focus is apparent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit use-case guidance with 'Use this for...' and enumerates supported output types and features. It does not mention exclusions or alternative tools, but the context is clear for selecting this tool for capture tasks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

3 tool updatesv1.0.0Jul 31, 2026
- First observedanalyze
- First observedcompare
- First observedscreenshot

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0

Scored 2026-07-31 08:00 across 3 tools

Disambiguation4/5

The three tools have distinct core purposes (capture, analyze, compare), but 'screenshot' and 'analyze' both involve capturing a live webpage, which could cause confusion. Descriptions provide enough clarity, but the overlap is noticeable.

Naming Consistency5/5

All tool names are single-word verbs—screenshot, analyze, compare—following a consistent and predictable pattern. There is no mixing of conventions or vague naming.

Tool Count5/5

With 3 tools, the server is well-scoped for its purpose of capturing, analyzing, and comparing webpages. Each tool occupies a distinct role, and the count is within the ideal 3–15 range.

Completeness4/5

The tool set covers the primary workflows: capture (screenshot), analysis (analyze), and comparison (compare). Minor gaps exist, such as no explicit snapshot management or status listing, but these are not critical for the core functionality.

Maintenance

ActivitySlowing

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Related MCP Connectors

snapforge A
org.snapforge
Screenshots, PDFs and Markdown from any URL or HTML for AI agents, via the SnapForge API
Browser Automation Web Scraping
42
snaplab
dev.snaplab
Screenshot, PDF and HTML-to-image rendering API so Claude and Cursor can see any web page.
Browser Automation Image & Video Processing
1
snaplab
app.hsingh.snaplab
Screenshot, PDF and HTML-to-image rendering API so Claude and Cursor can see any web page.
Image & Video Processing Browser Automation
1
render-mcp A
io.github.RodRomer
Hosted browser for AI agents: screenshots, post-JS DOM, console, WCAG. No install, no API key.
Browser Automation Testing & QA Tools
61

Related MCP Servers

mcp-server-npm-plus
Developer Tools Search Code Analysis
ofershap
A
license
B
quality
D
maintenance
MCP server for npm — search packages, check bundle sizes, scan vulnerabilities, compare downloads, inspect dependencies.
Updated 6 months ago (2026-03-10 09:22 UTC)
8
56
1
MIT
PagePixels Screenshots MCPofficial
Browser Automation Web Scraping Monitoring
PagePixels
A
license
Not graded
quality
D
maintenance
Enables AI assistants to capture website screenshots, automate browser interactions, and manage recurring screenshot configurations across 150+ global locations. It also supports AI-powered domain research and visual change monitoring for any web page.
Updated 4 months ago (2026-05-02 03:17 UTC)
17
MIT
rendex-mcp
Browser Automation Web Scraping Image & Video Processing
copperline-labs
A
license
A
quality
B
maintenance
Capture screenshots, generate PDFs, and render HTML to images via AI agents. Supports batch capture, geo-targeting, async webhooks, and CSS/JS injection.
Updated a month ago (2026-08-14 00:27 UTC)
11
73
7
MIT
Claude Google Sheets MCP
Workplace & Productivity App Automation
ringo380
A
license
Not graded
quality
F
maintenance
A comprehensive MCP server for Google Sheets integration with Claude, enabling spreadsheet discovery, data manipulation, and formatting through natural language commands and slash commands.
Updated a year ago (2025-09-27 02:33 UTC)
19
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/snapshot-site/snapshot-site-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

Snapshot Site MCP

Tools

Two ways to connect

Credentials

Compatibility

Usage

OAuth discovery flow

Verifying the deployment

Manual vs implicit client_id

Environment

Build

Local stdio mode

Claude Desktop configuration

Cursor configuration

Remote HTTP mode

Zitadel / OAuth

Available Tools

TDQS

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

mcp-server-npm-plus

PagePixels Screenshots MCPofficial

rendex-mcp

Claude Google Sheets MCP

Latest Blog Posts

MCP directory API