Skip to main content
Glama
melvenac

Open Brain Knowledge MCP Server

by melvenac

Related Servers

Alternatives to Open Brain Knowledge MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Persistent memory for AI coding agents, storing learned architecture decisions, patterns, and bug fixes in a local SQLite database with full-text search, enabling agents to recall information across sessions.
      6
      107 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides persistent cross-session memory and full-text search for AI coding assistants, storing project context, decisions, and preferences while enabling searchable access to conversation history via local SQLite.
      8
      1
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Persistent knowledge layer for AI agents. Structured KB with search, investigation threads, multi-session journal, and multi-agent attribution. SQLite or PostgreSQL.
      42
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Gives AI coding agents persistent memory by storing observations, decisions, and learnings in a local SQLite database with vector search, full-text search, and a rules engine.
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI coding assistants with persistent project memory to retain architectural decisions, code patterns, and domain knowledge across sessions. It stores data locally in a SQLite database, allowing agents to remember, recall, and manage project-specific context using full-text search.
      3 npm
      Apache 2.0

    TDQS

    A3.9/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: forget, index list, prune, recall, reindex, stats, store, store_summary, and summarize. Even similar operations like kb_index and kb_reindex are differentiated (single file vs. batch scanning). No ambiguity.

    Naming Consistency5/5

    All tools follow the 'kb_verb[_noun]' pattern consistently. Underscore snake_case is used throughout. The verbs are appropriate and mostly single-word except 'store_summary', which is still clear and consistent.

    Tool Count5/5

    10 tools is well-scoped for a knowledge base management server. They cover essential operations without being excessive or too sparse.

    Completeness4/5

    The tool set covers creating, retrieving, updating (via reindex/incremental indexing), searching, listing, forgetting, and pruning. A minor gap: there is no explicit tool to update or delete a stored summary, but the workflow allows overwriting through kb_store_summary.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues