EveryPage vs PDF Reader MCP

A side-by-side look at the EveryPage and PDF Reader MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

EveryPage logoEveryPageMarketing · Local subprocess (stdio)Share PDFs as tracked links and see who read them, how far they got, and where they stopped.43FairAuth: not declaredPDF Reader MCP logoPDF Reader MCPSearch & Data ExtractionEvidence-first PDF MCP. Agent Document Twin with citeable page+bbox evidence.61GoodAuth: no auth required

Verdict: choose EveryPage for marketing work as a local process; choose PDF Reader MCP for search & data extraction. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

EveryPage logoChoose EveryPage when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: EVERYPAGE_API_KEY.
Explore EveryPage

PDF Reader MCP logoChoose PDF Reader MCP when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • Its auth model fits you: No auth required.
  • You want tools like inspect, outline, read.
Explore PDF Reader MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecEveryPage logoEveryPagePDF Reader MCP logoPDF Reader MCP
CategoryMarketingSearch & Data Extraction
Quality signal43/100 · Fair61/100 · Good
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsEVERYPAGE_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars01,050
Directory activity 3 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
ToolsNot listed4

Tools & capabilities

EveryPage tools

No tool names declared yet. Check the project README from the listing page.

PDF Reader MCP tools 4

  • inspectDocument and media evidence when Markdown is not enough. video_timeline (bounded scene/cue timeline) and render_frame (actual decoded frames), and cite_check (quote/location support, not semantic truth), are anymd Pro; PDF operations: inspect (page facts, metadata), render_page (PNG images), extract_regions (crop bounding boxes), ocr_pages / analyze_regions (configured OCR or vision provider), structure (JSON with document map, elements, geometry; profile quality|research adds trust and accessibility reports), compare (page-level diff of sources[0] vs sources[1]).
  • outlineReturn a document heading tree with stable node ids, title paths, page/slide/chapter ranges and Markdown byte ranges. PDF bookmarks or detected headings, Word headings, PowerPoint slides, EPUB chapters and headings, HTML and Markdown. format json (default) or tree. Pass a node id to read to fetch that section.
  • readRead any document as clean Markdown: PDF, Word (DOCX), PowerPoint (PPTX), Excel (XLSX/XLS/ODS), CSV, EPUB, HTML or a web URL, Markdown/text, images (metadata + OCR), audio/video (metadata, chapters, subtitles). Pages/slides/sheets carry <!-- page N --> style markers for citation. Long documents stop at max_tokens (default 20000) and end with a cursor to continue; choose pages with pages: "1-5,8". A directory returns its readable files.
  • searchSearch documents for text: one file, many files, whole directories (recursive, .gitignore aware), or URLs, across every format read supports. Returns each hit as file + page/slide/sheet + a snippet with the match in bold. mode auto (default) finds the exact phrase and falls back to BM25-ranked passages when there is none; literal or ranked force one. Narrow directories with glob, e.g. "*.pdf".

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

EveryPage

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "everypage": {
      "command": "npx",
      "args": [
        "-y",
        "everypage-mcp"
      ],
      "env": {
        "EVERYPAGE_API_KEY": "YOUR_EVERYPAGE_API_KEY_HERE"
      }
    }
  }
}

PDF Reader MCP

No confirmed install command for PDF Reader MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

EveryPage is categorized under Marketing and uses a local stdio subprocess. PDF Reader MCP belongs to Search & Data Extraction and uses an install path we have not confirmed yet. Pick EveryPage for marketing work and PDF Reader MCP for search & data extraction.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. PDF Reader MCP has no confirmed install command yet — follow its own setup instructions.

EveryPage has no declared pricing — check the project's own site. PDF Reader MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add everypage and pdf-reader-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, EveryPage has a quality signal of 43/100 (Fair) with 3 views, 0 installs and 0 GitHub stars. PDF Reader MCP has 61/100 (Good) with 6 views, 0 installs and 1,050 GitHub stars.