Skip to main content
Glama
Jr-kenny

Shelby docs MCP

by Jr-kenny
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Shelby docs MCP

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • 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.
      11 npm
      2
      MIT

    • mcp-docs

      gmantovani2005
      A
      license
      Not graded
      quality
      D
      maintenance
      Generic MCP server that exposes Markdown documentation to LLMs, enabling them to search and answer questions about any software documentation.
      MIT

    • MCP AI Docs

      cartek99
      F
      license
      A
      quality
      D
      maintenance
      An MCP server that provides indexed, searchable access to Anthropic Claude and Google Gemini documentation, with full-text search, page fetching, and section listing capabilities.
      4
      -

    • 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.
      34 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.4/5.0

    Scored across 4 tools

    Disambiguation2/5

    Multiple tools have overlapping purposes that could cause confusion. The 'read_shelby_doc' tool appears to cover most of the functionality of 'get_shelby_doc_chunk' and 'search_shelby_docs', as it can read by exact path, title, URL, page ID, or fuzzy query. This creates ambiguity about when to use each tool, especially between 'read_shelby_doc' and 'search_shelby_docs' for fuzzy queries.

    Naming Consistency4/5

    The naming follows a mostly consistent pattern with 'shelby_doc' as the common prefix and snake_case throughout. However, there's a minor deviation with 'list_shelby_doc_pages' using 'pages' while others use 'doc' or 'docs', which slightly breaks consistency but doesn't significantly impact readability.

    Tool Count3/5

    With 4 tools, the count is borderline for a documentation server. It feels slightly thin as there might be room for additional operations like updating or managing documentation, but it's reasonable for basic read-only access. The scope appears limited to retrieval and listing, which the tools cover adequately in number.

    Completeness3/5

    For a documentation server, the surface covers reading, listing, and searching, which are core operations. However, there are notable gaps such as no create, update, or delete tools, which might be expected if the server supports documentation management. This limits the server to read-only use cases, making it incomplete for full lifecycle coverage.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources