Skip to main content
Glama
gilanggsb

knowledge-mcp

by gilanggsb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to knowledge-mcp

No user-submitted related servers found.

    Related Servers

    • doc-search by SodaShikenn

      doc-searchofficial

      SodaShikenn
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for hybrid documentation search (keyword + vector) and RAG chat, enabling natural language queries with cited answers from indexed repositories.
      MIT

    • MCPedia

      asepharyana
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for a content-first knowledge base, enabling AI agents to search (full-text, semantic, hybrid) and retrieve Markdown documents, list content, and find related docs.
      7 npm
      MIT

    • MCP Knowledge Assistant

      channico
      F
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that enables AI clients to search a knowledge base and retrieve complete source documents via narrow search and fetch tools.
      2
      -

    • mcp-docs

      pgupta1795
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for documentation search that automatically indexes web documentation sites and provides semantic, full-text, or hybrid search capabilities.
      2 npm
      MIT

    • mcp-local-rag

      xiuxiansk
      A
      license
      A
      quality
      C
      maintenance
      MCP server that enables local hybrid semantic and keyword search over private PDF, DOCX, Markdown, and text documents without sending data to embedding APIs.
      9
      5,718 npm
      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

    A3.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: knowledge_search for query-based relevance, knowledge_get for retrieving by ID, and knowledge_list for enumerating with filters. No overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent pattern: knowledge_ + verb (search, get, list). The naming is uniform and predictable, with no mixed conventions.

    Tool Count5/5

    Three tools is a well-scoped count for a read-focused knowledge server. Each tool covers a distinct core operation (search, retrieve, list) without unnecessary bloat.

    Completeness2/5

    The server is entirely read-only, offering no operations to create, update, or delete knowledge documents. For a domain implied as 'knowledge management', this is a significant gap that would prevent agents from writing to the knowledge base.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources