Skip to content
All guides

Best Screenshot Tools for AI Coding Agents

MCP servers and tools that let coding agents like Claude Code, Cursor, and Copilot take, find, or refresh screenshots.

Coding agents work with screenshots in two ways: looking at the UI while they build it, and updating documentation screenshots after a change. Different tools fit each job.

The short answer

For an agent that needs to look at the app while coding, use Playwright MCP. It is free and drives a real browser. For agents that update screenshots in a docs repo, Heroshot's MCP server is a strong free option. ScreenshotAgent's MCP server suits teams whose screenshots are a shared, hosted library used by docs, support, and marketing: the agent can list, create, and recapture them after it ships a change.

What we looked for

  • What the agent is trying to do: see the UI, or maintain published screenshots.
  • Setup effort in Claude Code, Cursor, or similar.
  • Where the resulting images live.
  • Cost per call.

Our picks

  1. 1. Playwright MCP

    Best for letting an agent see and drive your app

    Microsoft's MCP server gives an agent a browser to navigate and interact with pages, mainly through accessibility snapshots, and it can also save screenshots.

    Pricing: Free, Apache-2.0.

    • Runs locally against your dev server.
    • No per-call cost.
    • Images are local files, not a managed library.

  2. 2. Heroshot

    Best free option for docs-repo screenshots

    Its MCP server lets coding assistants capture and update screenshots defined in the repo's Heroshot config.

    Pricing: Free, MIT licensed, no paid tiers.

    • Visual picker writes the config for you.
    • Light/dark and viewport variants from one config.
    • GitHub Actions workflow commits new screenshots and opens a pull request.
    • Made for developers; writers will need help to set up.
    • Screenshots live in the repo, so there are no hosted embed URLs for a CMS or help center.

  3. 3. ScreenshotAgent

    Best for a hosted library shared with non-engineers

    A remote MCP server at /mcp with tools to list and search projects and screenshots, check capture status, create screenshots, recapture, and add AI annotations (circles, arrows, callouts, blur). Included on every plan and authenticated with a team API token.

    Pricing: Pro $199/mo (400 captures, 2,000 AI annotations), Business $499/mo (1,200 captures, 6,000 AI annotations), Enterprise from $1,499/mo. Unlimited users, Recapture API, MCP server, and search API on every plan. 14-day trial with 5 captures and 10 AI annotations, or 30 captures and 100 AI annotations with a card.

    • Agent changes reach docs, help center, and marketing images through the same URLs.
    • Approval step before new captures are served.
    • Paid, and each capture counts against your plan.
    • 60 MCP requests per minute per token; captures share the API's daily limit.

  4. 4. ScreenshotOne

    Best for one-off screenshots of public URLs

    ScreenshotOne offers an MCP server so agents can screenshot any URL through its API.

    Pricing: Free 100/mo. Basic $17/mo (2,000). Growth $79/mo (10,000). Scale $259/mo (50,000).

    • Cheap per shot.
    • Many rendering options.
    • Logged-in app pages need cookies or scripts.
    ScreenshotAgent vs ScreenshotOne

Pricing checked on October 2, 2026 from each vendor’s public website. Confirm current prices before buying.

FAQ

How do I add ScreenshotAgent to Claude Code?
Create a team API token, then run: claude mcp add --transport http screenshotagent https://screenshotagent.com/mcp with the token as a Bearer header. See the MCP server docs for details.
Can an agent recapture docs screenshots after it changes the UI?
Yes, with ScreenshotAgent or Heroshot. ScreenshotAgent updates hosted URLs; Heroshot updates files in your repo.

Sources

Run this guide in ScreenshotAgent

Start with one project and apply this workflow to keep screenshots accurate with less effort.

Start free trial14-day trial · 5 captures free · No card required