SkillAgentSearch skills...

adhd-hub

Self-hosted source of truth for half-finished plans, migrations, and setups for coding agents.

Install / Use

claude mcp add uniskela -- npx -y github:uniskela/adhd-hub

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

81/100

Category

Operations

Supported Platforms

Claude Code
Claude Desktop

Our assessment of adhd-hub

adhd-hub scores 81/100 on our quality scale, 645th of 763 Operations skills we index.

Its MCP Server is 24 KB long, well organised into 29 sections with 15 code examples: a thorough specification that gives an agent plenty to work with.

It has 10 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
30/30
Structure
20/20
Description
12/15
Adoption
4/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 4 days ago, so adhd-hub is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 92/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

adhd-hub compared with similar skills

All 4 of these similar skills score higher than adhd-hub; compare them before choosing.

SkillScoreStarsUpdatedFormat
adhd-hub (this skill)by uniskela81104d agoMCP Server
Agent-Reachby Panniantong100113.3k12d agoCLAUDE.md
hyperframesby heygen-com10087.1ktodayCLAUDE.md
rufloby ruvnet10082.1ktodayCLAUDE.md
headroomby headroomlabs-ai10080.2ktodayCLAUDE.md

Frequently asked questions

How do I install adhd-hub?
Run claude mcp add uniskela -- npx -y github:uniskela/adhd-hub. The install tabs above show the steps for each supported agent.
Which AI agents does adhd-hub work with?
It is written for Claude Code and Claude Desktop, as a MCP Server file. Other agents that read the same format can often use it too.
Is adhd-hub safe to use?
It is MIT-licensed and scores 92/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is adhd-hub still maintained?
The repository was last updated 4 days ago, so adhd-hub is actively maintained.

ADHD Progress Hub

Coded with Codex Coded with Cursor ADHD Progress Hub MCP server – quality and maintenance score on Glama

Self-hosted source of truth for half-finished plans, migrations, and setups — so coding agents (Cursor, Codex, Claude Code, …) can check overlap, save progress, and nudge you later.

<a href="https://www.producthunt.com/products/adhd-progress-hub?embed=true&amp;utm_source=badge-featured&amp;utm_medium=badge&amp;utm_campaign=badge-adhd-progress-hub" target="_blank" rel="noopener noreferrer"> <picture> <source media="(prefers-color-scheme: dark)" srcset="https://api.producthunt.com/widgets/embed-image/v1/featured.svg?post_id=1272430&amp;theme=dark"> <img src="https://api.producthunt.com/widgets/embed-image/v1/featured.svg?post_id=1272430&amp;theme=light" alt="ADHD Progress Hub on Product Hunt" width="225"> </picture> </a>

Inspired by claude-adhd (see ATTRIBUTION.md). This project is tool-agnostic: MCP over Streamable HTTP (plus an optional local stdio transport) + REST, optional OpenClaw notifications, and an optional local transcript indexer (summaries only).

Screenshots

My work with Notes & context (projects list, calm rows, and the reader opened beside them):

My work with Notes & context

| Now | My work | Progress | Settings | | --- | --- | --- | --- | | Now | My work | Progress | Settings |

Gallery shots use dummy demo data (Now shows a saved “Where you left off” step and a gentle “Is this still on your list?” check). More UI detail: Dashboard · Notes & context.

Why

You start a Proxmox migration / homelab setup / refactor in Cursor Cloud, continue on a Dev LXC, forget for a week, then rediscover a half-finished chat — or you don’t. The hub keeps:

  • Threads — open / blocked / done / dismissed work items
  • Progress wiki — data/wiki/projects/<slug>/PROGRESS.md
  • Overlap checks — “am I about to redo something half-done?”
  • Reminders — once / session / daily / random
  • OpenClaw bridge (optional) — chat nudges + memory sync when you’re away from the IDE

Quick start

Docker Compose with a published image is the recommended persistent server install. See the full installation guide for a ready-to-copy Compose file, docker run, source/uv, upgrades, backups, reverse proxies, and client-only CLI installs. Every server setting is documented in the environment variable reference. Hub state (SQLite including project tags and scan-line cache, plus ai.json AI settings) lives under /data in the container — mount a named volume or bind there and keep ADHD_HUB_DATA_DIR=/data (see What lives under /data).

Docker from this checkout

The repository Compose file builds the current checkout:

cp .env.example .env   # set a real ADHD_HUB_AUTH_TOKEN
docker compose up -d --build
curl -fsS http://127.0.0.1:8787/api/health

For a released server without a source checkout, use ghcr.io/uniskela/adhd-hub:latest (or a pinned X.Y.Z) as shown in the installation guide.

Run from source with uv

cp .env.example .env   # set ADHD_HUB_AUTH_TOKEN
uv sync
uv run adhd-hub serve --host 127.0.0.1 --port 8787

Local MCP over stdio

For MCP clients that launch a local subprocess, the same Hub tool catalog can run over stdio:

adhd-hub mcp-stdio

Generic MCP config:

{
  "mcpServers": {
    "adhd-hub": {
      "command": "adhd-hub",
      "args": ["mcp-stdio"]
    }
  }
}

Stdio is an optional local mode: it uses the configured Hub data directory and the same MCP tools, but it does not start the REST API, dashboard, or background scheduler. It has no bearer header because the MCP connection is the local child process itself. For a persistent/shared Hub, remote agents, OAuth, dashboard access, and scheduled reminders, keep using adhd-hub serve/Docker and the Streamable HTTP /mcp endpoint.

See the MCP tool contract for parameter metadata, output compatibility, side effects and local regression checks.

Published images (only after a manual release-PR merge by uniskela):

  • :latest, X.Y.Z, and X.Y on the Git tag created for that release (for example 0.22.1, 0.22)

Releases (Release Please): after uniskela manually merges a PR to main with Conventional Commits (feat:, fix:, feat!:…), Release Please opens or updates a release PR. It never auto-merges that PR. When uniskela manually merges the release PR, Release Please creates vX.Y.Z and then publishes the matching multi-architecture images. The publish workflow has no direct push, PR, or manual trigger. Squash merges use the PR title as the subject (body bullets do not count); keep titles conventional for release-surface work — see AGENTS.md / CONTRIBUTING.md.

Pre-1.0 bumps (see release-please-config.json): fix: → patch, feat: → minor, feat!: / breaking → minor (not 1.0.0 yet).

Documentation, chore, test, and CI-only merges do not open a release PR, even if their subject accidentally starts with feat:. A feature, fix, performance, revert, or explicit breaking-change subject reaches Release Please only when that commit changes a shipped runtime surface (src/, package metadata/lockfile, Dockerfile, or docker-compose.yml). A generated release PR continues through the tag-and-publish step after uniskela manually merges it.

docker pull ghcr.io/uniskela/adhd-hub:latest
docker pull ghcr.io/uniskela/adhd-hub:0.22.1

Repo secrets for Docker Hub: DOCKERHUB_USERNAME, DOCKERHUB_TOKEN. GHCR uses GITHUB_TOKEN (packages: write). After a successful image publish, the same Hub secrets push this README (Hub truncates at 25k bytes) and the GitHub repository short description onto uniskela/adhd-hub (DOCKERHUB_TOKEN must be a Hub PAT with Read, Write, and Delete).

Connect Cursor

Marketplace plugin (recommended for Cursor): install adhd-hub-cursorskill (Marketplace once published, or local/dev install of that repo). With a Hub already running, set plugin variables ADHD_HUB_MCP_URL ({base}/mcp) and ADHD_HUB_AUTH_TOKEN, then verify MCP tools and skills. That plugin ships the Hub rule + session/projects/env-check skills with Marketplace wiring; Hub remains the skill source of truth (Cursor plugin skill sync).

Project / CLI connect (monorepos, adhd-hub connect, or non-Marketplace setups): merge adapters/cursor-mcp.json into your MCP config (URL + bearer via ${env:ADHD_HUB_AUTH_TOKEN}), install the rule from adapters/cursor-rule.mdc into .cursor/rules/, and optionally install skills:

# Install from the published repository:
npx skills add uniskela/adhd-hub -g
# Or, while developing an unreleased local checkout:
npx skills add ./skills -g

Or use adhd-hub connect … --agents cursor --cursor-rule --skills — see docs/public/connect.md.

Optional third-party companions (i-have-adhd, Superpowers, Ponytail, Graphify, Context7, agent-browser, RTK, Serena, Humanizer): see docs/public/coding-companions.md. Choose only the tools that fit your workflow; Hub Settings → Coding agents and adhd-hub connect --with-* provide the supported opt-in install paths.

For calm, resumable project notes and plans, use the ADHD-friendly writing guide: one visible Now action, brief context, and a concrete return cue.

Documentation site: uniskela.com/docs/adhd-hub (Zensical via uniskela/com). A GitHub Pages mirror stays at uniskela.github.io/adhd-hub until the Pages cutover. Preview locally with uv sync --extra dev && uv run zensical serve. The Pages workflow deploys only from main after uniskela merges documentation changes; it does not run for pull requests or manual dispatches.

  • MCP (recommended persistent/shared transport): http://<host>:8787/mcp
  • MCP (optional local subprocess transport): adhd-hub mcp-stdio
  • REST docs: http://<host>:8787/docs
  • UI: http://<host>:8787/ui/

MCP tools

| Tool | Purpose | |------|---------| | session_digest | Compact open threads (goal/focus/next/resume) + reminders | | check_overlap | Rank open threads vs what you’re starting (goal/title/focus) | | suggest_duplicate_threads | Review same-outcome evidence and safe merge eligibility | | request_thread_merge | Queue a local duplicate merge for explicit human confirmation | | thread_merge_history | Read retained source threads, notes and events under their original IDs | | resolve_project | Map workspace path → project slug | | list_projects / upsert_project | Project registry (+ optional forge overrides) | | rename_project / delete_project | Queue rename/delete for /ui confirmation (not applied immediately) | | list_pending_actions | See delete/rename requests waiting for you | | list_open_threads | List unfinished work | | upsert_thread | Create/update a thread (one finishable outcome) | | upsert_progress | Update thread state + PROGRESS.md (thread_id when known) | | pause_thread | Leave a concrete resume step | | mark_done | Close a known thread | | set_reminder | once / session / daily / random |

Using this project with AI coding agents

If you use Codex, Cursor, Claude Code, or another assistant with Context7 MCP, you can ask it to consult the project's documentation before setting up or integrating the Hub. Context7 is optional and separate from ADHD Progress Hub's own MCP server.

Use Context7 MCP to resolve the official documentation library for uniskela/adhd-hub (expected ID: /uniskela/adhd-hub), then retrieve guidance for installation, agent connections, MCP transports and tools, authentication, and troubleshooting. Match the guidance to my installed ADHD Progress Hub version. If the library is still indexing or doesn't cover that version, check the maintained documentation and linked source files instead.

Optional OpenClaw

Install the Hub skills for OpenClaw:

npx skills add uniskela/adhd-hub -g -a openclaw

Pairing (recommended): In Settings → Phone alerts, click Start pairing, copy the prompt into OpenClaw, then Approve what it submits. OpenClaw never needs ADHD_HUB_AUTH_TOKEN — only the short pairing code. Full steps: OpenClaw connection and alerts.

Manual path: Enable private hooks on the OpenClaw gateway. Then in Settings → Phone alerts, save the webhook or agent URL, bearer token, alert schedule, stale age, cooldown, and alert size. Use Save and send a test to verify the route.

The bearer token is encrypted before it is written to the Hub data directory and is never returned to the browser. Environment variables remain available for initial provisioning:

ADHD_HUB_OPENCLAW_WEBHOOK_URL=http://op

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars10
CategoryOperations
Updated4d ago
Forks0

Languages

Python

Trust signals

92/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 low1 info