Skip to main content
Glama
deenesjakoruzh
site-shot

site-shot-mcp

Official
by site-shot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Site-Shot MCP server

Geben Sie Claude, Cursor und anderen KI-Agenten die Fähigkeit, jede Webseite zu sehen — machen Sie Website-Screenshots mit Site-Shot über das Model Context Protocol.

Echtes Chromium-Rendering · Ganzseiten-Erfassung · Länder-Proxys · automatische Entfernung von Werbung & Cookie-Bannern (sauberere Bilder, weniger Vision-Tokens).

Schnellstart (Claude Desktop)

  1. Holen Sie sich einen Site-Shot-API-Schlüssel unter https://www.site-shot.com/start/.

  2. Fügen Sie dies zu Ihrer Claude-Desktop-Konfiguration hinzu (claude_desktop_config.json):

{
  "mcpServers": {
    "site-shot": {
      "command": "npx",
      "args": ["-y", "site-shot-mcp"],
      "env": { "SITESHOT_API_KEY": "YOUR_API_KEY" }
    }
  }
}

  1. Starten Sie Claude Desktop neu. Bitten Sie es, "einen Ganzseiten-Screenshot von https://news.ycombinator.com zu machen", und es wird den Server aufrufen und Ihnen das Bild zeigen.

Funktioniert auf die gleiche Weise in jedem MCP-Client (Cursor, Cline, VS Code, LangChain, CrewAI) — weisen Sie den Client auf npx -y site-shot-mcp mit SITESHOT_API_KEY in der Umgebung hin.

Related MCP server: Webpage Screenshot MCP Server

Tools

capture_screenshot

Machen Sie einen Screenshot einer Webseite (standardmäßig Viewport).

Parameter

Typ

Standard

Hinweise

url

string (erforderlich)

—

Seite, die erfasst werden soll

full_page

boolean

false

Erfassen Sie die gesamte scrollbare Seite

width / height

number

API-Standard

Viewport / Gerätegröße

format

"png" | "jpeg"

png

Bildformat

block_ads

boolean

true

Werbung entfernen

block_cookie_banners

boolean

true

Cookie-Einwilligungs-Popups entfernen

country

string

—

Proxy-Land als zweistelliger ISO 3166-1 alpha-2-Code, z. B. "DE" (automatisch IP/Sprache/Zeitzone/Geo)

strict_country

boolean

true

Fehler ausgeben, wenn das Land keinen Proxy hat, anstatt auf die USA zurückzufallen

language / time_zone / geolocation

string

—

Manuelle Überschreibungen

wait_ms

number

API-Standard

Zusätzliche Wartezeit vor der Erfassung (SPAs/Animationen)

max_height

number

20000 (ganze Seite)

Erfasste Höhe begrenzen

Gibt den Screenshot als MCP-Bild zurück.

„API-Standard" ist keine Zahl, die dieses Paket angeben kann. width, height und wait_ms werden nur weitergeleitet, wenn Sie sie übergeben. Was also gilt, wenn Sie sie nicht übergeben, entscheidet die Site-Shot-API und kann sich ohne eine Veröffentlichung hier ändern. Versionen bis 1.1.0 druckten Pixelgrößen für width / height, die die API nicht verwendet — ein Agent, der sie wegließ, um „den Standard" zu nehmen, erhielt einen anderen Viewport, ohne dass das zurückgegebene Bild dies erkennen ließ. Übergeben Sie explizite Werte, wann immer die Größe wichtig ist.

Ländercodes sind ISO-Codes, keine Namen. Übergeben Sie "DE", nicht "Germany". Die API gleicht Codes exakt ab und würde andernfalls über einen US-Proxy rendern, ohne Sie zu informieren. Daher lehnt der Server vollständige Namen ab, bevor er ein Rendering ausgibt. strict_country (standardmäßig aktiviert) verwandelt ein nicht verfügbares Land ebenfalls in einen Fehler anstelle eines stillen US-Screenshots — übergeben Sie false, um wieder auf den Fallback zu setzen. Unterstützte Länder →

capture_full_page

Gleich wie capture_screenshot mit aktivierter Ganzseiten-Erfassung.

Warum diesen Server anstelle des eigenen Browsers des Agenten aufrufen?

Wenn Ihr Agent einen Browser steuert, kann er selbst Screenshots von Seiten machen — und für Seiten, die angemeldet sein müssen oder durch einen Ablauf geführt werden, ist das das richtige Werkzeug. Für öffentliche URLs ist es in der Regel bessere Technik, die Erfassung an diesen Server zu delegieren: Jede Erfassung läuft durch dieselbe Pipeline (keine Neuplanung zwischen den Läufen), kann aus einem bestimmten Land mit passender Locale und Zeitzone erfolgen (country + strict_country), wird von einem Bildklassifikator mit einer eskalierenden Wiederholungsleiter bewertet, bevor sie zurückgegeben wird, und kostet einen Bruchteil eines Cents anstelle einer Browsersitzung plus Vision-Tokens pro Blick. Der vollständige Vergleich, beide Richtungen ehrlich dargelegt: KI-Agent vs. Screenshot-API — wer sollte die Seite erfassen.

Konfiguration

Umgebungsvariable

Erforderlich

Beschreibung

SITESHOT_API_KEY

ja

Ihr Site-Shot-API-Schlüssel (verwendet als userkey).

Der Server ist ein dünner Wrapper über die bestehende Site-Shot-HTTP-API (https://api.site-shot.com/) — kein separates Backend.

Lokale Entwicklung

npm install
npm run check   # syntax check
npm run smoke   # offline tests (stubbed fetch, no API key needed)
SITESHOT_API_KEY=yourkey npm start   # run the server on stdio

Anforderungen

Node.js ≥ 18 (verwendet das eingebaute fetch).

Lizenz

MIT

Available Tools

2 tools
capture_full_pageCapture full-page website screenshotA

Take a full-page (entire scrollable height) screenshot of a web page with Site-Shot and return it as an image. Convenience wrapper around capture_screenshot with full-page capture enabled.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL of the web page to capture. A bare domain like example.com is accepted (https:// is assumed).
widthNoViewport width in pixels (default 1280).
heightNoViewport height in pixels (default 1024).
formatNoImage format. Default: png.
block_adsNoRemove ads for a cleaner screenshot. Default: true.
block_cookie_bannersNoRemove cookie-consent banners/popups. Default: true.
countryNoRender through a proxy in this country, e.g. "Germany" (auto-sets IP, language, time zone, geolocation).
languageNoOverride browser language, e.g. "de".
time_zoneNoOverride time zone, e.g. "Europe/Berlin".
geolocationNoOverride geolocation as "lat,lng".
wait_msNoMilliseconds to wait after load before capturing (for SPAs/animations).
max_heightNoCap the captured height in pixels (max 20000).

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes the action as a wrapper but does not disclose side effects, output format details, or limitations beyond what the schema parameters cover.

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?

Two sentences with no wasted words; the core purpose is front-loaded.

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?

Given the tool has 12 parameters (all well-described in schema) and no output schema, the description is adequate as a summary but lacks details on return format and additional behavioral context.

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 coverage is 100% with detailed parameter descriptions, so the description adds little extra meaning. Baseline score of 3 is appropriate.

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 takes a full-page screenshot and mentions it's a convenience wrapper around capture_screenshot with full-page capture enabled, distinguishing it from the sibling tool.

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 implies usage for full-page screenshots and references the sibling tool, but does not explicitly state when not to use it or provide alternative scenarios.

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

capture_screenshotCapture website screenshotB

Take a screenshot of a web page with Site-Shot and return it as an image. Renders in a real Chromium browser. Supports viewport/device sizing, full-page capture, country proxies, and automatic ad & cookie-banner removal (cleaner image, fewer vision tokens).

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL of the web page to capture. A bare domain like example.com is accepted (https:// is assumed).
widthNoViewport width in pixels (default 1280).
heightNoViewport height in pixels (default 1024).
formatNoImage format. Default: png.
block_adsNoRemove ads for a cleaner screenshot. Default: true.
block_cookie_bannersNoRemove cookie-consent banners/popups. Default: true.
countryNoRender through a proxy in this country, e.g. "Germany" (auto-sets IP, language, time zone, geolocation).
languageNoOverride browser language, e.g. "de".
time_zoneNoOverride time zone, e.g. "Europe/Berlin".
geolocationNoOverride geolocation as "lat,lng".
wait_msNoMilliseconds to wait after load before capturing (for SPAs/animations).
max_heightNoCap the captured height in pixels (max 20000).
full_pageNoCapture the entire scrollable page instead of just the viewport. Default: false.

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It states the tool renders in a real Chromium browser and automatically removes ads and cookie banners, which is helpful. However, it does not mention potential side effects, rate limits, execution time, or authentication requirements. It also does not clarify whether the screenshot is destructive or what happens to the browser instance after capture.

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

Conciseness4/5

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

The description is two sentences long, making it relatively concise. The first sentence states the core action, and the second lists major features. It avoids extraneous details but could be slightly more compact by combining the two sentences or trimming the feature list slightly.

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?

Given the complexity of the tool (13 parameters, no output schema), the description provides a high-level overview of capabilities but lacks detail on return format (e.g., image type, resolution), error handling, and how features like 'full_page' work in practice. It is adequate for an experienced user but incomplete for a novice.

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?

The input schema covers all 13 parameters with descriptions, achieving 100% coverage. The tool description reiterates some schema concepts (viewport sizing, full-page capture, country proxies) but does not add significant new meaning beyond what the schema already provides. For example, 'country' parameter is explained in the schema; the description only mentions 'country proxies' generically. Baseline 3 is appropriate.

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 it takes a screenshot of a web page using Site-Shot and returns an image. It mentions features like viewport sizing, full-page capture, and ad removal. However, it does not explicitly distinguish itself from the sibling tool 'capture_full_page', which may cause confusion.

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

Usage Guidelines2/5

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

The description lists features but provides no guidance on when to use this tool versus alternatives like 'capture_full_page'. It does not mention any prerequisites or conditions for use, nor does it explain when to use the 'full_page' parameter or when to prefer a different tool.

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.

  1. 2 tool updatesv1.0.1
    • Changedcapture_full_page3 fields changed
      • changedInput schema / properties / url / description
        Previous value: -"The URL of the web page to capture."New value: +"The URL of the web page to capture. A bare domain like example.com is accepted (https:// is assumed)."
      • removedInput schema / properties / url / format
        Removed value: -"uri"
      • addedInput schema / properties / url / minLength
        Added value: +1
    • Changedcapture_screenshot3 fields changed
      • changedInput schema / properties / url / description
        Previous value: -"The URL of the web page to capture."New value: +"The URL of the web page to capture. A bare domain like example.com is accepted (https:// is assumed)."
      • removedInput schema / properties / url / format
        Removed value: -"uri"
      • addedInput schema / properties / url / minLength
        Added value: +1
  2. 2 tool updatesv0.1.1
    • First observedcapture_full_page
    • First observedcapture_screenshot
Deploy Server
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

TDQS

B3.2/5.0

Scored across 2 tools

Disambiguation2/5

The two tools are nearly identical; capture_full_page is explicitly a wrapper for capture_screenshot with full-page enabled. An agent would likely misuse them, as the difference is only a parameter.

Naming Consistency3/5

Both use verb_noun pattern ('capture_screenshot', 'capture_full_page'), but 'full_page' is a qualifier while 'screenshot' is the resource; inconsistent because one tool name specifies a parameter in the name itself.

Tool Count3/5

Two tools is minimal but arguably sufficient for a simple screenshot service. However, the duplication suggests one tool could have been omitted, making the surface slightly too heavy for the scope.

Completeness3/5

The set covers basic screenshot needs with features like viewport sizing, proxies, and ad removal. However, it lacks tools for specific device emulation or batch processing, which are common in screenshot services.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers