Skip to main content
Glama
ArtiPyHeart

mcp-ebook-read

by ArtiPyHeart
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-ebook-read

No user-submitted related servers found.

    Related Servers

    • opds-mcp

      pastukhov
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that lets an LLM browse, search, and download books from OPDS catalogs (e.g., Project Gutenberg, Standard Ebooks) using tools for feed navigation, full-text search, and acquisition link downloads.
      4
      1
      AGPL 3.0

    • pdf-context

      mematcha
      A
      license
      A
      quality
      B
      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

    • pdf-agent-mcp

      sanhua1
      F
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that extracts text-layer content from PDF files, enabling AI agents to inspect, extract text, outlines, and page content.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 29 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear separation between library-level, document-level, and component-level operations (e.g., library_explore vs. document_explore, pdf_list_figures vs. pdf_list_tables). Overlap is minimal and resolved by descriptive names and context.

    Naming Consistency4/5

    Tools follow a consistent snake_case with domain prefixes (document_, library_, pdf_, epub_, storage_, eval_), and most use a verb_noun pattern. Minor variations like 'doctor_health_check' and 'get_outline' vs. 'read_outline_node' break perfect uniformity but remain predictable.

    Tool Count2/5

    With 29 tools, the set exceeds the 25-tool threshold for 'too many'. While the domain is complex, many tools could be consolidated (e.g., combining pdf_list_figures/images/tables into a single listing tool with type parameter), making the surface overly large for agents.

    Completeness4/5

    The tool set covers the full lifecycle: library scanning, document ingest, exploration, component-level reading (figures, tables, etc.), storage maintenance, and evaluation. Minor gaps exist, like no direct tool for top-level document metadata retrieval, but core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources