Skip to main content
Glama
Sign In
docs-mcp

docs-mcp

Official
by apideck-libraries
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to docs-mcp

No user-submitted related servers found.

    Related Servers

    • Lore

      ai-pipes
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search and ask questions across versioned service documentation, retrieve documents and diffs, and find related docs with cited answers over Streamable HTTP, SSE, or stdio.
      296 npm
      MIT

    • compendio-mcp

      RuloGB
      A
      license
      A
      quality
      B
      maintenance
      Indexes your project's markdown documentation and exposes it to AI agents via local hybrid search (lexical + semantic) with progressive disclosure tools.
      3
      81 npm
      5
      MIT
    • Helpdock MCP Server

      Helpdock MCP Serverofficial

      flisk-sh
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets coding agents search a local Markdown docs folder, ask questions answered with linked source passages, and add or replace pages. Backed by Postgres full-text search with no vector database required.
      4 npm
      1
      MIT

    • DocDex

      trushantgautam
      F
      license
      Not graded
      quality
      D
      maintenance
      Turns a directory of markdown documentation into searchable, citable tools for AI assistants, enabling targeted retrieval of specific sections with stable references.
      -
    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.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: search_docs performs full-text search, get_doc retrieves a specific page or section by path, and list_docs browses page metadata. The descriptions explicitly clarify when to use each and how they relate, leaving little room for misselection.

    Naming Consistency5/5

    All three tools follow a consistent snake_case verb_noun convention: search_docs, get_doc, list_docs. The pattern is predictable and readable across the entire set.

    Tool Count5/5

    Three tools are well-scoped for a documentation server: search, retrieve, and list form a compact and complete read-only surface. No tool feels redundant or missing at this scope.

    Completeness5/5

    For a read-only documentation server, the surface covers discovery (list_docs), search (search_docs), and retrieval of full pages or sections (get_doc). There are no obvious operational gaps for the stated purpose.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources