Skip to main content
Glama

Related Servers

Alternatives to kb-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM clients to read, search, and write to a local Obsidian vault over MCP, with full-text search, vault analytics, health scoring, and policy-enforced file operations.
      1
      MIT
    • F
      license
      B
      quality
      C
      maintenance
      Parses an Obsidian vault and exposes structured context (notes, blocks, tasks, headings) through MCP tools, enabling AI clients to query and reason over local markdown notes.
      19
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Serves folders of an Obsidian vault to AI agents over MCP as Open Knowledge Format bundles, letting them browse, search, read, graph and write draft notes with recorded provenance and checkable trust. Agents can propose changes, but only the user approves them, and stale or externally edited content is flagged rather than trusted.
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables natural language interaction with a local Obsidian vault, allowing MCP clients to read, search, create, append, and delete markdown notes securely.
      7
      979 npm
      MIT

    TDQS

    A3.6/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target clearly distinct operations (search, read, propose/apply changes, fetch queries/suggestions), and the propose/apply and fetch_queries/fetch_suggestions pairs are explicitly differentiated. However, kb_verify overlaps with the combined functionality of kb_graph_summary and kb_hygiene, so an agent may hesitate over which audit-style tool to call first.

    Naming Consistency5/5

    Every tool uses the same kb_ prefix followed by a verb_noun or verb_noun_phrase pattern in snake_case (kb_search, kb_read_page, kb_propose_changes, kb_fetch_queries). There are no mixed conventions or stray camelCase names, making the set highly predictable.

    Tool Count5/5

    With 12 tools, the set is well within a reasonable range for a knowledge-base server and each tool covers a distinct phase of the workflow (search, read, inspect, verify, propose, apply, record, reload). No tool appears redundant or purely filler.

    Completeness4/5

    The surface covers search, read, graph inspection, hygiene/citation audits, guarded write flows, query/suggestion recording, and index reload, which is close to full lifecycle coverage for a safe KB. A minor gap is the absence of a direct 'list all pages' or 'get raw index' tool, though kb_graph_summary and kb_search provide workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues