mcp.screenshotink.com

The screenshot MCP server for Claude, Cursor & AI agents

Five tools your agent can call to capture, batch, compare and audit any page — and see the result in the same turn. No local Chrome, no Puppeteer maintenance, works in CI and cloud sandboxes.

Get free API key API docs

100 captures/month free · the same key works over MCP and REST

✓ MCP server live Claude DesktopClaude CodeCursorWindsurf GitHub ↗
claude_desktop_config.json 
{
  "mcpServers": {
    "screenshotink": {
      "command": "npx",
      "args": ["@screenshotink/mcp"],
      "env": { "SCREENSHOTINK_API_KEY": "sk_live_…" }
    }
  }
}
Tool reference

Five tools, one key

Same parameters and defaults as the REST API. Every result returns the image inline, so the agent can reason about pixels immediately.

take_screenshot 
{ url, width?, full_size?,
  format?, no_ads?, lazy_load? }

When an agent needs to verify a deploy, check a layout, or read a page visually.

bulk_screenshots 
{ urls: string[≤20],
  width?, full_size?, format? }

When an agent audits a whole funnel or a competitor set in one call.

compare_screenshots 
{ url_a, url_b | image_a, image_b,
  threshold? }

When an agent checks staging vs production, or before vs after a change.

run_lighthouse 
{ url, categories?:
  ["performance","a11y","seo"] }

When an agent needs scores plus the rendered page to explain why.

capture_sitemap 
{ sitemap_url, limit?: ≤50,
  width?, format? }

When an agent inventories a site visually — every page the sitemap lists.

Captures over MCP count against the same quota as the REST API. One key, one meter.

See quotas →
In practice

A real agent session

MCP session claude · mcp.screenshotink.com
Compare our pricing page on staging vs production — did the new plan cards ship correctly?
▸ compare_screenshots { "url_a": "https://acme.com/pricing", "url_b": "https://staging.acme.dev/pricing" }
diff · A ↔ B · threshold 0.1
Diff by ScreenshotInk · 4.7% changed

Changed regions highlighted — labels included for non-color reading

The plan grid changed from 3 to 4 cards on staging — the new "Scale" card is present and highlighted. Card widths shrank from 84px to 68px equivalents; spacing is consistent. 4.7% of pixels differ, all within the plan grid region. The deploy looks correct and intentional. ✓

Why hosted

Works where local browsers don't

CI pipelines

No headless Chrome install, no flaky browser binaries in your runners. One HTTP call from any job.

Cloud agents

Hosted runtimes can't launch browsers. The remote MCP endpoint gives them eyes without a single dependency.

Zero maintenance

We patch Chromium, rotate IPs, handle lazy-load and cookie walls. Your agent just asks for pixels.

Give your agent eyes in 30 seconds

Free key, 100 captures/month. One npx command or the remote URL — live now. No card required.

Get free API key Setup docs