Skip to main content
Glama
deenesjakoruzh
site-shot

site-shot-mcp

Official
by site-shot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Site-Shot MCP server

Дайте Claude, Cursor и другим ИИ-агентам возможность видеть любую веб-страницу — делайте скриншоты сайтов с помощью Site-Shot через Model Context Protocol.

Настоящий рендеринг Chromium · захват всей страницы · прокси по странам · автоматическое удаление рекламы и cookie-баннеров (чище изображения, меньше токенов для зрения).

Быстрый старт (Claude Desktop)

  1. Получите API-ключ Site-Shot на https://www.site-shot.com/start/.

  2. Добавьте это в конфигурацию Claude Desktop (claude_desktop_config.json):

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

  1. Перезапустите Claude Desktop. Попросите его "сделать полноэкранный скриншот https://news.ycombinator.com" и он вызовет сервер и покажет вам изображение.

Работает так же в любом MCP-клиенте (Cursor, Cline, VS Code, LangChain, CrewAI) — укажите клиенту npx -y site-shot-mcp с SITESHOT_API_KEY в окружении.

Related MCP server: Webpage Screenshot MCP Server

Инструменты

capture_screenshot

Сделать скриншот веб-страницы (по умолчанию — область просмотра).

Параметр

Тип

По умолчанию

Примечания

url

string (обязательно)

—

Страница для захвата

full_page

boolean

false

Захватить всю прокручиваемую страницу

width / height

number

по умолчанию API

Размер области просмотра / устройства

format

"png" | "jpeg"

png

Формат изображения

block_ads

boolean

true

Удалять рекламу

block_cookie_banners

boolean

true

Удалять всплывающие окна согласия на cookie

country

string

—

Страна прокси в виде двухбуквенного кода ISO 3166-1 alpha-2, например "DE" (авто IP/язык/часовой пояс/гео)

strict_country

boolean

true

Выдать ошибку, если для страны нет прокси, вместо перехода на прокси в США

language / time_zone / geolocation

string

—

Ручные переопределения

wait_ms

number

по умолчанию API

Дополнительное ожидание перед захватом (SPA/анимации)

max_height

number

20000 (полная страница)

Ограничить высоту захвата

Возвращает скриншот в виде MCP-изображения.

"API default" — это не число, которое этот пакет может указать. width, height и wait_ms передаются только тогда, когда вы их передаёте, поэтому то, что применяется, когда вы их не передаёте, решает Site-Shot API и может измениться без выпуска новой версии здесь. Версии до 1.1.0 выводили размеры в пикселях для width / height, которые API не использует — агент, опускавший их, чтобы получить «значение по умолчанию», получал другой вьюпорт, и в возвращённом изображении ничто не указывало на это. Передавайте явные значения, когда размер важен.

Коды стран — это коды ISO, а не названия. Передавайте "DE", а не "Germany". API сопоставляет коды точно и в противном случае выполнил бы рендеринг через прокси в США, не сообщив вам об этом, поэтому сервер отклоняет полные названия прежде чем потратить рендер. strict_country (включён по умолчанию) точно так же превращает недоступную страну в ошибку вместо тихого скриншота через США — передайте false, чтобы вернуться к запасному варианту. Поддерживаемые страны →

capture_full_page

То же, что и capture_screenshot, но с включённым захватом всей страницы.

Зачем вызывать этот сервер вместо собственного браузера агента?

Если ваш агент управляет браузером, он может сам делать скриншоты страниц — и для страниц, требующих входа или прохождения по сценарию, это правильный инструмент. Для публичных URL делегирование захвата этому серверу обычно лучше с инженерной точки зрения: каждый захват выполняется по одному и тому же конвейеру (без повторного планирования между запусками), может быть выполнен из конкретной страны с соответствующими локалью и часовым поясом (country + strict_country), оценивается классификатором изображений с эскалационной лестницей повторных попыток перед возвратом результата и стоит долю цента вместо сеанса браузера плюс vision-токены за каждый просмотр. Полное сравнение, честно рассматривающее обе стороны: ИИ-агент против API скриншотов — кто должен захватывать страницу.

Конфигурация

Переменная окружения

Обязательная

Описание

SITESHOT_API_KEY

да

Ваш API-ключ Site-Shot (используется как userkey).

Сервер — это тонкая обёртка над существующим HTTP API Site-Shot (https://api.site-shot.com/) — без отдельного бэкенда.

Локальная разработка

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

Требования

Node.js ≥ 18 (использует встроенный fetch).

Лицензия

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