Side-by-Side Model Context Protocol Comparison
PDF Reader MCP vs Umami MCP
In-depth architectural comparison of the PDF Reader MCP and Umami MCP 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
Umami MCP
Developer Tools · Local stdio
Quality: 55/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 Umami MCP 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).
- Primary tools included: inspect, outline, read.
Choose Umami 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).
- You have access to required keys:
UMAMI_URL, UMAMI_USERNAME, UMAMI_PASSWORD, UMAMI_MCP_MODE, UMAMI_MCP_ALLOW_DESTRUCTIVE, UMAMI_MCP_ENV_FILE, UMAMI_MCP_OAUTH. - Primary tools included: umami_list_websites, umami_get_website, umami_create_website.
Feature & Specification Comparison
Tools & Capabilities Breakdown
PDF Reader MCP Tools (4)
inspect
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 Configuration
Umami MCP Configuration