learning-loop-mcp
Related Servers
Alternatives to learning-loop-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceProvides AI agents with persistent, local, and shareable project memory by storing decisions and code context in a searchable SQLite index, supporting keyword and semantic search via MCP.3MIT
- 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
- 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
- AlicenseNot gradedqualityNot gradedmaintenanceProvides AI coding agents with persistent, long-term memory through local semantic search and SQLite storage. It enables agents to save and retrieve architectural decisions or project context across different conversation sessions without requiring cloud services.MIT
- AlicenseNot gradedqualityCmaintenanceProvides AI coding agents with low-latency project intelligence, including workspace setup, encrypted backups, diagnostics, evolution digests, and cross-project pattern scoring from local SQLite data.MIT

nodespace-mcpofficial
FlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to query a local knowledge base for persistent, searchable project context, reducing re-explanation and token usage.8-
TDQS
Scored across 11 tools
Most tools have distinct purposes, but several pairs overlap in surface intent: amnesia_check vs amnesia_evaluate both concern continuity/Amnesia validation, and learning_context vs search both return lesson-related content. The descriptions help a careful agent differentiate them, but the boundaries are not immediately obvious.
All names use snake_case and are readable, but the pattern is mixed: some are verb_noun (capture_outcome, register_solution, reindex_solutions), some are noun phrases (learning_status, learning_context, project_preflight), and some are bare words (index, search, solutions). This is not chaotic, but it lacks a consistent convention.
Eleven tools is well within the ideal range for a domain-specific server. Each tool serves a distinct role in the learning-loop lifecycle, and none feel redundant or purely decorative.
The toolset covers the main learning-loop workflow: preflight, outcome capture, Amnesia validation, indexing, solution registration, status, and retrieval. Minor gaps exist—such as no explicit promotion tool or lesson deletion—but these may be intentional given the append-only and forward-only design.