Skip to main content
Glama

getsnap-mcp

Getsnap MCP server

Official MCP server for getSnap.dev. Gives Claude and other agents the ability to capture a web page, compare two pages and audit one for accessibility.

The capture tools return the image itself, not a link to it. A model can look at the page it just asked for, so "screenshot this and tell me what's broken" works in a single turn.

Features

  • capture_screenshot — any URL to PNG, JPEG or WebP, full page or viewport, with mobile and tablet emulation, returned inline so the model can look at it

  • capture_pdf — any URL to a PDF, returned as a link, since a PDF cannot be shown to a model inline

  • compare_pages — visual diff of two URLs: similarity score plus the overlay, inline

  • audit_accessibility — axe-core in a real browser: WCAG 2.0/2.1/2.2 violations by severity

  • check_usage — credits used and remaining, costs nothing

  • Cookie banner removal and ad blocking are on for every capture

  • Free tier: 100 captures a month, no card

Related MCP server: claude-vision-mcp

Install

No install step. Your client runs it with npx.

Get a free API key at getsnap.dev — 100 captures a month, no card.

Claude Code

claude mcp add getsnap --env GETSNAP_API_KEY=sk_live_... -- npx -y getsnap-mcp

Claude Desktop

claude_desktop_config.json:

{
  "mcpServers": {
    "getsnap": {
      "command": "npx",
      "args": ["-y", "getsnap-mcp"],
      "env": { "GETSNAP_API_KEY": "sk_live_..." }
    }
  }
}

The same block works in any client that speaks MCP over stdio.

Tools

Tool

Credits

Returns

capture_screenshot

1

The image, inline

capture_pdf

1

A link — a PDF can't be shown to a model

compare_pages

2

Similarity score + the diff overlay, inline

audit_accessibility

1

WCAG violations by severity

check_usage

0

Credits used and remaining

Cookie banners and ad overlays are removed by default on captures. Cached responses cost nothing and say so.

Things worth knowing

Large images are not inlined. Past about 1.5 MB the capture still happened and is still on the CDN, so the tool returns the link and says why. A full_page capture of a long page will usually hit this — pass format: "jpeg" or full_page: false to get it inline instead.

Every capture spends a credit, so each tool description states its cost. An agent deciding whether to call something should be able to see what it will cost before it does.

compare_pages costs 2, because it launches a browser per URL.

Configuration

Variable

Required

Default

GETSNAP_API_KEY

yes

—

GETSNAP_BASE_URL

no

https://api.getsnap.dev

Without a key the server exits immediately with a message explaining where to get one, rather than starting and failing on first use.

Examples

Once connected, ask your agent in plain language:

  • "Screenshot stripe.com on mobile and tell me if anything overlaps."

  • "Compare our staging site against production and show me what moved."

  • "Audit example.com for accessibility and list the critical failures."

  • "How many getSnap credits do I have left?"

Use cases

  • Catch layout breakage — screenshot a page at mobile width and have the model describe what overlaps or clips

  • Review a deploy — diff staging against production and see what moved before anyone else does

  • Accessibility triage — list WCAG failures by severity ahead of a release

  • Generate documents — turn an invoice, report or receipt URL into a PDF

  • Watch a competitor — capture a pricing page on a schedule and compare it with last week's

Versioning

This package versions independently of the getSnap REST API and the Node and Python SDKs. It shared their number until 1.14.3, when it moved out of the API monorepo into this repository; from here it moves on its own schedule.

MIT licensed. Issues to support@getsnap.dev.

Available Tools

5 tools
audit_accessibilityAudit a page for accessibility problemsA
Read-only

Run axe-core against a URL in a real browser and return WCAG 2.0/2.1/2.2 violations by severity, with the elements responsible. Costs 1 credit per call. Returns structured findings rather than an image, so you can act on them directly.

Inputs: url (required), max_violations.

capture_pdfCapture a page as PDFA
Read-only

Render a URL to PDF and return a link to it. Costs 1 credit per call. A PDF cannot be shown to you inline - use capture_screenshot if you need to read the page yourself.

Inputs: url (required), delay, full_page.

capture_screenshotCapture a screenshotA
Read-only

Render a URL in a real browser and return the image, so you can see the page. Removes cookie banners and ad overlays by default. Costs 1 credit per call. Use full_page for the whole scrollable page, or device to emulate a phone or tablet.

Inputs: url (required), delay, device, format, +4 more.

check_usageCheck remaining creditsA
Read-only

How many credits are used and remaining on this key this period. Free - spends no credit.

Inputs: no named parameters.

compare_pagesCompare two pages visuallyA
Read-only

Capture two URLs and compare them pixel by pixel. Returns a similarity score and an overlay image marking what changed, which you can look at. Costs 2 credits - it launches a browser per URL. Use for staging against production, or a page before and after a change.

Inputs: after_url (required), before_url (required), full_page, threshold.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: capture (screenshot/pdf), compare two pages, audit accessibility, and check credits. The only potential overlap—capture_screenshot vs capture_pdf vs compare_pages, all of which render URLs—is resolved explicitly in descriptions (e.g., PDF can't be shown inline, compare diffs two pages).

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun convention: compare_pages, audit_accessibility, capture_screenshot, capture_pdf, check_usage. The shared capture_ prefix is used sensibly for the two rendering tools.

    Tool Count5/5

    Five tools is well-scoped for a page-capture/audit service, with no filler. Each tool earns its place and covers a distinct capability.

    Completeness4/5

    Core lifecycle is covered: screenshot, PDF, comparison, accessibility audit, and credit usage. Minor gaps exist (e.g., no HTML/text extraction or element-scoped capture beyond device/full_page params), but agents can work around these.

    Related MCP Connectors

    Related MCP Servers