Skip to main content
Glama
apideck-libraries

docs-mcp

Official
by apideck-libraries
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to docs-mcp

No user-submitted related servers found.

    Related Servers

    • compendio-mcp

      RuloGB
      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
      471 npm
      5
      MIT

    • DocDex

      trushantgautam
      F
      license
      Not graded
      quality
      C
      maintenance
      Turns a directory of markdown documentation into searchable, citable tools for AI assistants, enabling targeted retrieval of specific sections with stable references.
      -

    • search-docs

      otolab
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to search local Markdown documents using natural language, with automatic indexing and section-level retrieval.
      10
      2 npm
      1
      MIT

    • Documentation MCP Server

      esola-thomas
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to navigate and query hierarchical documentation structures, supporting markdown files with YAML metadata and OpenAPI 3.x specifications. It features intelligent full-text search, metadata filtering, and a built-in web interface for both human and AI-driven documentation access.
      6
      MIT
    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

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a clearly distinct operation: list_docs for browsing structure, search_docs for full-text queries, and get_doc for retrieving content by path. The descriptions explicitly cross-reference each other, reinforcing the intended workflow.

    Naming Consistency5/5

    All three tools follow the same noun-prefixed pattern with a consistent verb (get_doc, list_docs, search_docs), using uniform snake_case throughout. No deviations or mixing of conventions.

    Tool Count4/5

    Three tools cover the core read-only documentation workflow (browse, search, fetch) without redundancy. Slightly lean, but each tool earns its place and the scope is well-defined.

    Completeness4/5

    The browse/search/retrieve lifecycle is fully covered for consuming docs, with get_doc supporting both whole-page and section retrieval. Writing or indexing operations are absent, but may be intentionally out of scope for a read-oriented server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources