Skip to main content
Glama
codemcp

agentic-knowledge

by codemcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to agentic-knowledge

No user-submitted related servers found.

    Related Servers

    • api-docs-mcp

      akshaysadanand
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that gives AI coding assistants access to up-to-date API documentation via RAG by crawling documentation sites, indexing them into a vector store, and enabling semantic queries.
      MIT

    • mcp-ragdocs

      hannesrudolph
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server implementation that provides tools for retrieving and processing documentation through vector search, enabling AI assistants to augment their responses with relevant documentation context
      9 npm
      265
      MIT

    • RAG Docs MCP Server

      gorizond
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that provides tools for retrieving and processing documentation through vector search, enabling AI assistants to augment their responses with relevant documentation context.
      19 npm
      MIT

    • DocDex

      tgautam2
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that turns a directory of markdown documentation into searchable, citable tools for AI assistants, enabling them to find, read, and reference specific sections with auditable citations.
      -
    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.2/5.0

    Scored across 3 tools

    Disambiguation4/5

    Each tool targets a distinct action (search, list, init), but search_docs also lists available docsets, creating a minor overlap with list_docsets. Despite this, the tools are clearly differentiated by their core purposes.

    Naming Consistency5/5

    All tool names follow the verb_noun snake_case pattern: search_docs, list_docsets, init_docset. This is consistent and predictable.

    Tool Count5/5

    Three tools is within the ideal 3-15 range, and each tool serves a necessary function without redundancy. The count is well-scoped for the server's documentation search purpose.

    Completeness5/5

    The set covers the complete lifecycle: init_docset for setup, list_docsets for discovery, and search_docs for querying. No obvious gaps exist for the intended use case.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources