Use kanman from Claude Code

Connect your own Claude Code to an AI team in one click, take the next Ready story, work in your own checkout and let kanman check the result and keep the evidence on the story.

Developers can work on an AI team’s stories from their own Claude Code. Claude takes the next Ready story, works in your checkout with your own git access, and kanman checks the result against the acceptance criteria and keeps the evidence on the story. This works with or without a tracker, and with or without repositories connected to the team.

Create your connection

  1. Open the team’s settings, Claude Code. A story page links there too: Work on it in Claude Code.
  2. Click Create my connection.

kanman creates a personal key for you in one click. The key:

  • works only for this team, and only with kanman’s Claude Code connection
  • expires after 90 days
  • is shown only once, so copy the command right away
  • replaces your previous connection when you create a new one

The page shows the exact command with your key filled in. It has this shape:

claude mcp add --transport http kanman \
  https://api.kanman.ai/functions/v1/executor-mcp/teams/<team> \
  --header "Authorization: Bearer km_..."

Run it in a terminal inside your repository, then start Claude Code there.

Ask for the next story

Ask Claude for the next story, for example:

Take the next story from kanman, implement it in this repository and commit it. Then submit it for review with the branch and the diff (git diff main...HEAD).

To work on a specific story, name its key, for example “work on PAYME-3”.

What happens

  1. Claude gets the next story from the team’s Ready column (or the story you named) and moves it to In progress.
  2. Claude implements the story in your checkout, with your own git access. On the way it reports progress, can ask the team a question (it appears under Decisions) and checks the team’s policy before it touches sensitive paths.
  3. When the work is committed, Claude submits the branch, the diff and, if you opened one, the merge or pull request URL. Pushing and opening the merge request stay with you, the way you always do it.
  4. kanman checks the change against the acceptance criteria: it reviews the submitted diff and checks the team’s policy limits, such as denied paths and the size of the change. Then it posts the evidence on the story.
  5. If something is missing, Claude sees what to fix the next time it looks at the story, fixes it and submits again.
  6. When everything passed, Claude completes the story and it moves on to Review or Done, depending on the team’s columns.

No git host token needed

kanman needs no token for your GitHub or GitLab for this. Your code stays in your checkout, and only the diff you submit reaches kanman.

On a team without a repository, no acceptance spec runs, and the evidence says that the outcome is not proven. See Use kanman without a tracker.

The tools Claude uses

Tool What it does
List stories Shows the team’s stories in Ready, In progress and Review, and whether someone works on them
Get story Reads the story: acceptance criteria, Demonstrate step, test plan and the team’s policy summary
Start work Moves the story to In progress
Report progress Posts a short progress line for the team
Ask a teammate Asks the team a question; it appears under Decisions
Check policy Asks whether something is allowed before trying it, for example a path
Submit for review Hands in the branch, the diff and optionally the merge or pull request URL for checking
Complete work Moves the story on once the checks have passed

Parameters and results are in the MCP tools reference.

Codex

Codex works the same way. Add the same address to Codex’s MCP configuration and pass your key as the bearer token, for example in ~/.codex/config.toml:

[mcp_servers.kanman]
url = "https://api.kanman.ai/functions/v1/executor-mcp/teams/<team>"
bearer_token_env_var = "KANMAN_API_KEY"

Set KANMAN_API_KEY to the km_ key from the command, then start Codex in your repository.

Last updated: January 1, 0001

Open kanman