Urlsnap Mcp
Give Claude Desktop or Claude Code one MCP to screenshot URLs, export PDFs, and extract markdown without custom Puppeteer scripts.
Overview
dev.urlsnap/urlsnap-mcp is a Build-phase MCP server that screenshots URLs, exports PDFs, and extracts markdown for Claude Desktop and Claude Code via URLSnap.
What is this MCP server?
- Screenshot any URL through URLSnap’s hosted rendering API
- PDF export from URLs for specs, audits, and shareable artifacts
- Markdown extraction for agent-friendly parsing of docs and marketing pages
- stdio npm package urlsnap-mcp v1.0.2 for Claude Desktop and Claude Code
- Mandatory URLSNAP_API_KEY from urlsnap.dev/dashboard
- npm package: urlsnap-mcp
- Published version: 1.0.2
- Transport: stdio
What problem does it solve?
Agents cannot reliably see live web pages, so builders rerun manual screenshots and copy-paste when researching or documenting URLs.
Who is it for?
Indie builders who want fast visual and text captures from URLs inside Claude Code without maintaining browser automation.
Skip if: Fully offline crawls, heavy SPAs needing custom auth flows, or teams avoiding paid capture APIs.
What do I get? / Deliverables
After you add the MCP with an API key, agents return screenshots, PDFs, and markdown from URLs inside the coding session.
- PNG or equivalent screenshots of requested URLs
- PDF exports and markdown text suitable for agent analysis
Recommended MCP Servers
Journey fit
Canonical shelf is Build → agent-tooling because URLSnap is a stdio npm MCP that extends the agent’s capture toolkit. Subphase agent-tooling reflects npm urlsnap-mcp transport and required URLSNAP_API_KEY for managed rendering.
How it compares
Hosted URL capture MCP, not a local Playwright skill or generic curl/HTML parser.
Common Questions / FAQ
Who is dev.urlsnap/urlsnap-mcp for?
Solo builders on Claude Desktop or Claude Code who need screenshots, PDFs, and markdown from URLs through a single MCP integration.
When should I use dev.urlsnap/urlsnap-mcp?
Use it when validating competitors, prototyping with live page references, or generating launch assets from production URLs.
How do I add dev.urlsnap/urlsnap-mcp to my agent?
Install npm package urlsnap-mcp, set URLSNAP_API_KEY from urlsnap.dev/dashboard, and configure the server as stdio in your MCP client.