Skip to main content
Glama
Jubast

live-docs-mcp

by Jubast
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to live-docs-mcp

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

    • 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.
      -
    • GitHits by githits-com

      GitHitsofficial

      githits-com
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to search and access open-source code, documentation, and package information via a local MCP server.
      1,996 npm
      113
      Apache 2.0

    • docpilot-mcp

      neromtoobad
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools to fetch live, version-accurate documentation, changelogs, examples, and method signatures for npm and PyPI packages, preventing AI coding agents from hallucinating stale APIs.
      11 npm
      ISC
    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 2 tools

    Disambiguation5/5

    search_library targets finding a library by name, while search_docs targets searching within a library's documentation by topic. The two tools have clearly distinct purposes and are complementary rather than overlapping.

    Naming Consistency5/5

    Both tool names follow the same search_<noun> snake_case pattern. The naming is predictable and clearly indicates action and target.

    Tool Count3/5

    Two tools is on the low end for a documentation-focused server, but each tool covers a distinct step in the lookup workflow. It feels minimal yet coherent.

    Completeness2/5

    The surface is limited to search operations; there is no way to list libraries, retrieve full documentation content, or navigate doc structure. Agents may be able to find relevant topics but cannot fetch the actual documentation content.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources