Ext Ops Panel
Open dashboard
Comparison

prince-pdf-claude vs PDFCrowd PDF Export

prince-pdf-claude is a plugin bundle for AI coding tools published by yeslogic. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). PDFCrowd PDF Export is an MCP server published by pdfcrowd. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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

Where each is published
Marketplaceprince-pdf-claudePDFCrowd PDF Export
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.2.2
Downloads/month (npm): 223
Downloads/week (npm): 37
Forks (GitHub): 0
Stars (GitHub): 2
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

prince-pdf-claude vs PDFCrowd PDF Export
Factprince-pdf-claudePDFCrowd PDF Export
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (prince.cloud/mcp)On your machine (pdfcrowd-mcp-pdf-export)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
Licence (differs)Not statedMIT
Repository (differs)github.com/yeslogic/prince-pdf-claudegithub.com/pdfcrowd/pdfcrowd-mcp-pdf-export
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 5 days agono remote endpoint we check

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

prince-pdf-claude

In its own words, on Claude Code: claude-plugins-community:

Convert HTML, Markdown, and XML documents to high-quality PDF using the Prince formatting engine.

PDFCrowd PDF Export

In its own words, on Official MCP Registry:

Create polished, professional PDFs from a single prompt. Documentation, reports, charts, and more.

How to run each

prince-pdf-claude As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install prince-pdf-claude@claude-community

PDFCrowd PDF Export As a local MCP server: npm package

Claude Code
claude mcp add --env "PDFCROWD_API_KEY=<YOUR_PDFCROWD_API_KEY>" --transport stdio pdfcrowd-mcp-pdf-export -- npx -y pdfcrowd-mcp-pdf-export

Requires: PDFCROWD_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only prince-pdf-claude has a remote endpoint we 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 prince-pdf-claude publish no settings it asks for, so we do not compare settings.

What it can do: prince-pdf-claude · What it can do: PDFCrowd PDF Export · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built