Screenshotink

com.screenshotinkPublished by screenshotink.comOfficial publisherv1.0.4Updated Nov 2, 2026

Screenshot, diff, audit and sitemap-capture any web page — 5 MCP tools for AI agents.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBrowser AutomationSecurity & Monitoring

Overview

AI-generated overview

ScreenshotInk lets an assistant screenshot, batch-capture, pixel-diff, Lighthouse-audit and sitemap-crawl web pages through a hosted Chromium fleet.

What you can do
  • Capture a single URL as viewport or full-page image in png, jpeg or pdf, with dark mode, ad and cookie-banner blocking and lazy-load handling
  • Capture up to 20 URLs in one call to audit a funnel or competitor set
  • Pixel-diff two URLs and get the changed percentage plus a highlighted diff image
  • Run Google Lighthouse scores for performance, accessibility, best practices and SEO with core web vitals
  • Fetch a sitemap.xml and screenshot every page it lists
  • Results come back inline in the same turn so the agent can reason about the pixels
When to use it
Useful when an assistant needs to see or verify rendered web pages without a local browser: comparing staging against production, checking visual regressions in CI, auditing page performance and SEO, or capturing many pages at once from a cloud agent that cannot launch a browser.
Requirements
A ScreenshotInk API key, passed as SCREENSHOTINK_API_KEY or the --key argument for the local npm package, or as a bearer token for the remote endpoint. The remote server at mcp.screenshotink.com uses OAuth 2.1 sign-in or a bearer key. The local option needs Node.js to run the npm package over stdio. Network access to ScreenshotInk's service is required.
Before you install
The API key is a live secret; keep it out of shared configs and repositories. Captures count against the same monthly quota as the REST API, so heavy batch or sitemap runs can exhaust it. Requested URLs are fetched by ScreenshotInk's hosted browsers, so page addresses are sent to a third party. Screenshots and diffs are returned to the assistant as image data.

Installation

In SourceWeft

  1. Open Screenshotink in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.screenshotink%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "screenshotink": {
      "type": "http",
      "url": "https://mcp.screenshotink.com/mcp"
    }
  }
}

README

ScreenshotInk MCP Server

[npm version] [MCP] [license]

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

bash
claude mcp add screenshotink -- npx -y @screenshotink/mcp --key sk_live_YOUR_KEY

or connect to the hosted remote server (nothing runs locally):

bash
claude mcp add --transport http screenshotink https://mcp.screenshotink.com/mcp \  --header "Authorization: Bearer sk_live_YOUR_KEY"

Claude Desktop

claude_desktop_config.json:

json
{  "mcpServers": {    "screenshotink": {      "command": "npx",      "args": ["-y", "@screenshotink/mcp"],      "env": { "SCREENSHOTINK_API_KEY": "sk_live_YOUR_KEY" }    }  }}

Cursor / Windsurf

json
{  "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/mcpAuth:  OAuth 2.1 (sign in on first use) — or Authorization: Bearer sk_live_YOUR_KEY

Tools

ToolWhat it does
take_screenshotCapture any URL — viewport or full page, png/jpeg/pdf, dark mode, ad & cookie-banner blocking, lazy-load handling
bulk_screenshotsUp to 20 URLs in one call — audit a funnel or a competitor set at once
compare_screenshotsPixel-diff two URLs (staging vs production, before vs after) — returns changed-% and a highlighted diff image
run_lighthouseGoogle Lighthouse scores (performance, accessibility, best practices, SEO) + core web vitals
capture_sitemapFetch 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

MIT © ScreenshotInk — a ScalingWeb product

Source: README.md at commit b996b5c

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.4LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts