Skip to main content
Glama
shenyimings

DocNav-MCP

by shenyimings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to DocNav-MCP

No user-submitted related servers found.

    Related Servers

    • mcp-document-assistant

      SamamaSaleem
      F
      license
      A
      quality
      C
      maintenance
      A local AI document assistant MCP server that enables listing, reading, and editing documents via tools, resources, and prompts, allowing LLMs to manage document workflows through natural language.
      3
      -
    • MinerU Document Explorer by opendatalab

      MinerU Document Explorerofficial

      opendatalab
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to search, deep-read, and build knowledge bases from Markdown, PDF, DOCX, and PPTX documents via MCP tools for retrieval, document navigation, and ingestion.
      27 npm
      641
      MIT

    • DocFill Agent MCP Server

      nicomathieu
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables LLM agents to read, understand, and fill DOCX templates while preserving formatting like bold labels and fonts. It exposes tools for document upload, AST inspection, editing, and validation.
      1
      MIT

    • Zileo Docs

      assistance-micro-design
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for indexing, semantic search, and generation of multi-format documents. Exposes 13 tools over JSON-RPC 2.0 so an LLM can search your local PDF, Excel, and Word files, and create or edit Excel and Word documents.
      AGPL 3.0
    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

    A3.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: list_documents enumerates loaded docs, load_document/remove_document manage the document lifecycle, get_outline provides structure, navigate_section gives context, read_section extracts content, search_document finds text, and get_document_stats offers metadata. An agent can easily differentiate them based on their specific actions and targets.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, such as list_documents, load_document, get_outline, and navigate_section. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions across the eight tools.

    Tool Count5/5

    With 8 tools, this server is well-scoped for document navigation and analysis, covering core operations like loading, listing, navigating, reading, searching, and removing documents, along with metadata and outline retrieval. Each tool earns its place without redundancy, making the count ideal for the domain.

    Completeness5/5

    The tool set provides complete CRUD/lifecycle coverage for document navigation: load_document (create), list_documents (read), remove_document (delete), and operations for analysis (get_outline, navigate_section, read_section, search_document, get_document_stats). There are no obvious gaps, ensuring agents can perform all essential tasks without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources