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