ADHD Progress Hub
Related Servers
Alternatives to ADHD Progress Hub
- FlicenseNot gradedqualityAmaintenancePersistent 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).306MIT
Related Servers
- AlicenseBqualityAmaintenanceLets multiple AI agents and parallel coding sessions share one memory and task ledger, so they can claim work instead of duplicating it, resume each other's handoffs and reasoning, and use credentials without ever seeing the keys. Connects assistants such as Claude Code, Codex, Cursor, Gemini, ChatGPT and custom agents over MCP, backed by a single local SQLite file or a self-hosted Postgres hub.35MIT
- AlicenseNot gradedqualityBmaintenancePersistent project memory and task management for AI coding agents through MCP. Lets Claude Code, Cursor, Codex and other MCP clients save decisions and bug fixes, search relevant context, and reuse it across sessions.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents in different editors and MCP clients to share messages, project context, notes, task ownership, handoffs, and advisory file claims through a local SQLite-backed coordination server. Supports MCP stdio, MCP Streamable HTTP, a JSON HTTP API, and a local CLI for multi-project agent collaboration.MIT
- 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
- AlicenseAqualityAmaintenanceSelf-hosted relay where coding-agent sessions on different machines share a team board, message each other and check for git conflicts before a commit or push. Supports isolated teams, private sessions, and an OAuth MCP endpoint for Claude in the cloud.91MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to store, search, and retrieve persistent local-first memory — project-specific decisions, preferences, error patterns, and research plus cross-project guidelines — so context survives across sessions without any external API calls. Optionally also exposes a task queue for autonomous execution and GitHub issue resolution in MCP clients such as Claude Code, OpenCode, and Goose.-
TDQS
Scored across 23 tools
Tools are grouped into clearly labeled lifecycle actions with explicit cross-references (e.g., dismiss vs. mark_done vs. pause), so most boundaries are clear. A few pairs like upsert_thread vs. upsert_progress and get_overview vs. session_digest could still cause initial misselection, though descriptions mitigate it.
The overwhelming majority follow a verb_noun snake_case pattern with consistent verbs such as list, upsert, dismiss, mark, pause, set, and resolve. Minor deviations like session_digest (noun-only) and mark_done (verb_adjective) keep it from being fully consistent.
23 tools is on the heavy side and sits in the 16–25 borderline range. The breadth is largely justified by covering projects, threads, progress, reminders, triage, health reporting, and memory sync, but a few tools could likely be consolidated without losing clarity.
Project and thread lifecycles are well covered, including creation, update, pause, dismiss, completion, and soft triage. Notable gaps remain: reminders can be set and listed but not updated, deleted, or explicitly marked handled, and there is no direct get-thread-detail tool for a known thread.