Agent Progress Board
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
agent-progress-board
A phone-friendly board of work progress across projects, fed by coding agents.
One group per project. Each item (a planned slice, a problem, something waiting for a person, a bug, new unplanned work) is a colour-coded tile with one line of what and why, plus its parent. The board shows everything still open plus whatever finished in the last 12 hours. Everything is exposed through one remote MCP server: agents load it as an MCP server, or post the same MCP tool calls over HTTPS where they can't. Clients live in the repos that use them.
Status: building (Slice 1, the MCP items API). See plan.md.
Design in one paragraph
A Cloudflare Worker with a D1 database holds the items. State comes from two sources merged on one stable key per item: a sync step that reads each repo's plan documents, and live events pushed by agents and hooks. Item types, colours and the project list come from configuration; the code holds no project data.
Related MCP server: wirk-mcp
Develop
npm ci
npm run lint && npm run typecheck && npm testTests run in the Workers pool against a local D1. npm run dev (Vite with the Worker) reads
.dev.vars (copy .dev.vars.example); raw wrangler dev has no built assets and is not used. Deploys happen only through Cloudflare Workers Builds on merge to
main, whose deploy command is npm run deploy:ci (D1 remote migrations, then deploy).
The board page
A React + TypeScript page (web/, built by Vite) served by the Worker as static assets: a
"Waiting for you" strip, one group per project, tiles by type and priority, a detail panel
(side panel on desktop, bottom sheet on the phone), light and dark colours from the board
config, fonts bundled with the page. It reads GET /api/board, which answers with the open
items, those done in the window, their details, links and latest events, and the config the
page draws with (colours and labels from BOARD_CONFIG, filled from config/board.example.json).
The page and /api/board are closed until Cloudflare Access is set up: the Worker refuses
every request that has no valid Access JWT, and refuses all of them while the Worker secrets
ACCESS_TEAM_DOMAIN and ACCESS_AUD are unset. /mcp keeps its bearer tokens.
npm run build # vite build: page to web/dist/client, Worker bundle beside it
npm run test:e2e # Playwright (chromium) at 1440x900 and 390x844, /api/board faked
npx playwright install chromium # once
npm run seed # BOARD_URL=<worker>/mcp BOARD_WRITE_TOKEN=<token>; --dry-run prints the callsnpm run dev runs the Worker behind the same gate, so the real page can be opened only through
Cloudflare Access (there is no local bypass). The E2E tests serve the bare page with
vite --mode e2e (no Worker, no gate); that mode refuses to start or build unless
playwright.config.ts sets its env flag.
Worker secrets (never in the repo; wrangler secret put <NAME>): BOARD_WRITE_TOKEN (all
tools), BOARD_READ_TOKEN (list_open, get_item), OWNER_PASSPHRASE (the claude.ai sign-in
page, see OAuth for claude.ai), ACCESS_TEAM_DOMAIN, ACCESS_AUD and the
optional BOARD_CONFIG (one JSON string, see config/board.example.json: window hours, staleAfterMinutes,
projects, type labels and colours). The last three are secrets too because the pipeline deploy
(wrangler deploy) replaces dashboard plain-text vars with the config file's and the file holds
none, while it keeps secrets. In BOARD_CONFIG a type's old single color key is no longer read:
use its light and dark colour sets.
OAuth for claude.ai
claude.ai connects from Anthropic's cloud and signs in with OAuth, so /mcp also accepts OAuth
tokens next to the bearer tokens (@cloudflare/workers-oauth-provider, storage in the KV
binding OAUTH_KV). To add the board: in claude.ai open Settings, Connectors, add a custom
connector with the URL https://<your-worker-host>/mcp; claude.ai opens the board's sign-in
page, you type the owner passphrase and allow. An OAuth caller is read-only
(list_open, get_item); writes need a bearer write token.
Endpoints:
/.well-known/oauth-protected-resource/mcp,/.well-known/oauth-authorization-server,/oauth/register(open registration, limited to Claude's redirect addresses),/authorize,/oauth/token.The owner check is the Worker secret
OWNER_PASSPHRASE, compared in constant time; unset or shorter than 32 characters, the page refuses everyone. Nothing counts or locks wrong tries: the long passphrase is what makes guessing hopeless. Approval always grants read; the page shows the client's name and the full address (with port) the access is sent to.Extra redirect addresses (exact strings) go in
BOARD_CONFIGasoauth_redirect_uris.The issuer and resource default to the origin of the request. To pin them (so the workers.dev name and a custom domain do not issue tokens that fail on each other), set
public_origininBOARD_CONFIGto an https origin, for example{"public_origin": "https://board.example.org"}. Once it is set, every client, bearer tokens included, must use that origin: the other hostnames of the Worker (for example the workers.dev name) answer 401.Changing
OWNER_PASSPHRASEonly guards new sign-ins; access already granted keeps working until the grant's refresh token expires. To end it now, revoke the grant: the provider's helperenv.OAUTH_PROVIDER.listUserGrants("owner")lists the owner's grants andrevokeGrant(grantId, "owner")ends one (from the installed@cloudflare/workers-oauth-providertypes). The Worker has no admin route that calls them.Setup: the KV namespace is created by the pipeline deploy (the binding has no id in
wrangler.jsonc); set the passphrase withwrangler secret put OWNER_PASSPHRASE.Locally:
OWNER_PASSPHRASEin.dev.vars(see.dev.vars.example).
MCP tool reference
Writing a client (hook, script, skill)? See the client guide.
One endpoint: POST /mcp (Streamable HTTP, stateless, JSON responses) with
Authorization: Bearer <token> (a static token, or an OAuth token from the flow above). A
missing or wrong token gets 401 with a WWW-Authenticate header pointing at the resource
metadata. A read token calling a
write tool gets a tool error and nothing is written. Invalid input returns a tool error
naming the field; nothing is written.
Enums: type = slice | problem | waiting_for_me | bug | unplanned; status =
open | in_progress | blocked | done | stale; priority = P0 | P1 | P2 | P3 (default P2).
Keys are stable and chosen by the reporter, for example <project>/slice-58.
Tool | Scope | Inputs | Returns |
| write |
| the item |
| write |
| the item |
| write |
| the item |
| read | optional | items not done, plus items done inside the window, each with its latest 20 events |
| read |
| the item with all its events, newest first |
| write |
|
|
Optional fields on report_progress and ask_human: leave one out to keep the stored value, send
null to clear parent, why, details_md, links or source. An empty string for note,
why, details_md or parent is a tool error naming the field.
An item has key, project, parent, type, priority, status, title, why,
details_md, links, source, heartbeat_at, created_at, updated_at, done_at. A
report that changes nothing but the heartbeat writes an event with the note Heartbeat.
A Workers cron trigger (every 15 minutes, triggers in wrangler.jsonc) turns a live
in_progress or blocked item whose heartbeat is older than staleAfterMinutes (config,
default 120, 60 to 10080) to stale and writes the event Heartbeat expired; a new report on
the key brings it back. Items only doc sync set never go stale.
A plain HTTPS POST works without an MCP client or an initialize call (both Accept
types are required):
curl -s https://<your-worker-host>/mcp \
-H "Authorization: Bearer $BOARD_WRITE_TOKEN" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"report_progress",
"arguments":{"key":"demo-app/slice-58","project":"demo-app","type":"slice",
"title":"Tag search","parent":"Wave 3","status":"in_progress"}}}'License
MIT, see LICENSE. Public but unsupported: issues may not get answers.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Project tracker for AI agents and teams: file, claim, update and hand off tickets over MCP.
Project management shared by people and AI agents, with persistent project state through MCP.
Minimal issue tracker: projects, objectives and trackable plans, written by agents over MCP.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Related MCP Servers
- AlicenseBqualityCmaintenanceProvides a local-first MCP interface for managing SQLite-backed projects, boards, and tickets, including metrics, epics, documentation links, run-history, and staging-lease coordination with completion summaries for done items.32MIT
- AlicenseBqualityBmaintenanceEnables AI agents to coordinate work and ticketing over MCP through five tools for checking status, querying items by ID, field, topic or receipt, writing batched changes and links with revision expectations, reviewing proposals, and rendering shareable pages. Supports JSON output for structured data and idempotent requests for safe retries.5Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to take and progress tasks, hand in completed work with evidence, and enables users to publish, search, and retrieve guides, file bugs, manage inbox/board/activity/logs, and plan tasks over MCP.MIT
- AlicenseNot gradedqualityAmaintenanceExposes an MCP workflow that lets AI coding providers claim and track tasks, log actions, coordinate lead/explorer/consultant/builder/reviewer handoffs, and manage specification documents on the filesystem. Completion is gated on server-owned health checks, so finished work requires passing verification evidence rather than a provider's own claim.29 npmMIT