Docweave vs Sejda
Docweave is an MCP-native PDF/document-generation API: one REST call turns HTML, a URL, or a template + JSON into a PDF. If you are evaluating Sejda's HTML-to-PDF API, the biggest difference is that Docweave ships an open-source MCP server so AI agents can call generate_pdf directly, and it bills per document rather than per page or conversion credit.
Sejda is a broad suite of online PDF tools — merge, split, compress, edit, and convert — that also exposes an HTML-to-PDF API. Docweave is narrower and more specialized: it focuses on generating documents (HTML, a URL, or a template + JSON) reliably for developers, no-code automations, and AI agents.
Where Docweave differs
| Docweave | Sejda | |
|---|---|---|
| MCP-native tool | generate_pdf, open source (npx @docweave/mcp) | See provider docs/pricing |
| Pricing model | Per document | See provider docs/pricing |
| Sources | HTML, URL, template + JSON | HTML, URL (see provider docs) |
| Rendering | Chromium | See provider docs |
Switching from Sejda
The request shape is simple — 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", "margin": "20mm" }
}' \
--output invoice.pdfFAQ
Is Docweave a drop-in Sejda alternative?
For HTML-to-PDF, the shape is familiar: you send a source and get a PDF back. Docweave accepts raw HTML, a URL, or a template + JSON, renders with Chromium, and returns the file over one REST call. The main additions are a first-class MCP server and per-document pricing.
What does Docweave offer that Sejda's tool suite does not?
An open-source, MCP-native generate_pdf tool (npx @docweave/mcp) that any MCP client — Claude, Cursor, and others — can call directly, plus template + JSON rendering so you can store a layout once and bind data into it, rather than assembling documents through a general-purpose tool suite.
How does pricing compare?
Sejda's tools and API have their own plan structure — check the provider's current docs/pricing for exact numbers. Docweave bills per document, so a long report and a one-page receipt are priced the same way.
Can I use Docweave from an AI agent?
Yes. Add the Docweave MCP server and your agent gets a generate_pdf tool — one tool call instead of HTTP plumbing, with built-in idempotency (an idempotencyKey) so retries never double-generate the same document.
Try the MCP-native PDF API.
Get an API key