agents-learning
Related Servers
Alternatives to agents-learning
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenancePersistent memory MCP server for AI coding agents. Stores, searches, and retrieves context across sessions using SQLite and FTS5.MIT
- FlicenseNot gradedqualityDmaintenanceA lightweight MCP memory server built on SQLite + FTS5, providing cross-session long-term memory for Claude Code.-
- AlicenseAqualityAmaintenancePersistent memory MCP server for AI coding agents (Claude Code, Codex, Gemini CLI). Hybrid retrieval (vector + BM25), cross-encoder reranking, knowledge graph, session checkpoint/resume, and multi-scope isolation. Local-first with LanceDB.3050 npm15MIT
- AlicenseBqualityCmaintenancePersistent memory engine for AI coding agents. Single Go binary, zero runtime dependencies, MCP-native. Stores, searches, and deduplicates memories across sessions using embedded SQLite with hybrid FTS + semantic search, memory decay, relation graph, and token-budget context assembly.1023MIT
- AlicenseNot gradedqualityAmaintenanceMinimal long-term memory MCP server for AI assistants backed by SQLite FTS5 full-text search, optional hybrid vector retrieval, scoped memory graphs, and VSCode extension.1MIT

hive-memoryofficial
AlicenseNot gradedqualityDmaintenanceMCP server for personal and shared memory with full-text search (SQLite FTS5) and outcome tracking, compatible with any MCP agent like Claude Code, Cursor, and Codex CLI.0MIT
TDQS
Scored across 11 tools
The search/read pairs for knowledge, work memory, and candidate references are distinguishable, but the boundaries between formal knowledge vs. work history vs. candidate references remain subtle for an agent. Two separate feedback tools (case_feedback and candidate_reference_feedback) also overlap in purpose, increasing misselection risk.
All names use snake_case and generally follow a resource_action pattern (knowledge_read, work_memory_search, candidate_reference_feedback, task_update). A few are resource_noun (learning_status, session_context), but the convention remains predictable overall.
Eleven tools is well within the appropriate range for a focused learning/reference server. Each tool maps to a distinct operation: status, context, task scope, knowledge access, work-memory access, candidate access, and feedback.
The surface covers reading, searching, using knowledge, and reporting feedback, but there are no tools to create, update, or delete formal knowledge or candidates. Reliance on external hooks for writes leaves notable lifecycle gaps for a learning system.