How to Give AI Agents Website Screenshots with MCP (2026)

If you're building an AI agent that needs to see a web page — to drive a browser, run visual QA, or feed a screenshot into a vision model — you need a screenshot API that the agent can call on its own. In 2026 the clean way to wire that up is the Model Context Protocol (MCP): you point your agent at an MCP server and it gets a screenshot tool it can invoke directly. This guide explains what MCP is, why agents need screenshots, shows a copy-paste Claude Desktop config for Site-Shot's official MCP server, and lists which screenshot APIs actually ship an official MCP server versus those that don't.

Disclosure: this comparison is published by Site-Shot. We have kept the numbers accurate and the trade-offs honest — including where competitors beat us. Prices checked August 2026; confirm on each vendor pricing page before buying.

What is MCP, and why would an agent need screenshots?

The Model Context Protocol (MCP) is an open standard for connecting AI assistants to external tools and data. An MCP server exposes one or more tools (each with a name, a description, and a JSON input schema); an MCP client — Claude Desktop, Cursor, Claude Code, and a growing list of agent frameworks — discovers those tools and lets the model call them. The agent never sees your API key or HTTP plumbing; it just sees a tool like "capture a screenshot of this URL" and decides when to use it.

Agents reach for screenshots in three recurring patterns:

• Vision pipelines. A multimodal model can't reliably reason about a page from raw HTML. Hand it a rendered PNG and it can read layout, find a button, check a chart, or verify that a deploy looks right.
• Web automation. An agent driving a flow (login, checkout, form fill) needs to look between steps to confirm what happened before it clicks again.
• Visual QA and monitoring. Capture a page on a schedule or after a change, then diff or describe it to catch broken layouts, missing images, or unexpected content.

Why ad and cookie-banner removal helps vision models

Ads, sticky cookie-consent overlays, and newsletter modals can cover the content an agent needs. Removing them at capture time (Site-Shot's no_ads and no_cookie_popup parameters, and equivalents on some competitors) gives the model a cleaner image to inspect. It does not guarantee lower image-token costs: those depend on the model, image dimensions, and detail settings, not simply on whether ads are visible.

Setting up Site-Shot's MCP server (copy-paste config)

Site-Shot ships an official MCP server published as site-shot-mcp (registry id io.github.site-shot/site-shot-mcp). It runs over npx, so there's nothing to install globally. Drop this into your Claude Desktop config file (claude_desktop_config.json — Settings → Developer → Edit Config), restart Claude Desktop, and the tools appear:

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

The server exposes two tools:

• capture_screenshot — a viewport screenshot of a URL, with the usual options (dimensions, device emulation, format, ad/cookie removal, country proxy).
• capture_full_page — a full-length capture that scrolls and stitches the entire page (up to 20,000px tall on Site-Shot), ideal for handing a whole article or dashboard to a vision model.

The same config shape works in other MCP clients (Cursor, Claude Code, etc.) — they all read a command / args / env block. Under the hood each tool is a single GET request to Site-Shot's real Chromium renderer, returning a PNG/JPEG or JSON (base64 image plus the target's response headers).

Honest scoping: the MCP server requires an API key. Site-Shot's free, no-signup offering is the browser-based online tool — great for one-off captures, but it does not issue an API key. To use the MCP server (or the HTTP API at all) you need an account and a key from the pricing page, starting at $5/mo for 2,000 screenshots. See the AI agents page for the full agent setup.

Which screenshot APIs ship an official MCP server?

Plenty of screenshot APIs exist; far fewer maintain an official, first-party MCP server you can trust to track their feature set. This table sorts by that distinction.

Cost per 1,000 is from each provider's cheapest paid plan — except Urlbox, whose $19/mo Lo-Fi tier is scoped to sites you own and returns third-party pages as thumbnails only, so its row uses Hi-Fi, the first plan an agent can point at arbitrary URLs ($49/mo for 5,000, checked August 2026). For an agent, "official MCP" matters: a first-party server stays in sync with the API and is maintained by the vendor; a third-party wrapper can lag or vanish.

The MCP-ready options, one by one

Site-Shot

Site-Shot's official server (npx -y site-shot-mcp) exposes capture_screenshot and capture_full_page, backed by real Chromium with device emulation, country proxies (IP, language, time zone, geolocation on every plan), full-page to 20,000px, and ad/cookie removal that keeps vision-model images clean. It's the lowest entry commitment with an official MCP — $5/mo for 2,000 shots, dropping to $0.80/1,000 at scale — and the only one here with a genuinely free, no-signup browser tool to prototype against. Best for: agents that want full-featured real-browser captures without premium per-shot pricing. Gap: the official client SDKs cover Node.js (npm install site-shot-sdk) and Python (pip install site-shot) — elsewhere the HTTP API is a plain GET you call directly from non-MCP code.

ScreenshotOne

ScreenshotOne ships an official MCP server (the render-website-screenshot tool, env SCREENSHOTONE_API_KEY) alongside the deepest feature set in this list: SDKs in seven languages, PDF and video rendering, JS/CSS injection, S3 upload, webhooks, and a dedicated AI-agents page. It is genuinely the most polished, integration-rich option — and the priciest per shot at $8.50/1,000 ($17/mo for 2,000; geo proxy is gated to its Growth and Scale tiers). Best for: teams that want the richest agent tooling and don't mind paying for it.

Urlbox

Urlbox maintains an official MCP server (@urlbox/screenshot-mcp, a render tool that returns PNG/PDF/MP4 plus HTML/metadata, env SECRET_KEY). Its differentiators include tamper-evident timestamps and hashes (its claim), change detection, and many formats. There's no free tier — a 7-day trial and a $100/10K refund guarantee instead — and an agent pointing at arbitrary URLs needs Hi-Fi at $49/mo for 5,000 renders ($9.80/1,000, checked August 2026); the cheaper $19 Lo-Fi tier is scoped to sites you own and returns third-party pages as thumbnails. Best for: teams that have verified its retention and evidence features against their own legal or audit requirements.

Microlink

Microlink offers an official MCP integration over a "browser as API" with full Puppeteer/Playwright control and global edge caching. Its volume pricing is the cheapest full-featured option here — $49/mo for 46,000 requests (~$1.07/1,000) — with adblock and cookie-banner handling available even on the free 25-req/day tier. Best for: high-volume agents that want headless-browser control and the lowest full-featured price at scale.

CaptureKit

CaptureKit pairs screenshots with a Page Content API (HTML/Markdown/AI summaries), stealth mode, and an official Streamable HTTP MCP endpoint at https://mcp.capturekit.dev/, from $7/mo for 1,000 credits. Each MCP tool maps to an API operation. That content side is handy when your agent needs both a screenshot and clean page text to reason over. Best for: indie developers building agents that need clean web content for an LLM alongside captures.

ApiFlash, ScreenshotAPI.net, and Thum.io

ApiFlash is fast and cheap (Chrome on AWS Lambda, $7/mo for 1,000), and exposes an HTTP API that can be wrapped as an agent tool. ScreenshotAPI.net has a broad parameter set (element capture, video, PDF, data extraction) from $9/mo; check its current docs for MCP support. Thum.io is the cheapest raw price ($0.20/1,000) with a no-signup branded free tier, but full-page is a paid feature and it does not advertise ad/cookie removal or geo routing. For these vendors, verify current MCP documentation or wrap the HTTP API as a tool.

How to choose for an AI agent

• Want the lowest-commitment official MCP with real-browser quality? Site-Shot — $5/mo, official site-shot-mcp, ad/cookie removal for cleaner captures, and a free browser tool to test first.
• Want the richest, most integration-heavy agent tooling regardless of price? ScreenshotOne.
• Need archival and evidence-oriented features? Consider Urlbox after checking its verification and retention details.
• High volume and want the cheapest full-featured option? Microlink at scale.
• Need clean page content plus screenshots for your LLM? CaptureKit.
• Comfortable wrapping an HTTP API yourself? ApiFlash (fast/budget), ScreenshotAPI.net (broad params), or Thum.io (cheapest thumbnails) are options to compare.

For more detail, see our screenshot MCP server roundup, the 8-tool screenshot API comparison, the cheapest screenshot API guide, and full-page vs. viewport screenshots when deciding which tool your agent should call. If you are still weighing whether the agent should capture pages itself at all, start with AI agent vs. screenshot API. And if your agent is built on a framework instead of an MCP client, the image has to reach the model a different way: LangChain lets a tool return it, while CrewAI requires passing it in as a file.

FAQ

What is a screenshot API for AI agents? A screenshot API for AI agents is a hosted service that renders a web page in a real browser and returns an image (PNG/JPEG), which an AI agent calls to "see" a page — for vision-model reasoning, web automation, or visual QA. The agent-friendly way to expose it is an MCP server, so the model can invoke a screenshot tool directly instead of you writing custom HTTP glue.

What is a screenshot MCP server? An MCP server that exposes screenshot capture as one or more tools an AI agent can call. Site-Shot's official server (npx -y site-shot-mcp, registry id io.github.site-shot/site-shot-mcp) exposes capture_screenshot and capture_full_page; ScreenshotOne, Urlbox, Microlink, and CaptureKit ship official servers too. For the other vendors, check current documentation before assuming a vendor-published MCP server is available; otherwise wrap the HTTP API as a tool.

How do I take a website screenshot programmatically for an agent? Two ways. Over MCP: add the vendor's MCP server to your client config (for Site-Shot, the npx/args/env block above with your SITESHOT_API_KEY) and let the agent call the tool. Or directly: send a single HTTP GET to the screenshot API with the target URL and options, and read back the PNG/JPEG or a JSON payload. Site-Shot supports both; the HTTP API is a plain GET with no SDK required, and Node.js and Python projects can install the official site-shot-sdk or site-shot package instead.

Do I need an API key to use a screenshot MCP server? Hosted screenshot services generally do. Site-Shot's server authenticates with SITESHOT_API_KEY, which requires an account. Site-Shot's free, no-signup option is its browser-based online tool only — that tool does not issue an API key. The paid API, which the MCP server uses, starts at $5/mo for 2,000 screenshots. A self-hosted server that runs its own browser may not need a vendor key.

Why remove ads and cookie banners before sending a screenshot to a vision model? Ads, cookie overlays, and modals can hide the content you want analyzed. Site-Shot's no_ads and no_cookie_popup options can produce a cleaner screenshot, but they do not by themselves guarantee a lower vision-token bill when the image dimensions stay the same.

Which screenshot API is best for building an AI agent in 2026? If you want the lowest-commitment official MCP with real-browser quality and ad/cookie removal, Site-Shot ($5/mo, site-shot-mcp). For the richest agent tooling and SDKs, ScreenshotOne. For archival and evidence-oriented features, consider Urlbox after checking its verification details. For cheapest at volume, Microlink. For screenshots plus clean page content over a remote MCP endpoint, CaptureKit.

Capture your first screenshot free in your browser — no signup — at site-shot.com. Building an agent? See the AI agents page, grab an API key on the pricing page, and read the API docs.