Built for agents
There is no separate UI a person operates and an API bolted on beside it — the MCP is the primary interface, for people and agents alike.
Define
- read_backlog
- find_cards
- read_card
- create_card
- update_card
- move_card
- drop_card
- claim_next_card
- create_idea
- claim_next_idea
- update_idea
- drop_idea
- promote_idea
- promote_idea_to_card
Plan
- create_plan
- read_plan
- update_plan
- add_plan_section
- revise_plan_section
- read_plan_history
Build
- record_pull_request
- update_pull_request
- record_review
- update_finding
Land
- record_landing
- record_deploy
Know
- propose_record
- read_record
- revise_record
- link
- unlink
- read_architecture
- add_architecture_section
- revise_architecture_section
- search
- get
The Standard
- read_standard
- save_project_standard
whoami answers who a connection acts as, with exactly that person’s access. describe_schema, search and get are how an agent finds its way around before it reads or writes anything named above.
Permissions follow the person who connected
There is no separate service account with its own standing access. An MCP connection acts as the person who approved it, with exactly their access — whoami answers who that is — so a coding agent never reaches further than the person running it could reach by hand.