Skip to main content
Glama

Related Servers

Alternatives to oss-docs-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to fetch current, version-accurate library documentation at request time instead of relying on training memory, with search for answering questions and full-fidelity retrieval of pages or specific declarations. Supports bare or module-path library names, version pinning, and disambiguation when names collide.
      825 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search a daily-refreshed index of official documentation and read whole sections of it, so answers come from current pages with citations. Covers Claude Code, Cursor, Codex and MCP through two tools over MCP or REST.
      2
      MIT

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct role in a clear workflow: list projects/versions, search docs, inspect page structure, read chunk text, and compare versions. Search_docs, get_page_outline, and read_chunks all concern documentation content, but their descriptions make the progression from discovery to outline to full text unambiguous.

    Naming Consistency4/5

    All names use consistent snake_case, and most follow a readable verb_noun pattern such as list_projects, search_docs, and read_chunks. The only minor deviation is whats_new, which is still understandable but not structurally aligned with the rest.

    Tool Count5/5

    Six tools is well-scoped for a documentation search and retrieval server. Each tool occupies a distinct step in the workflow, and there are no obviously redundant or missing helper tools.

    Completeness4/5

    The surface covers project/version discovery, keyword search, page outlining, full-chunk retrieval, and cross-version change tracking, which covers the core documentation workflow well. A direct page-listing or full-page retrieval tool would close a minor discovery gap, but agents can work around it via search and outlines.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data