thebrain-mcp
Related Servers
Alternatives to thebrain-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceWraps TheBrain knowledge graph as an MCP server, enabling AI assistants to search, create, and manage thoughts, links, and notes via natural language.5-
- AlicenseNot gradedqualityDmaintenanceMCP server that provides semantic memory with search, related-content traversal, and write-back capabilities, all powered by local embeddings of your notes, documents, and chat histories.3MIT
- AlicenseNot gradedqualityFmaintenanceA personal knowledge base MCP server with semantic search, storing thoughts in PostgreSQL with pgvector embeddings and providing 8 tools for capture, search, browse, stats, relations, traces, and hydration.1Apache 2.0
- AlicenseNot gradedqualityFmaintenanceMCP server exposing personal knowledge base tools, including save, search, get, context, link, and feedback, backed by brain-cli's SQLite database.MIT
- AlicenseNot gradedqualityCmaintenanceA universal MCP server providing persistent, structured memory through a knowledge graph with graph storage, semantic vector search, and multi-hop traversal for AI agents and IDEs.24 PyPI1MIT
- AlicenseAqualityDmaintenanceA local MCP server enabling hybrid search over documents, memory, and knowledge graphs for retrieval-augmented generation, with tools for SQLite, semantic memory, and entity-relationship queries.41MIT
TDQS
Scored across 17 tools
Each tool maps to a distinct resource+action, and the overlapping-looking pairs are explicitly delineated in descriptions: set_note (replace) vs append_note (append), get_thought (one hop) vs traverse (several hops), create_thought (single) vs ingest (bulk). An agent can reliably pick the right tool.
Every tool uses a uniform brain_ prefix with snake_case verb_noun naming (brain_search, brain_create_thought, brain_delete_thought, brain_attach_url). The convention is applied consistently across all 17 tools with no stylistic drift.
17 tools is slightly on the heavy side but each earns its place within a graph domain (search, read, traverse, mutate thoughts/notes/links/tags, index management). No redundant tools bloat the surface.
Strong lifecycle coverage: create/get/update/delete thoughts, note set/append, link, tag add/remove, URL attach, search, traverse, ingest and index management. Minor gaps exist (e.g. no explicit link-removal or parent-reparenting operation), but core workflows are fully supported.