Ext Ops Panel
Open dashboard
Comparison

com.makespdf/makespdf vs io.github.kmalakoff/mcp-pdf

com.makespdf/makespdf is an MCP server published by makespdf.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.kmalakoff/mcp-pdf is an MCP server published by kmalakoff. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
Marketplacecom.makespdf/makespdfio.github.kmalakoff/mcp-pdf
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 1.0.3
Downloads/month (npm): 4 241
Downloads/week (npm): 1 421
Forks (GitHub): 3
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

com.makespdf/makespdf vs io.github.kmalakoff/mcp-pdf
Factcom.makespdf/makespdfio.github.kmalakoff/mcp-pdf
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub2
Forks (GitHub) (differs)No figure on GitHub3
Last releaseNot publishedNot published
Where it runs (differs)Remote server (makespdf.com/api/v1/mcp)On your machine (@mcp-z/mcp-pdf)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/mcp-z/mcp-pdf
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 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

com.makespdf/makespdf

In its own words, on Official MCP Registry:

Compliant PDFs (PDF/A-2A + PDF/UA-1) from markdown or a compact DSL - fast, no headless browser.

io.github.kmalakoff/mcp-pdf

In its own words, on Official MCP Registry:

MCP server for PDF generation using PDFKit

How to run each

com.makespdf/makespdf As a remote MCP server

Claude Code
claude mcp add --transport http makespdf https://makespdf.com/api/v1/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

io.github.kmalakoff/mcp-pdf As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mcp-pdf -- npx -y @mcp-z/mcp-pdf

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

Only com.makespdf/makespdf 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 com.makespdf/makespdf publish no settings it asks for, so we do not compare settings.

What it can do: com.makespdf/makespdf · What it can do: io.github.kmalakoff/mcp-pdf · 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.

Where the data comes from: how the catalog is built