Skip to main content
Glama

Related Servers

Alternatives to ADHD Progress Hub

  • F
    license
    Not graded
    quality
    B
    maintenance
    Persistent 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.
    -
  • A
    license
    A
    quality
    A
    maintenance
    Local-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).
    30
    5
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables 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
  • A
    license
    Not graded
    quality
    D
    maintenance
    A 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
  • F
    license
    Not graded
    quality
    B
    maintenance
    Centralized 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.
    -
  • A
    license
    A
    quality
    A
    maintenance
    Local 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.
    16
    77 npm
    1
    MIT

TDQS

A3.9/5.0

Scored across 23 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count3/5

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.

Completeness3/5

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.

Maintenance

ActivityMaintained
ResponsivenessResponsive