pdfs.build vs co.leafwright/leafwright
pdfs.build is an MCP server published by pdfs.build. Marketplaces we read that list it: 1 (Official MCP Registry). co.leafwright/leafwright is an MCP server published by leafwright.co. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  pdfs.build |  co.leafwright/leafwright |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.2.4 Downloads/month (npm): 202 Downloads/week (npm): 37 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | pdfs.build | co.leafwright/leafwright |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (backend.pdfs.build/mcp) | Remote server (leafwright.co/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 2 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/tactic-systems/leafwright |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago, requires a key | Responded 3 days ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
pdfs.build
Design, publish and render PDF templates with Typst. Full template lifecycle over MCP.
co.leafwright/leafwright
Render HTML, URLs, and templates to PDF. AI drafts templates and fixes them from logs.
How to run each
pdfs.build As a remote MCP server
claude mcp add --transport http pdfs-build https://backend.pdfs.build/mcpco.leafwright/leafwright As a remote MCP server
claude mcp add --transport http leafwright https://leafwright.co/mcpRequires: LEAFWRIGHT_API_KEY (secret), LEAFWRIGHT_MCP_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of pdfs.build publish no settings it asks for, so we do not compare settings.
What it can do: pdfs.build · What it can do: co.leafwright/leafwright · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.