convert_url_to_pdf — webpage to pdf MCP Tool
convert_url_to_pdf
(convert url to pdf) is one of 1 tool on the
webpage to pdf
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call convert_url_to_pdf from your client
- Claude Code webpage to pdf convert_url_to_pdf run in your project directory
- Claude Desktop webpage to pdf convert_url_to_pdf ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor webpage to pdf convert_url_to_pdf ~/.cursor/mcp.json
- VS Code webpage to pdf convert_url_to_pdf .vscode/mcp.json
- Zed webpage to pdf convert_url_to_pdf ~/.config/zed/settings.json
- Windsurf webpage to pdf convert_url_to_pdf ~/.codeium/windsurf/mcp_config.json
- Cline webpage to pdf convert_url_to_pdf ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI webpage to pdf convert_url_to_pdf ~/.gemini/settings.json
- Grok webpage to pdf convert_url_to_pdf .mcp.json (in your project root)
- ChatGPT webpage to pdf convert_url_to_pdf Settings → Connectors → Advanced → Developer mode
- Claude.ai webpage to pdf convert_url_to_pdf Settings → Connectors → Add custom connector
- LangChain webpage to pdf convert_url_to_pdf pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http webpage-to-pdf https://urltopdf.org/api/mcp
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.