io.github.CloudCorpRecords/bookbind vs io.github.zp130221/pdfedit-mcp
io.github.CloudCorpRecords/bookbind is an MCP server published by CloudCorpRecords. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.zp130221/pdfedit-mcp is an MCP server published by zp130221. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-11. 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 |  io.github.CloudCorpRecords/bookbind |  io.github.zp130221/pdfedit-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.10 Downloads/month (npm): 1 999 Downloads/week (npm): 1 160 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.1.15 Downloads/month (npm): 1 999 Downloads/week (npm): 1 160 Forks (GitHub): 0 Stars (GitHub): 0 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 | io.github.CloudCorpRecords/bookbind | io.github.zp130221/pdfedit-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-11-10 |
| Where it runs (differs) | On your machine (@reneturcios/bookbind) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/cloudcorprecords/bookbind | github.com/zp130221/pdfedit-mcp |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-11-04 | 2026-10-16 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 21 h 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
io.github.CloudCorpRecords/bookbind
EPUB and PDF ebook tools: merge, split, compress, convert, edit metadata, validate and covers.
io.github.zp130221/pdfedit-mcp
Edit text inside existing PDFs: replace, delete, redact, insert, fill forms; original fonts kept.
How to run each
io.github.CloudCorpRecords/bookbind As a local MCP server: npm package
claude mcp add --transport stdio bookbind -- npx -y @reneturcios/bookbind mcpio.github.zp130221/pdfedit-mcp As a remote MCP server
claude mcp add --transport http pdfedit-mcp https://pdfedit-mcp-remote.niubai-pdfedit-remote-worker.workers.dev/mcpRequires: PDFEDIT_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.zp130221/pdfedit-mcp has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of io.github.CloudCorpRecords/bookbind nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
The marketplaces of io.github.CloudCorpRecords/bookbind publish no settings it asks for, so we do not compare settings.
What it can do: io.github.CloudCorpRecords/bookbind · What it can do: io.github.zp130221/pdfedit-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.