The workflow as an MCP server
Every workflow’s board is also an MCP server, so outside agents — Claude Code, Codex, Kiro, Devin, anything that speaks MCP — can read cards, move them and trigger the worker on a station.
- Part
- F-16
- Status
- Live
- In one line
- Outside agents can drive the line
A workflow has an MCP endpoint with a scoped token. What a token may do is what its scopes say: a read-only token can only read, a write token can create, move and delete cards, and triggering a column’s worker is its own capability.
This is how CodeBook joins a toolchain rather than replacing it. A coding agent in your editor can file the card it just discovered it needs, move it, and start the QA worker on it; a nightly job can move a release along; a support tool can open a bug where the QA agent will find it. A move made over MCP obeys the same rules as a drag.
Related parts
F-15
Tool connections
A catalogue of MCP servers — live documentation, web search, GitHub, Linear, Stripe, Supabase and more. Every tool is off until you switch it on, and a station cannot use any of them until you allow that station.
F-03
Triggers
A card dropped into the station, a card created there, a comment left on one. Each is a switch you turn on per station, so work starts when it is ready rather than when somebody remembers.
F-14
Repositories and pull requests
Connect GitHub, GitLab, a self-hosted Gitea or the git host inside CodeBook to a workflow and its engineering agents read the code, make the change on a branch and open a draft pull request — never a merge. When the pull request is merged, the card moves.
Ready to run
Don’t build your own software factory. Assemble one.
Build the factory. Pick the workers. Define how work moves. CodeBook runs it.
Sign in with your Bookbag account