# pdfzen MCP server

Render PDFs from 45 starter templates or raw HTML. Pay-per-render with USDC via x402.

## Links
- Registry page: https://www.getdrio.com/mcp/site-pdfzen-render
- Repository: https://github.com/yalamber/pdfzen
- Website: https://pdfzen.site

## Install
- Endpoint: https://api.pdfzen.site/mcp
- Auth: Not captured

## Setup notes
- Remote endpoint: https://api.pdfzen.site/mcp

## Tools
- list_starters - List pdfzen's 45 public starter templates — invoices, receipts, contracts, certificates, NDAs, letters, reports, resumes, boarding passes, menus, bank statements, lab reports, lease agreements, performance reviews, and more. Returns an array of { slug, name, description, icon, pageOptions, fonts, dataKeys }. Free, no payment, no auth required. Call this first to discover what fits the user request, then optionally call get_starter to see the expected data shape, then call render_template_to_pdf to produce the PDF. Endpoint: https://api.pdfzen.site/mcp
- get_starter - Fetch the full HTML body, CSS, sampleData, and pageOptions for one starter template by slug. Use this when you need to understand the exact shape of `data` the template expects before calling render_template_to_pdf, or when you want to fork a starter into custom HTML. Free, no payment, no auth required. Endpoint: https://api.pdfzen.site/mcp
- render_template_to_pdf - Render one of the 45 starter templates into a PDF. Returns the PDF as base64-encoded bytes in the tool result. **Settled per call via x402 USDC on Base mainnet — $0.006 per render.** Pass the signed payment authorization in the X-PAYMENT header on the outer POST /mcp HTTP request. If the header is missing, this tool returns a structured PaymentRequirement that x402-aware runtimes (Coinbase Agent Kit, x402-fetch) auto-sign and retry. Your user-supplied `data` is merged ON TOP of the template sampleData, so partial payloads inherit demo defaults — handy for incremental input (e.g. only the customer's name + total, ship the rest as the demo). Endpoint: https://api.pdfzen.site/mcp
- render_html_to_pdf - Render arbitrary Handlebars-flavoured HTML into a PDF. Use only when no starter fits the user request (one-off layouts, custom branding the user described in chat). Prefer render_template_to_pdf when a starter matches — output quality is more predictable. Returns the PDF as base64-encoded bytes. **Settled per call via x402 USDC on Base mainnet — $0.006 per render.** Pass the signed payment in the X-PAYMENT header on the outer POST /mcp request. If missing, returns a PaymentRequirement to sign. Endpoint: https://api.pdfzen.site/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: site.pdfzen
- Version: 1.0.0
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: May 14, 2026
- Source: https://registry.modelcontextprotocol.io