Skip to main content
Glama
JohnXu22786

doctrove

by JohnXu22786
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to doctrove

No user-submitted related servers found.

    Related Servers

    • Beit-MCP

      Comrade-e
      F
      license
      Not graded
      quality
      B
      maintenance
      Local MCP server that indexes documentation from URLs/files into a vector database, enabling coding agents to search and use up-to-date library and API documentation.
      -

    • memo

      ngabzar02
      A
      license
      A
      quality
      A
      maintenance
      MCP server for local, offline-capable library documentation. It resolves library IDs and retrieves up-to-date docs via hybrid search from a persistent SQLite cache.
      3
      1
      MIT

    • 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.
      45 npm
      13
      MIT

    • live-docs-mcp

      Jubast
      F
      license
      B
      quality
      B
      maintenance
      A local-only MCP server that provides AI coding agents with up-to-date documentation for specific libraries or tools during feature implementation, including search tools, multi-version support, and user-defined library entries.
      2
      -
    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.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a clearly distinct role: lookup finds the canonical ID, releases lists available versions, and extract fetches documentation content. Their purposes are complementary with no overlap, and the descriptions explicitly indicate when to use each tool.

    Naming Consistency4/5

    Two tools follow the 'catalog_' prefix pattern, while the third uses 'doc_'. This is a minor deviation, but the verbs (lookup, releases, extract) are consistently descriptive and make the tool purposes clear despite the prefix mismatch.

    Tool Count5/5

    With only three tools, the server is tightly scoped to its purpose of documentation retrieval. Each tool is essential to the workflow, and the count is within the well-scoped range for a specialized server.

    Completeness5/5

    The set covers the full pipeline from discovering the correct entry and checking version availability to extracting focused documentation fragments. There are no obvious dead ends or missing operations for the server's stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources