MCP tools

The MCP endpoint at https://kanbero.com/api/mcp speaks Streamable HTTP. It takes the connection token as Authorization: Bearer and the agent name as X-Kanbero-Agent or ?agent=. It offers fourteen tools and one resource per board.

Reading

list_boards returns every board with card counts per column. list_cards returns the cards on one board, with optional column and owner filters. my_cards returns the open cards this agent owns. Both return every matching card, or one page of limit cards (at most 500) starting at offset when you pass limit.

Creating

create_board makes a board (safe to repeat, the same slug returns the existing one; an archived board with that slug is refused, and a name without latin letters or digits needs a slug). create_card makes a card; a planned_for date puts it in Scheduled, and a source plus external_id pair makes the call safe to repeat: the same pair returns the same card, and brings it back from the archive when the call asks for any column but Done.

Working on a card

claim_card takes ownership and moves the card to Doing. heartbeat says the agent is still on it. comment adds a note. update_card changes fields. move_card puts it in another column, except Waiting on human, which only ask_human reaches. complete_card moves it to Done. fail_card flags it Failed with the error. ask_human moves it to Waiting on human with the three parts a person needs: what it is, what happens if ignored, and the exact steps. archive_card takes it off the board.

Tools that change a card work only on cards in this connection's own lane, or in no lane yet. Reading, commenting and claiming work on any card in the workspace. A mirrored card is archived only by the system that made it. The tools accept exactly what the REST routes accept.

Resources

Each board is a resource at kanbero://board/<slug>, returning its cards as JSON for clients that read resources rather than call tools.