brain-v42
Related Servers
Alternatives to brain-v42
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides persistent, searchable memory across coding projects and machines, letting agents record and retrieve projects, reusable assets, sessions, decisions, commits, and handoffs via MCP.2Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides persistent memory for AI coding agents, enabling them to save, search (hybrid vector/BM25/concept graph), list sessions, and forget memories via MCP tools.11 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceProvides persistent memory and task management for coding agents via MCP tools, enabling mid-session recall and capture of durable knowledge.1,117 npm10MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI coding agents and IDEs to capture conversations, extract structured knowledge into a queryable graph database, and recall past decisions, patterns, files, and errors across all projects and workspaces. Provides persistent memory tools for saving, searching, and cleaning up knowledge via MCP.2-
- AlicenseAqualityBmaintenanceProvides persistent memory for AI coding agents via MCP, enabling teams to share and recall facts across sessions. Automatically captures, classifies, and curates knowledge from supported transcript sources.1818 npm1AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceProvides persistent memory for AI coding agents via MCP, allowing them to recall fragility, decisions, and bugs across sessions.273 npm3MIT
TDQS
Scored across 9 tools
Most session tools map to distinct lifecycle states, but resume and heartbeat both target an open session with no clear boundary between them, and start's 'replay' capability also blurs with resume. The find_tool/call_tool pair is clearly distinct, which keeps the set usable.
All tools share the brain_ prefix and snake_case, and the seven session tools follow a consistent brain_session_<verb> pattern. The two meta-tools break that pattern with brain_find_tool and brain_call_tool, so the set is mostly consistent but not fully uniform.
Nine tools is well within the ideal range, and each tool maps to a distinct session lifecycle action or a general tool-search/call capability. Nothing feels redundant or bloated.
The session lifecycle is well covered: start, resume, heartbeat, capture, end, abandon, and list, with artifact attribution handled. Adding the meta find/call tools rounds out the surface with no obvious dead ends.