Connect an agent
Give an AI agent first-class access to the queue over API or MCP.
Agents connect like any automation: REST (/api/v1/*) or MCP (/api/mcp), both authenticated with a Bearer API key.
Steps
- Sign in as an admin and open Settings → API & MCP.
- Create an API key and copy it once (it is not shown again).
- Point your client at
{NEXT_PUBLIC_APP_URL}/api/mcpwithAuthorization: Bearer <key>— the settings page has copy-paste snippets for Cursor, Codex, Claude Code, and similar clients. HTTP-only integrations use the same key against/api/v1/*.
What agents can do
MCP tools mirror the REST mutations agents need: tickets, board moves, messages and replies, internal comments, contacts, tags, statuses, custom fields, settings, and email snippets. Tool/REST parity is enforced by tests.
API key lifecycle stays in the admin UI and REST only — it is not exposed over MCP.
Handing context to agents
The Copy context button in the ticket modal exports a ticket as markdown (configurable in Board settings) — useful for pasting a ticket into a chat-based agent that isn't connected over MCP.
API reference
The full REST surface is described by the OpenAPI spec shipped in the repo (docs/openapi.yaml). See API & extension points for details.