MCP Continuation Notes
Related Servers
Alternatives to MCP Continuation Notes
No user-submitted related servers found.
Related Servers
- AlicenseAqualityNot gradedmaintenanceProvides centralized knowledge management for projects, allowing users to store, search, and maintain project-specific knowledge that persists across sessions.2714 npm1-
- AlicenseAqualityCmaintenanceEnables AI coding agents to hand off in-progress work across sessions and different MCP clients by persisting shared state and handoff notes in a project folder.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables agent sessions to persist and reload project-scoped handoffs and todos across sessions, preserving context and tracking next steps.MIT
- AlicenseNot gradedqualityBmaintenanceProvides durable project context for coding agents, including project maps, session history, and explicit memories, all stored locally.46 npm7MIT
- AlicenseNot gradedqualityAmaintenanceProvides persistent memory for AI coding agents across sessions by saving and loading session context like tasks, decisions, and blockers.115 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides operational continuity for AI coding agents, preserving task state, decisions, checkpoints, and project context across sessions and model switches via MCP.1Apache 2.0
TDQS
Scored across 7 tools
Tools are mostly distinct: write, read (three variants), delete, check, list. The three read tools overlap slightly, but their intended use cases are clearly described (read-and-cleanup, read-with-staleness, read-without-staleness) and one is deprecated, reducing ambiguity.
All tool names follow a consistent pattern: continuation_ prefix plus a verb phrase (write, read_and_cleanup, read_with_staleness, cleanup_old, check_handoff, list_for_project, read_project_note). The naming is perfectly uniform and predictable.
With 7 tools, the server is well-scoped for the single purpose of managing continuation notes. Each tool serves a clear lifecycle function (write, read, check, list, delete) without bloat or redundancy.
The tool set covers the full continuation‑note lifecycle: creation (write), retrieval (read variants), existence checking, listing for a project, and deletion. No obvious gaps exist; the write tool replaces previous notes, so an explicit update is unnecessary.