url_to_screenshot — url-to-pdf MCP Tool
url_to_screenshot
(url to screenshot) is one of 4 tools on the
url-to-pdf
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call url_to_screenshot from your client
- Claude Code url-to-pdf url_to_screenshot run in your project directory
- Claude Desktop url-to-pdf url_to_screenshot ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor url-to-pdf url_to_screenshot ~/.cursor/mcp.json
- VS Code url-to-pdf url_to_screenshot .vscode/mcp.json
- Zed url-to-pdf url_to_screenshot ~/.config/zed/settings.json
- Windsurf url-to-pdf url_to_screenshot ~/.codeium/windsurf/mcp_config.json
- Cline url-to-pdf url_to_screenshot ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI url-to-pdf url_to_screenshot ~/.gemini/settings.json
- Grok url-to-pdf url_to_screenshot .mcp.json (in your project root)
- ChatGPT url-to-pdf url_to_screenshot Settings → Connectors → Advanced → Developer mode
- Claude.ai url-to-pdf url_to_screenshot Settings → Connectors → Add custom connector
- LangChain url-to-pdf url_to_screenshot pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http url-to-pdf https://url-pdf.hammbox.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 8 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.