Open Brain Knowledge MCP Server
Related Servers
Alternatives to Open Brain Knowledge MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenancePersistent 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.6107 npm1MIT
- AlicenseAqualityBmaintenanceProvides 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.81MIT
- AlicenseCqualityCmaintenancePersistent knowledge layer for AI agents. Structured KB with search, investigation threads, multi-session journal, and multi-agent attribution. SQLite or PostgreSQL.424MIT
- AlicenseNot gradedqualityCmaintenanceGives 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.4MIT
- AlicenseNot gradedqualityDmaintenanceProvides 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 npmApache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to record and query reasoning steps in SQLite, offloading trace data from the context window, with DAG support and persistent cross-session memory.2MIT
TDQS
Scored across 10 tools
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.
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.
10 tools is well-scoped for a knowledge base management server. They cover essential operations without being excessive or too sparse.
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.