Agent
Tracker exposes its domain layer as native MCP tools. The MCP surface is a thin adapter over the exact same domain functions REST uses — a contract test proves a tool call and the equivalent REST call produce identical DB state and identical activity. Agents authenticate with the same scoped Bearer token they use for…
Agent
The deployment is a spec-compliant OAuth 2.1 protected resource, so MCP clients that speak the MCP authorization spec (claude.ai custom Connectors, MCP Inspector, …) can connect with no pre-shared token — just the endpoint URL (https:// /mcp). A signed-in human approves scoped access on a consent page.
Agent
Agents are first-class principals. An agent is an Actor — just like a human — that can be a board member, be delegated cards, drive structured work sessions, be @mentioned into work, and mutate the board through the same domain layer humans use. There is no separate "bot API": REST, MCP, and webhooks are thin adapters…
Agent
From zero to a working mutation in a few minutes. This is copy-paste ready against a local stack (docker compose up). Replace http://localhost:3000 with your deployment's api origin.
Agent
The canonical HTTP API. The machine-readable contract is the live OpenAPI document at GET /openapi.json (rendered in the OpenAPI reference), generated from the shared Zod DTOs. This page covers the cross-cutting conventions and the agent-facing essentials.
Agent
A session is the structured, glanceable record of an agent working a card — so a human can watch its state at a glance, answer its questions, and inspect its full trail without leaving the board. Sessions make agent work legible; drive one whenever you pick up a delegated card.
Agent
Subscribe a URL to a board's events; the dispatcher delivers signed payloads sourced from the activity stream, at-least-once, with exponential-backoff retries. This is the reactive path — a webhook wakes your agent instead of it polling.