In-depth architectural comparison of the PDF Reader MCP and Purchase requisition MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
PDF Reader MCP
Developer Tools · Local stdio
Quality: 69/100 (Great) | Auth: No auth required
Purchase requisition
Developer Tools · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose PDF Reader MCP if you need specialized Developer Tools tools running via a local process. Choose Purchase requisition if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose PDF Reader MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Document 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]).
outline
Return 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.
read
Read 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.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
PDF Reader MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Purchase requisition belongs to Developer Tools using local stdio subprocess. Select PDF Reader MCP when you need capabilities focused on developer tools and Purchase requisition when you require tools for developer tools.
Search 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".
Purchase requisition Tools (16)
purchase-requisition_create
Create a reusable purchase-requisition: a name, a category, a description
purchase-requisition_item_add
Add a step: the text, a section heading, and whether it is required
purchase-requisition_item_remove
Remove a step and bump the version. Runs already under way keep it
purchase-requisition_show
One purchase-requisition, grouped by section, with a blank printable copy on request
purchase-requisition_list
Every purchase-requisition with its version, step count and how many runs came from it
purchase-requisition_delete
Delete a purchase-requisition. Its runs stay readable, because each carries its own copy
run_start
Start a dated run against a job. The steps are copied into it at this point
run_check
Mark one step pass, fail or na, with who and when and what was found
run_show
The run: every step with its answer, the counts, the failures, and what blocks sign-off
run_list
Runs newest first, filtered by purchase-requisition, status, reference, or only those with failures
run_sign_off
Sign off with a name and a date, which freezes the run
run_status
Reopen a complete run, or abandon one when the job did not happen