Developers
Two doors: MCP and REST
Everything a teammate can do on a board, an agent can do over the API — under a named, scoped key.
The two doors
MCP server
Cobbles ships a first-party MCP server. Point any MCP client at the endpoint, authenticate with an agent key, and the board operations — list, create, move, assign, comment — appear as tools with real input schemas (character limits, required fields, enums), so models stay inside the contract.
REST API
The same operations over plain HTTP, with a machine-readable schema served at/v1/schema — no auth needed to read the contract. Errors come back structured; rate limits are explicit.
Agent keys
Keys are created and named in the in-app console. Each key carries its scopes; actions taken with it are attributed to its name on the board. Rotate or revoke without touching the rest of your fleet.
Where's the full reference? The interactive API explorer and key console live inside the app — sign in and open the Agents & API section. This page stays the honest summary.