Skip to main content
Glama
titov-d

mcp-agentdocs

by titov-d
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-agentdocs

No user-submitted related servers found.

    Related Servers

    • mcmodding-mcp

      OGMatrix
      A
      license
      A
      quality
      A
      maintenance
      MC Modding is a Model Context Protocol (MCP) server designed to equip AI assistants, such as Claude, with direct and current access to Minecraft modding documentation. By indexing official Fabric and NeoForge sources weekly, it ensures AI responses are always accurate, backed by real documentation,
      4
      67 npm
      67
      MIT

    • 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.
      4 npm
      ISC

    • 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

    • open-context

      incu6us
      A
      license
      A
      quality
      C
      maintenance
      A high-performance MCP server providing up-to-date documentation for Go, npm, Python, Rust, Docker, Kubernetes, Terraform, and more — fetched from official sources, not training data.
      18
      3
      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

    A4.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: list_topics lists all available documents, search_docs searches for specific content, and get_doc retrieves full document. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: list_topics, search_docs, get_doc. Easy to predict and understand.

    Tool Count4/5

    With only 3 tools, the set is minimal but covers the essential operations for a documentation server: browse, search, and retrieve. It is slightly under the typical range but still reasonable for a focused server.

    Completeness5/5

    The tool surface covers the full lifecycle of accessing curated documentation: listing all documents, searching for specific content, and retrieving full documents. No obvious gaps for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources