Skip to main content
Glama

Related Servers

Alternatives to everypage-mcp

  • A
    license
    B
    quality
    D
    maintenance
    An MCP server that lets AI assistants read and visually analyze local documents — PDFs, Excel spreadsheets, CSV files, Word documents, PowerPoint presentations, and images.
    4
    21 npm
    49 PyPI
    MIT

Related Servers

  • A
    license
    A
    quality
    D
    maintenance
    An 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.
    4
    22 npm
    1
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    A 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.
    10
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    An 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.
    -
  • A
    license
    Not graded
    quality
    D
    maintenance
    MCP 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 npm
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    MCP server that converts PDFs to Markdown, reconstructing hidden hyperlinks and extracting images in reading order for AI agents.
    MIT

TDQS

A4.2/5.0

Scored across 15 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues