PDF Reader (@Sylphlab/Pdf MCP Server

πŸ“„ The PDF intelligence layer for AI agents β€” Agent Document Twin, evidence-first extraction, visual crops, OCR provenance, trust reports, and

Local serverstdioTypeScript

What is the PDF Reader (@Sylphlab/Pdf MCP server?

πŸ“„ The PDF intelligence layer for AI agents β€” Agent Document Twin, evidence-first extraction, visual crops, OCR provenance, trust reports, and benchmark-gated releases. MCP server for Claude, Cursor, VS Code, and any MCP client. The pdf reader (@sylphlab/pdf mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 10 defined tools rather than through you.

What it actually does

Turn PDFs into structured text, tables, OCR, visual evidence, and page-level citations β€” locally β€” via SDK, CLI, or MCP.

Adding it to your client

The server ships on npm as @sylphx/pdf-reader-mcp, so your MCP client can launch it on demand β€” there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

  • Export β€” @sylphx/pdf-reader-mcp/sdk β†’ Citra (read / search / evidence)
  • Roadmap β€” ** idiomatic high-level @sylphx/citra package name + richer typed SDK; semantics stay isomorphic with CLI/MCP
  • Doc β€” Purpose
  • Platform β€” Native package (auto optionalDependency)
  • read_pdf β€” Smart default: markdown, tables, structure, OCR, citations
  • search_pdf β€” Find page + snippet matches before deep reading
  • pdf_evidence β€” Crops, renders, inspect, focused evidence ops
  • Mode β€” What it measures
  • persistent_warm β€” long-lived server, repeated identical local read_pdf after warm-up
  • startup_inclusive β€” spawn + initialize + one task

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch PDF Reader (@Sylphlab/Pdf.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the pdf reader (@sylphlab/pdf mcp server does with a few real requests.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" β€” permissions, credentials, and how much of your context its toolset consumes. PDF Reader (@Sylphlab/Pdf's toolset β€” Export, Roadmap, Doc and 7 more β€” is a fair guide to whether it matches your workflow. It is maintained by sylphlab; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against PDF Reader (@Sylphlab/Pdf's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
Export@sylphx/pdf-reader-mcp/sdk β†’ Citra (read / search / evidence)
Roadmap** idiomatic high-level @sylphx/citra package name + richer typed SDK; semantics stay isomorphic with CLI/MCP
DocPurpose
PlatformNative package (auto optionalDependency)
read_pdfSmart default: markdown, tables, structure, OCR, citations
search_pdfFind page + snippet matches before deep reading
pdf_evidenceCrops, renders, inspect, focused evidence ops
ModeWhat it measures
persistent_warmlong-lived server, repeated identical local read_pdf after warm-up
startup_inclusivespawn + initialize + one task

How to install the PDF Reader (@Sylphlab/Pdf MCP server

{
  "mcpServers": {
    "pdf-reader-mcp-sylphlab": {
      "command": "npx",
      "args": ["-y", "@sylphx/pdf-reader-mcp"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • β€œUse PDF Reader (@Sylphlab/Pdf to Export.”
  • β€œUse PDF Reader (@Sylphlab/Pdf to Roadmap.”
  • β€œUse PDF Reader (@Sylphlab/Pdf to Doc.”

Frequently asked questions

It is a multi‑layer output (lossless, visual, semantic, evidence, agent) that keeps the PDF readable by agents while preserving the provenance needed to verify answers – page numbers, bounding boxes, crop IDs, and extraction methods.