Skip to main content
Glama
glassBead-tc

MCP Documentation Server

by glassBead-tc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to MCP Documentation Server

No user-submitted related servers found.

    Related Servers

    • docs-mcp

      base-kit
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a local MCP server for searching and retrieving documentation from 22+ open-source projects, enabling AI coding assistants to access up-to-date docs without network dependency.
      6 npm
      2
      MIT

    • mcp_for_agents

      chineidu
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables building local, offline MCP servers that expose open-source package documentation to AI agents, with tools to list doc sources, search docs, and retrieve doc content over stdio.
      MIT

    • MCP SpecNavigator

      kayaozkur
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables intelligent navigation and exploration of the Model Context Protocol specification through dynamic markdown tree generation, section search, content retrieval, and upstream synchronization with the official MCP repository.
      -

    • devdocs-mcp

      madhan-g-p
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides version-pinned, deterministic documentation sourced from DevDocs.io to AI assistants (Claude, RooCode, Cline, Copilot etc.) and also via offline mode. Not via Scraping! But using the supported downloading option from devdocs.
      44 npm
      13
      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

    B3/5.0

    Scored across 3 tools

    Disambiguation3/5

    The tools have some overlap in purpose, as both get_docs_by_category and mcp_docs_guide retrieve documentation content, which could cause confusion. However, search_docs is distinct with its keyword-based functionality, and descriptions help clarify that get_docs_by_category provides structured overviews while mcp_docs_guide offers comprehensive guides, mitigating ambiguity.

    Naming Consistency2/5

    Naming is inconsistent with mixed conventions: get_docs_by_category uses snake_case with a verb_noun pattern, mcp_docs_guide uses snake_case but lacks a clear verb, and search_docs uses snake_case with a verb_noun pattern. The lack of a uniform verb style and the inclusion of 'mcp' in one tool name disrupt predictability.

    Tool Count3/5

    With 3 tools, the count is borderline thin for a documentation server, as it might lack operations like updating or deleting documentation. However, it covers basic retrieval and search, which could be sufficient for a minimal scope, placing it in the middle range.

    Completeness4/5

    For a documentation server, the tools provide good coverage with retrieval by category, comprehensive guides, and search functionality, allowing agents to access and find documentation effectively. Minor gaps exist, such as no update or management tools, but core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources