everypage-mcp
OfficialRelated Servers
Alternatives to everypage-mcp
- AlicenseBqualityDmaintenanceAn MCP server that lets AI assistants read and visually analyze local documents — PDFs, Excel spreadsheets, CSV files, Word documents, PowerPoint presentations, and images.421 npm49 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceUniversal MCP server for extracting text from various document formats including PDF, Excel, Word, CSV, and more, with support for streaming, limits, and markdown conversion.3MIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for AI-assisted PDF reading with pagination, search, and page navigation.3 npmMIT
- AlicenseAqualityDmaintenanceAn MCP server that enables AI assistants to read, search, and analyze PDF files from local paths or URLs. It provides tools for extracting specific page ranges, searching for terms, and retrieving document metadata.422 npm1MIT
- AlicenseAqualityDmaintenanceA local-first MCP server that ingests PDFs, extracts structure, and provides semantic search and sequential navigation tools for AI clients to query and learn from documents.10MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that provides AI-powered document processing and search capabilities, including PDF summarization, text extraction, metadata retrieval, and web search via Google Custom Search.-

aidocx-mcp-serverofficial
AlicenseNot gradedqualityDmaintenanceMCP server for AiDocX, enabling AI assistants to create, upload, manage, and analyze business documents and presentation decks, with support for various document types and AI-powered generation.60 npmMIT- AlicenseNot gradedqualityDmaintenanceMCP server that converts PDFs to Markdown, reconstructing hidden hyperlinks and extracting images in reading order for AI agents.MIT
TDQS
Scored across 15 tools
Most tools target clearly distinct resources and actions (files, variants, webhooks, account). A few pairs overlap in surface intent — get_readership vs list_events (both about reading activity) and delete_variant vs update_variant (both can revoke a link) — but the descriptions draw the boundaries clearly enough to disambiguate.
All tools use a consistent everypage_ prefix with a snake_case verb_noun pattern (list_files, get_file, update_file_settings, create_variants, list_webhooks). Minor wording differences like share_pdf and manage_webhook don't break the predictable convention.
15 tools is well within the well-scoped range and each earns its place: file CRUD, variant lifecycle, webhooks, analytics, and account. No obvious redundancy or filler.
Covers the full document lifecycle (upload/share, list, get, settings, replace, delete/trash) plus variants, webhooks, readership, events, and account info. Minor gaps exist (e.g. no explicit restore-from-trash tool despite delete mentioning it, no per-variant get), but core workflows are covered.