html_to_pdf — Printwren: HTML to PDF and URL to PDF (real Chrome) MCP Tool
html_to_pdf
(html to pdf) is one of 2 tools on the
Printwren: HTML to PDF and URL to PDF (real Chrome)
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call html_to_pdf from your client
- Claude Code Printwren: HTML to PDF and URL to PDF (real Chrome) html_to_pdf run in your project directory
- Claude Desktop Printwren: HTML to PDF and URL to PDF (real Chrome) html_to_pdf ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Printwren: HTML to PDF and URL to PDF (real Chrome) html_to_pdf ~/.cursor/mcp.json
- VS Code Printwren: HTML to PDF and URL to PDF (real Chrome) html_to_pdf .vscode/mcp.json
- Zed Printwren: HTML to PDF and URL to PDF (real Chrome) html_to_pdf ~/.config/zed/settings.json
- Windsurf Printwren: HTML to PDF and URL to PDF (real Chrome) html_to_pdf ~/.codeium/windsurf/mcp_config.json
- Cline Printwren: HTML to PDF and URL to PDF (real Chrome) html_to_pdf ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Printwren: HTML to PDF and URL to PDF (real Chrome) html_to_pdf ~/.gemini/settings.json
- Grok Printwren: HTML to PDF and URL to PDF (real Chrome) html_to_pdf .mcp.json (in your project root)
- ChatGPT Printwren: HTML to PDF and URL to PDF (real Chrome) html_to_pdf Settings → Connectors → Advanced → Developer mode
- Claude.ai Printwren: HTML to PDF and URL to PDF (real Chrome) html_to_pdf Settings → Connectors → Add custom connector
- LangChain Printwren: HTML to PDF and URL to PDF (real Chrome) html_to_pdf pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http html-to-pdf https://printwren.cybermax-tools.workers.dev/mcp?via=mcp-registryOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 26 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.