About screenshotink
ScreenshotInk is a hosted browser capture MCP server for AI agents and teams checking web pages. It returns screenshots inline and combines capture, visual comparison, Lighthouse audits, and sitemap coverage without requiring a local browser.
Key features
- 01Capture viewport or full-page screenshots
- 02Batch capture up to 20 URLs
- 03Compare pages with pixel diffs
- 04Run Lighthouse audits and core web vitals
- 05Capture pages listed in a sitemap
Use cases
- 01Check staging against production
- 02Audit a funnel or competitor pages
- 03Review performance, accessibility, and SEO
- 04Capture every page in a sitemap
MCP support
Exposes five browser-capture tools to MCP clients through a hosted endpoint or the @screenshotink/mcp package. Results include screenshots inline for the agent to inspect.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.screenshotink.com/mcpclaude mcp add --transport http com-screenshotink https://mcp.screenshotink.com/mcp{"mcpServers":{"com-screenshotink":{"type":"http","url":"https://mcp.screenshotink.com/mcp"}}}Open in Cursor{"servers":{"com-screenshotink":{"type":"http","url":"https://mcp.screenshotink.com/mcp"}}}Open in VS Code{"mcpServers":{"com-screenshotink":{"type":"http","url":"https://mcp.screenshotink.com/mcp"}}}{"mcpServers":{"com-screenshotink":{"serverUrl":"https://mcp.screenshotink.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEScreenshotInk MCP Server
Give your AI agent eyes. Five tools to capture, batch, compare and audit any web page — through ScreenshotInk's hosted Chromium fleet. No local browser, no Puppeteer maintenance; works in Claude Desktop, Claude Code, Cursor, Windsurf, CI runners and cloud sandboxes.
Every result returns the screenshot inline in the same turn, so the agent can reason about pixels immediately.
You: Compare our pricing page on staging vs production — did the new cards ship?
Agent: ▸ compare_screenshots { url_a: "https://acme.com/pricing", url_b: "https://staging.acme.dev/pricing" }
4.7% of pixels differ, all inside the plan grid — the new Scale card is present. Deploy looks correct. ✓
Quick start
You need a ScreenshotInk API key — free, 100 captures/month, no card: screenshotink.com/signup
Claude Code
claude mcp add screenshotink -- npx -y @screenshotink/mcp --key sk_live_YOUR_KEY
or connect to the hosted remote server (nothing runs locally):
claude mcp add --transport http screenshotink https://mcp.screenshotink.com/mcp \
--header "Authorization: Bearer sk_live_YOUR_KEY"
Claude Desktop
claude_desktop_config.json:
{
"mcpServers": {
"screenshotink": {
"command": "npx",
"args": ["-y", "@screenshotink/mcp"],
"env": { "SCREENSHOTINK_API_KEY": "sk_live_YOUR_KEY" }
}
}
}
Cursor / Windsurf
{
"mcpServers": {
"screenshotink": {
"command": "npx",
"args": ["-y", "@screenshotink/mcp", "--key", "sk_live_YOUR_KEY"]
}
}
}
Remote server (cloud agents, hosted runtimes, custom connectors)
Anything that speaks Streamable HTTP can connect directly — nothing to install. In Claude or ChatGPT, add it as a custom connector with the URL below and sign in over OAuth; for scripts/CI, pass your key as a bearer token:
URL: https://mcp.screenshotink.com/mcp
Auth: OAuth 2.1 (sign in on first use) — or Authorization: Bearer sk_live_YOUR_KEY
Tools
| Tool | What it does |
|---|---|
take_screenshot | Capture any URL — viewport or full page, png/jpeg/pdf, dark mode, ad & cookie-banner blocking, lazy-load handling |
bulk_screenshots | Up to 20 URLs in one call — audit a funnel or a competitor set at once |
compare_screenshots | Pixel-diff two URLs (staging vs production, before vs after) — returns changed-% and a highlighted diff image |
run_lighthouse | Google Lighthouse scores (performance, accessibility, best practices, SEO) + core web vitals |
capture_sitemap | Fetch a sitemap.xml and screenshot every page it lists |
Same parameters and defaults as the REST API. Captures over MCP count against the same quota as the REST API — one key, one meter. Identical requests within 24h are served from cache for free.
Why hosted?
- CI pipelines — no headless Chrome install, no flaky browser binaries in runners.
- Cloud agents — hosted runtimes can't launch browsers; the remote endpoint gives them eyes with zero dependencies.
- Zero maintenance — we patch Chromium, handle lazy-load, ads and cookie walls. Your agent just asks for pixels.
Links
- Product & docs: screenshotink.com · MCP docs
- REST API reference: screenshotink.com/docs
- Issues: GitHub issues
MIT © ScreenshotInk — a ScalingWeb product
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.