PDF Reader MCP vs Sitelemetry — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
PDF Reader MCP vs Sitelemetry
In-depth architectural comparison of the PDF Reader MCP and Sitelemetry 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
Sitelemetry
Developer Tools · Remote HTTP/SSE
Quality: 52/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 Sitelemetry if your workspace requires Developer Tools integration with remote web transport. 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, Sitelemetry belongs to Developer Tools using remote streaming HTTP/SSE transport. Select PDF Reader MCP when you need capabilities focused on developer tools and Sitelemetry 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".
Sitelemetry Tools (7)
audit_security
Security posture of a website: public checks such as DNS, e-mail authentication records, TLS and HTTP security headers on any target; on a verified host, the protected and active checks your plan includes.
audit_seo
Technical SEO crawl: crawlability, indexation, titles and meta tags, headings, canonical tags, structured data, broken internal links, redirect chains and AI-crawler policy.
audit_ai_visibility
How ready a site's content is to be found and cited by AI search and LLM assistants: entity clarity, answerability, source signals, llms.txt and AI-crawler policy.
audit_integrations
Analytics, tag manager, marketing pixel, site verification and consent setup detected from the site's HTML and headers.
audit_accessibility
WCAG 2.2-oriented checks of the static HTML: image alternatives, form labels, heading structure, landmarks, contrast signals, language attribute and more.
audit_performance
Performance and Core Web Vitals through Google PageSpeed Insights: LCP, INP, CLS, FCP, TTFB and the top improvement opportunities.
audit_full
Every audit area the connected account includes, in one call, with a combined score across the measured areas.