Thread Keeper
Related Servers
Alternatives to Thread Keeper
No user-submitted related servers found.
Related Servers
AlicenseAqualityCmaintenanceShared memory MCP server for AI coding agents, enabling context sharing across sessions with local SQLite or cloud-based semantic search, compatible with Claude Code and Cursor.235 npm1MIT- FlicenseNot gradedqualityDmaintenanceShared memory and orchestration for coding agents, enabling persistent knowledge, multi-agent coordination, and a canonical workflow across MCP-compatible AI clients.34 npm98-
- AlicenseAqualityAmaintenanceCross-agent memory bridge for AI coding assistants. Persistent knowledge graph shared across 10 IDEs (Cursor, Windsurf, Claude Code, Codex, Copilot, Kiro, Antigravity, OpenCode, Trae, Gemini CLI) via MCP. 22 tools including team collaboration, auto-cleanup, mini-skills, session management, and workspace sync. 100% local, zero API keys required.91,383 npm829Apache 2.0
- AlicenseCqualityDmaintenanceMCP server for sharing source-backed engineering memory across AI coding clients like Cursor and VS Code.301MIT
- FlicenseNot gradedqualityDmaintenanceA persistent, conflict-aware memory MCP server for AI coding assistants (Cursor, Claude Code).-
- AlicenseNot gradedqualityBmaintenanceMCP server that gives AI agents a continual learning brain with lessons, skills, memories, evidence-based refinement, rollback, and hybrid GraphRAG retrieval.MIT
TDQS
Scored across 134 tools
With 134 tools, many overlap heavily: spawn/tasks/tournament/task_logs/task_thread/claim_pickup/release_pickup all concern spawning and managing child sessions; review_thread/auto_review_trigger/shadow_review_run/curator_review/candidate_review_run/curator_run are all 'review' triggers with unclear boundaries; lesson_append/lesson_patch/lesson_remove/lesson_restore/lesson_neighbors/lesson_violation/lesson_get/lesson_list form a dense cluster where an agent may struggle to pick the right mutation. Tool descriptions are detailed but the sheer volume and overlapping 'review'/'evolve'/'dialectic' families make misselection likely.
Patterns are mostly snake_case with verb_noun, and families like lesson_*, curator_*, evolve_*, dialectic_*, spawn_budget_*, and sync_* are clearly prefixed, which helps grouping. However conventions are mixed: some tools are bare verbs (note, link, unlink, search, distill, forget, ingest, spawn, tournament), some are noun-only (brief, context, peers, presence, inbox, tasks, neighbors), some embed verbs inconsistently (auto_review_trigger vs review_thread vs shadow_review_run), and dialectic_claim/dialectic_review/dialectic_supersede mix noun/verb ordering. The prefix families prevent chaos, but it's not a predictable verb_noun pattern throughout.
134 tools is extreme and far beyond what any agent can reliably select from in-context; it vastly exceeds the 25+ threshold that already scores poorly. While each tool may earn its place in the system's architecture, the surface is so large that tool selection becomes a serious practical concern.
The surface is remarkably complete: full lifecycle for lessons (get/list/append/patch/remove/restore/violation/neighbors), skills (create/edit/patch/write_file/remove_file/delete/restore/validate/list/record), threads (open/close/idle/note/review/claim/release), dialectic claims (claim/evidence/review/supersede/synthesis/observation_resolve), plus mechanics, daemons, cleanup, sync, curation, and evolution. Every domain appears to have CRUD/lifecycle coverage with no obvious dead ends.