Skip to main content
Glama
rkratky

DocsHub MCP Server

by rkratky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to DocsHub MCP Server

No user-submitted related servers found.

    Related Servers

    • llms-mcp

      druellan
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that exposes the llms.txt file and its referenced local or external resources from a project root to provide context for AI models. It automatically parses documentation links and URLs to make them accessible as additional MCP resources.
      1
      MIT

    • MCP LLMS-TXT Documentation

      langchain-ai
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools to load and fetch documentation from any llms.txt source, giving users full control over context retrieval for LLMs in IDE agents and applications.
      1,033
      MIT

    • docs-mcp-server

      DewminK
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes one or more documentation folders (Markdown, MDX, TXT) to AI agents, enabling listing, reading, and searching of documentation files.
      -

    • mcp-docs

      gmantovani2005
      A
      license
      Not graded
      quality
      C
      maintenance
      Generic MCP server that exposes Markdown documentation to LLMs, enabling them to search and answer questions about any software documentation.
      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.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct, non-overlapping role in the documentation workflow: listing projects, fetching project docs (full or index), and reading individual pages. The descriptions clearly define when to use each tool.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: list_available_docs, get_project_docs, read_doc_page. This is predictable and easy for an agent to interpret.

    Tool Count5/5

    With 3 tools, the server is tightly scoped to its purpose of retrieving documentation. Each tool is essential to the workflow, and there is no redundancy or excess.

    Completeness5/5

    The tool set covers the full lifecycle of fetching documentation: discover projects, retrieve either full content or an index, and then fetch specific pages. The fallback mechanism ensures no dead ends for users.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources