Docweave vs pdf-mcp.io
Both Docweave and pdf-mcp.io are MCP-native HTML-to-PDF APIs built for AI agents — you POST HTML and get a PDF back, and an agent can call it as a tool. The real differences are the pricing model, an open-source MCP server, extra sources (template + JSON and URL), and an SSRF guard for URL rendering.
Per-document vs per-page
pdf-mcp.io charges 1 credit for the first page and 0.01 credits for each additional page, so a longer document costs more. Docweave charges one unit per document, regardless of length — your bill doesn't depend on how long each PDF happens to be.
| Document | pdf-mcp.io (per page) | Docweave (per document) |
|---|---|---|
| 1-page invoice | 1.00 credit | 1 document |
| 25-page report | 1.24 credits | 1 document |
| 100-page report | 1.99 credits | 1 document |
Illustrative, based on pdf-mcp.io's published 1 credit + 0.01/extra-page model. Always check both providers' current pricing pages.
Where Docweave differs
| Docweave | pdf-mcp.io | |
|---|---|---|
| MCP server | Open source (npx @docweave/mcp) + hosted | MCP-native (hosted) |
| Pricing model | Per document (flat, any length) | Per page (1 + 0.01/extra page) |
| Sources | HTML, URL, template + JSON | HTML — see provider docs |
| URL rendering | SSRF-guarded, egress-isolated | See provider docs |
| Rendering | Chromium | Chromium (HTML-to-PDF) |
Switching from pdf-mcp.io
The request shape is familiar — POST a source, get a PDF back:
curl https://docweave.dev/api/v1/pdf \
-H "Authorization: Bearer dw_live_your_key" \
-H "Content-Type: application/json" \
-H "Accept: application/pdf" \
-d '{
"source": { "type": "html", "html": "<h1>Invoice #1024</h1>" },
"options": { "format": "A4" }
}' \
--output invoice.pdfFAQ
Is pdf-mcp.io priced per page or per document?
pdf-mcp.io uses prepaid credits: the first page of a document costs 1 credit and each additional page adds 0.01 credits, so your cost scales with document length. Docweave bills per document — a one-page receipt and a 100-page report are billed the same way. Check pdf-mcp.io's pricing page for current numbers.
Are both usable from an AI agent via MCP?
Yes. Both are MCP-native, so an agent can generate a PDF with a tool call instead of raw HTTP. The differences are Docweave's open-source MCP server (npx @docweave/mcp), template + JSON and URL sources, per-document pricing, and an SSRF guard on URL rendering.
Does Docweave protect against SSRF when rendering a URL?
Yes. Rendering an arbitrary URL is a textbook SSRF primitive — especially when an autonomous agent supplies the URL. Docweave validates and guards URL targets and runs rendering egress-isolated, so an agent can call it on untrusted input safely.
Can I switch from pdf-mcp.io to Docweave easily?
The request shape is familiar: POST a source (HTML, a URL, or a template + JSON) and get a PDF back. Docweave also honors an idempotency key so a retried call never double-generates or double-bills the same document.
Per-document pricing, an open-source MCP server, and SSRF-safe URL rendering.
Get an API key