ADHD Progress Hub
Related Servers
Alternatives to ADHD Progress Hub
- FlicenseNot gradedqualityBmaintenancePersistent memory and task coordination for AI coding agents. Tracks sprint items, logs tasks, manages session handoffs, and surfaces HITL requests so you stay in control across single or parallel Claude Code, Codex, Cursor, and Windsurf sessions.-
- AlicenseAqualityAmaintenanceLocal-first shared memory and task coordination for AI coding agents. One Go binary, MCP server, markdown files you own. Hooks for Claude Code and Codex CLI (and their desktop apps).304MIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceA local-first MCP server and continuity control plane that helps AI coding tools maintain project state, tasks, and context across sessions, models, and interruptions, with features like session tracking, token-efficient context assembly, and code understanding via Code Atlas.MIT
- FlicenseNot gradedqualityAmaintenanceSelf-hosted control plane for AI coding agents, providing persistent memory, session continuity, environment awareness, coordination, and replayable traces via MCP.2-
- FlicenseNot gradedqualityBmaintenanceCentralized multi-project state & handoff MCP server that lets AI agents save checkpoints in one session and resume in another with minimal token overhead, including git snapshots and code-graph integration.-
- AlicenseAqualityAmaintenanceLocal MCP server giving AI coding agents (Claude Code, Cursor, VS Code/JetBrains Copilot) a shared, persistent memory of your projects and every bug/issue faced during development. Stateless, plain-file storage (AGENTS.md + issues.jsonl) — no database.16207 npm1MIT
- AlicenseNot gradedqualityBmaintenanceSelf-hosted personal context layer that gives AI agents shared memory via MCP.MIT
- FlicenseNot gradedqualityBmaintenancePersistent context layer for AI coding assistants. Sync memory files from Claude Code to ChatGPT, Gemini, Cursor, Windsurf, and Copilot via a native MCP endpoint. Bearer token auth, JSON-RPC 2.0 over stateless HTTP. Free tier available.-
TDQS
Scored across 20 tools
Each tool targets a distinct resource/action, and the descriptions explicitly cross-reference related tools to prevent misselection. Even near-synonyms like pause_thread, dismiss_thread, and mark_done are clearly separated by intended outcome.
All 20 tools use a consistent verb_noun snake_case pattern (get_overview, check_overlap, list_projects, pause_thread, etc.). No mixed conventions or vague generic names.
At 20 tools, this falls in the 'heavy' range (16–25). While each tool serves a distinct purpose, the set could be tightened (e.g., merging some thread state tools or reminder utilities) without losing functionality.
The surface covers project and thread lifecycles (create/update/close/abandon), reminders, session digests, and environment checks. Minor gaps exist (e.g., no reminder update/delete, no hard delete for threads) but core workflows are fully supported.