Ext Ops Panel
Open dashboard
Comparison

EasyAccessPDF vs PDF Reader (PDF Agent Stack)

EasyAccessPDF is an MCP server published by luotwo. Marketplaces we read that list it: 1 (Official MCP Registry). PDF Reader (PDF Agent Stack) is an MCP server published by shuji-bonji. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-07. 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
MarketplaceEasyAccessPDFPDF Reader (PDF Agent Stack)
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.22.0
Downloads/month (npm): 854
Downloads/week (npm): 113
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.22.0
Downloads/month (npm): 854
Downloads/week (npm): 113
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

EasyAccessPDF vs PDF Reader (PDF Agent Stack)
FactEasyAccessPDFPDF Reader (PDF Agent Stack)
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub)00
Last release (differs)Not published2026-11-06
Where it runs (differs)Remote server (easyaccesspdf.com/wp-json/easy/v1/mcp)On your machine (@shuji-bonji/pdf-reader-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedMIT
Repository (differs)github.com/luotwo/easyaccesspdf-mcpgithub.com/shuji-bonji/pdf-reader-mcp
Changes in the last 7 days (differs)012
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Status out of date: last check 46 h ago returned HTTP 200no 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

EasyAccessPDF

In its own words, on Official MCP Registry:

PDF accessibility checks (veraPDF PDF/UA-1), auto-fix and Markdown conversion. EU-hosted.

PDF Reader (PDF Agent Stack)

In its own words, on Official MCP Registry:

Read PDF internals: text, structure, fonts, signatures and tags, with what was not read declared.

How to run each

EasyAccessPDF As a remote MCP server

Claude Code
claude mcp add --transport http easyaccesspdf-mcp https://easyaccesspdf.com/wp-json/easy/v1/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

PDF Reader (PDF Agent Stack) As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio pdf-reader-mcp -- npx -y @shuji-bonji/pdf-reader-mcp

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

Only EasyAccessPDF 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

Neither one's marketplaces publish the settings it asks for.

What it can do: EasyAccessPDF · What it can do: PDF Reader (PDF Agent Stack) · 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.

Where the data comes from: how the catalog is built