A
licenseA
qualityB
maintenanceShared memory layer for AI coding agents to store and recall learned information across sessions and tools.
9
2
MIT
@brainfeather/mcp
Related Servers
Alternatives to @brainfeather/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides persistent, searchable memory and knowledge capture for AI-assisted development, enabling agents to retain decisions, bugs, and patterns across sessions and projects.MIT
- AlicenseNot gradedqualityCmaintenanceProvides persistent memory for AI coding tools, allowing them to remember corrections, decisions, and preferences across sessions and different tools.8 npm2MIT
- AlicenseNot gradedqualityBmaintenanceProvides a local long-term memory layer for AI coding tools like Cursor and Claude Code, enabling cross-session, cross-tool sharing of project facts, user preferences, decisions, and workflows.12 npm2MIT
- AlicenseAqualityCmaintenancePersistent memory for AI coding agents. Store coding standards, architecture decisions, and project context across sessions with AES-256 encryption.81MIT
- AlicenseAqualityCmaintenanceProvides persistent memory for OpenCode coding agents, allowing them to store and recall architecture decisions, conventions, and gotchas across sessions via semantic search.539 npmMIT
TDQS
A4.1/5.0
Scored across 8 tools
Disambiguation4/5
Most tools have clearly distinct purposes: save vs. search vs. delete vs. import vs. graph traversal. The only potential confusion is between get_context and search_memory, as both retrieve remembered information, but get_context is broad and task-oriented while search_memory is a targeted topic lookup, and the descriptions reinforce this boundary.
Naming Consistency5/5
All tool names follow a consistent verb_noun snake_case pattern: get_context, search_memory, list_entities, forget_memory, traverse_graph, save_memory, capture_activity, onboard_project. The naming convention is uniform and predictable.
Tool Count5/5
With 8 tools, the server covers the core memory lifecycle (create, read, update via supersedesId, delete, import, capture, exploration) without unnecessary bloat. The count is well-scoped for a project-context memory system.
Completeness5/5
The tool set covers the full durable-fact workflow: saving explicit memories, capturing inferred ones, importing existing documentation, retrieving context, searching past decisions, traversing entity relationships, and deleting erroneous records. No obvious critical operation is missing for the stated purpose.
Maintenance
ActivityMaintained
ResponsivenessNo issues