Marrow
Related Servers
Alternatives to Marrow
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to maintain persistent, cross-session memory of codebase architecture, naming conventions, and decisions through MCP tools. Eliminates repetitive project re-explanation by automatically injecting stored context into every session with local-first SQLite storage and optional team sharing capabilities.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents and assistants to share a local-first, token-efficient persistent memory layer across MCP-compatible runtimes, storing typed project facts, decisions, failures, and solutions with temporal validity. It supports offline use and Postgres-compatible storage, so agents can retrieve relevant context without re-embedding entire repositories.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to share a persistent local-first memory hub, storing and recalling architectural decisions and context across different tools via MCP, so users can switch assistants without losing context.Apache 2.0
- AlicenseAqualityDmaintenanceMCP server that provides a shared semantic memory layer for AI coding agents, enabling teams to store, search, and sync context, decisions, and knowledge across projects with project-based isolation and multi-backend support.141MIT
- FlicenseNot gradedqualityAmaintenanceProvides local-first, cross-session persistent memory that lets AI coding agents store, semantically search, and recall project-specific and cross-project knowledge via MCP tools and resources, with an optional task queue for autonomous execution.-

Mandrelofficial
AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to maintain structured, persistent memory as a typed-edge knowledge graph over contexts, decisions, and tasks, with deterministic auto-threading, trust signals, and replayable story recall. It also exposes a token-lean MCP gateway for on-demand tool discovery, helping agents preserve causal project context across sessions.5,295 npm5MIT
TDQS
Scored across 19 tools
Each tool targets a distinct resource/action, and descriptions explicitly delimit overlapping cases such as full-text search vs. semantic search and update_task vs. complete_tasks. The role/session tools are also clearly differentiated between session start and mid-session role switching.
Almost all tools use consistent snake_case verb_noun naming, such as list_project_artifacts, save_project_artifacts, and complete_tasks. Minor deviations exist with semantic_search and singular/plural variation between update_task and add_tasks/search_tasks, but the pattern remains highly readable.
Nineteen tools is slightly heavy for the typical 3–15 range, but the server spans artifacts, tasks, projects, and sessions, so each tool has a plausible role. The count is reasonable overall, though the surface is broader than a tightly scoped server.
Artifact lifecycle coverage is strong, including read, save, list, search, move, delete, history, and restore, but the task and project surfaces lack deletion/get-details operations. More importantly, descriptions reference source-browsing tools such as view_file_source, get_project_map, and search_code_skeletons that are absent from the tool set, creating dead ends.