getsnap-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GETSNAP_API_KEY | Yes | Your getSnap API key. Required; without it the server exits immediately. | |
| GETSNAP_BASE_URL | No | The base URL for the getSnap API. | https://api.getsnap.dev |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| capture_screenshotA | 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. |
| capture_pdfA | 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. |
| compare_pagesA | 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. |
| audit_accessibilityA | 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. |
| check_usageA | How many credits are used and remaining on this key this period. Free - spends no credit. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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).
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.
Five tools is well-scoped for a page-capture/audit service, with no filler. Each tool earns its place and covers a distinct capability.
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.