Skip to main content
Glama
deenesjakoruzh
site-shot

site-shot-mcp

Official
by site-shot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Site-Shot MCP server

Da a Claude, Cursor y otros agentes de IA la capacidad de ver cualquier página web — toma capturas de pantalla de sitios web con Site-Shot mediante el Model Context Protocol.

Renderizado real de Chromium · captura de página completa · proxies por país · eliminación automática de anuncios y banners de cookies (imágenes más limpias, menos tokens de visión).

Inicio rápido (Claude Desktop)

  1. Obtén una clave de API de Site-Shot en https://www.site-shot.com/start/.

  2. Añade esto a tu configuración de Claude Desktop (claude_desktop_config.json):

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

  1. Reinicia Claude Desktop. Pídele "haz una captura de pantalla de página completa de https://news.ycombinator.com" y llamará al servidor y te mostrará la imagen.

Funciona igual en cualquier cliente MCP (Cursor, Cline, VS Code, LangChain, CrewAI) — apunta el cliente a npx -y site-shot-mcp con SITESHOT_API_KEY en el entorno.

Related MCP server: Webpage Screenshot MCP Server

Tools

capture_screenshot

Captura una página web (viewport por defecto).

Parámetro

Tipo

Por defecto

Notas

url

string (obligatorio)

—

Página a capturar

full_page

boolean

false

Capturar toda la página desplazable

width / height

number

Por defecto de la API

Tamaño de viewport / dispositivo

format

"png" | "jpeg"

png

Formato de imagen

block_ads

boolean

true

Eliminar anuncios

block_cookie_banners

boolean

true

Eliminar los avisos emergentes de consentimiento de cookies

country

string

—

País del proxy como código de dos letras ISO 3166-1 alpha-2, p. ej. "DE" (IP/idioma/zona horaria/geolocalización automáticos)

strict_country

boolean

true

Fallar si el país no tiene proxy, en lugar de recurrir a EE. UU.

language / time_zone / geolocation

string

—

Anulaciones manuales

wait_ms

number

Por defecto de la API

Espera adicional antes de la captura (SPAs/animaciones)

max_height

number

20000 (página completa)

Limitar la altura capturada

Devuelve la captura de pantalla como una imagen MCP.

«Por defecto de la API» no es un número que este paquete pueda indicar. width, height y wait_ms solo se reenvían cuando los pasas, así que lo que se aplique cuando no los pasas lo decide la API de Site-Shot y puede cambiar sin necesidad de publicar una versión de este paquete. Las versiones hasta la 1.1.0 imprimían tamaños de píxel para width / height que la API no usa: un agente que los omitía para tomar "el valor por defecto" obtenía un viewport distinto, y la imagen devuelta no revela esa nada. Pasa valores explícitos siempre que el tamaño sea importante.

Los códigos de país son códigos ISO, nunca nombres. Pasa "DE", no "Germany". La API hace coincidir los códigos exactamente; de lo contrario usaría un proxy de EE. UU. sin avisarte, por lo que el servidor rechaza los nombres completos antes de gastar una renderización. strict_country (por defecto, activado) convierte un país no disponible en un error en lugar de una captura silenciosa desde EE.UU — pasa false para volver a la alternativa. Países compatibles →

capture_full_page

Igual que capture_screenshot con la captura de página completa habilitada.

¿Por qué llamar a este servidor en lugar del navegador del propio agente?

Si tu agente controla un navegador, puede capturar las páginas por sí mismo — y para páginas que requieren iniciar sesión o seguir un flujo paso a paso, esa es la herramienta adecuada. Para URLs públicas, delegar la captura en este servidor suele ser una mejor ingeniería: cada captura recorre la misma canal (sin replanificar entre pasos), se puede tomar desde un país concreto con la configuración regional y la zona horaria correspondientes (country + strict_country), la evalúa un clasificador de imágenes que reintenta de forma progresiva antes de devolverla, y cuesta menos de un céntimo en lugar de una sesión de navegador más tokens de visión por cada vistazo. La comparación completa, argumentada con honestidad en ambas direcciones: Agente de IA vs. API de capturas — quién debe capturar la página.

Configuración

Variable de entorno

Obligatoria

Descripción

SITESHOT_API_KEY

sí

Tu clave de API de Site-Shot (se usa como userkey).

El servidor es una envoltura fina sobre la API HTTP existente de Site-Shot (https://api.site-shot.com/) — no hay ningún backend por separado.

Desarrollo local

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

Requisitos

Node.js ≥ 18 (usa el fetch incorporado).

Licencia

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