Skip to main content
Glama
fdciabdul

mcp-adonis-docs

by fdciabdul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-adonis-docs

No user-submitted related servers found.

    Related Servers

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

    • docs-mcp

      kislevlevy
      F
      license
      Not graded
      quality
      B
      maintenance
      Local documentation search server for AI models using hybrid retrieval (phrase, keyword, vector). Provides MCP tools to search and fetch documentation from bundled or custom doc sets without any external API keys.
      -

    • starlight-mcp

      bkspace
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Astro/Starlight docs sites, providing search, get, and list tools for documentation content.
      58 npm
      12
      MIT

    • doctrove

      JohnXu22786
      A
      license
      A
      quality
      B
      maintenance
      Versioned library documentation retrieval MCP server for coding agents, providing accurate, versioned, and traceable API documentation snippets with scoring, caching, and offline support.
      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.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: detect_version identifies project context, search_docs finds relevant documentation pages, and get_doc retrieves page content. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow the same snake_case verb_noun pattern: detect_version, search_docs, get_doc. The naming is predictable and consistent.

    Tool Count5/5

    Three tools is a well-scoped size for a documentation server. Each tool covers a necessary step in the workflow: version detection, searching, and fetching content.

    Completeness5/5

    The tool set forms a complete workflow: detect version, search relevant docs, and retrieve specific pages or sections. There are no obvious dead ends or missing core operations for documentation access.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources