Skip to main content
Glama
grandinh
by grandinh

Related Servers

Alternatives to Claude MCP Knowledge Base

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that enables verified agents to retrieve from, propose changes to, and share capabilities around a human-owned Markdown/Git knowledge base, ensuring curation, exact-byte approval, and Git-based promotion.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that gives AI coding agents a git-backed markdown wiki to read and update, enabling search, read, write, verify, ingest, promote, and lint operations on versioned knowledge documents with schema validation, staleness tracking, and contradiction detection.
      4
      MIT
    • F
      license
      A
      quality
      B
      maintenance
      An MCP server that acts as a knowledge engine for software projects, delivering relevant context at the start of a task and accumulating knowledge at its end through tools like start_task, context, finish_task, remember, and search, with a file-based source of truth and optional semantic retrieval via Graphiti/Neo4j.
      5
      -
    • F
      license
      C
      quality
      D
      maintenance
      Git-backed MCP server for creating and maintaining an Obsidian-style markdown knowledge base with full CRUD, search, and git sync.
      7
      -
    • F
      license
      B
      quality
      D
      maintenance
      An MCP server that enables interaction with Markdown knowledge bases, allowing users to search and retrieve content by tags, text, URL, or date range from their local markdown files.
      7
      92
      -

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools target distinct resource-action pairs, but search_knowledge_base and get_mcp_specification both cover MCP documentation and best practices and could be confused. The descriptions help by distinguishing broad search from canonical spec retrieval, so the ambiguity is limited.

    Naming Consistency5/5

    All tool names consistently follow a verb_noun pattern: search, list, get, add, check, update. Multiword objects like blocklist_entry and knowledge_base do not break the predictability of the naming convention.

    Tool Count5/5

    Six tools is a well-scoped count for a knowledge base MCP server. Each tool covers an essential workflow: searching, listing indexed content, retrieving the spec, managing blocklist entries, and triggering updates.

    Completeness3/5

    The core search, listing, spec retrieval, and update workflows are covered, but the blocklist lifecycle is incomplete—there is no way to remove an entry or list all blocked entries. An accidental blocklist addition becomes a dead end for the agent.