Skip to main content
Glama
esola-thomas

Documentation MCP Server

by esola-thomas

Related Servers

Alternatives to Documentation MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Lets AI agents search and read a folder of Markdown documentation at query time, exposing heading-level search, whole-page or section retrieval, and page listing as tools and resources over stdio or Streamable HTTP. Can run as a CLI, a hosted endpoint, or a library inside an existing Node or Next.js site.
      3
      273 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI-powered querying and management of documentation through markdown file serving, keyword search, and OpenAI-based Q\&A capabilities. Supports document indexing, analysis, and agent handoffs with rate limiting protection.
      5
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Indexes your project's markdown documentation and exposes it to AI agents via local hybrid search (lexical + semantic) with progressive disclosure tools.
      3
      555 npm
      5
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI-powered querying and serving of markdown documentation with search, Q\&A capabilities, and document analysis. Built for the YC Agents Hackathon with OpenAI integration and rate limiting protection.
      MIT

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools are clearly distinct: search_documentation is full-text, search_by_tags is metadata-based, get_document retrieves content, and navigation tools handle hierarchy. There is slight overlap between search_documentation and search_by_tags, but the descriptions clarify the different search modes.

    Naming Consistency4/5

    Tool names consistently use verb_noun pattern (search_documentation, navigate_to, get_table_of_contents, get_document, get_all_tags). search_by_tags follows the pattern, though 'navigate_to' is slightly less descriptive than the others but still consistent in style.

    Tool Count5/5

    Six tools is well-scoped for a documentation server, covering search, navigation, and metadata retrieval without unnecessary redundancy. Each tool serves a distinct purpose in the documentation workflow.

    Completeness4/5

    The surface covers core documentation needs: full-text search, tag search, navigation, TOC, and document retrieval. Minor gaps include no obvious way to get related documents or search within a specific subtree, but the core workflows are complete.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive