Use kanman from Claude Code or Codex

You can use kanman from your own Claude Code or Codex. One connection covers your whole workspace: every team, every story you can see in kanman. You sign in once in the browser; there is no key to copy and nothing to set up per team or per story.

Your coding tool then works with kanman the way you do in the app, with your role:

• find stories, take one yourself and hand it back with a note;
• see stories and decisions, and answer them;
• ask kanman, as in your conversation in the app.

Everything it changes is recorded as you.

Connect Claude Code

Run this once, in any terminal:

claude mcp add --transport http --scope user kanman https://api.kanman.ai/functions/v1/mcp

Then start Claude Code, type /mcp, choose kanman and Authenticate. Your browser opens:

1. Sign in to kanman, if you are not signed in yet.
2. kanman asks: Allow Claude Code to work in kanman as you? It shows your account and the workspace. If you belong to several workspaces, pick the one this connection is for.
3. Click Allow. The browser goes back to Claude Code, and the kanman tools appear.

Claude Code keeps the connection and renews it on its own. You do not need to sign in again unless you disconnect it.

The command is also in the app: open Your settings > API tokens and find the connection for Claude Code or Codex (one per workspace). A story page links there too (Work on it in Claude Code).

Connect Codex

codex mcp add kanman --url https://api.kanman.ai/functions/v1/mcp
codex mcp login kanman

codex mcp login opens the browser for the same sign-in. Then start Codex in your repository.

Which team kanman works on

kanman picks the team from the repository you are in. Your coding tool asks kanman who you are and passes the repository’s address (git remote get-url origin); kanman answers with the team that works on that repository. If two teams work on the same repository, kanman lists both and your coding tool asks you which one you mean.

You can always name the team instead (“work on the payments team”), or a story key such as PAY-12: a story key finds its own team.

Work on a story yourself

In your repository, ask Claude to find a story and take it, for example:

Find the story about the CSV export in kanman and assign it to me.

A story assigned to you is yours: kanman does not start on it. Work on it in your own checkout, push and open the merge request as you always do; your CI and your code host’s rules apply as for any change.

When you are done, or when kanman should take over, hand it back with a note, for example:

Write "@kanman done, the endpoint is merged" on the story and assign it back to kanman.

kanman reads the note the next time it looks at the board and continues with the work that waited for it. See Handing work back and forth.

What your coding tool can do

Your coding tool can do what you can do in kanman, never more. A viewer can read but not change anything; members and admins can work on stories. The tools and their inputs are listed in the MCP tools reference.

What needs me? Ask your coding tool this and it shows the questions kanman has for you right away, each with the options kanman sees. Tell your coding tool your choice and it answers the item for you; the answer applies to every story the item covers and shows in the app, Slack and Teams within seconds. Why did kanman merge INT-241? gets the answer from what kanman recorded at the time.

Text that kanman passes on from others, such as a story’s description from a tracker or a CI log, is marked as data for your coding tool, so instructions hidden in it are not followed.

Disconnect

Open Your settings > API tokens (avatar menu). Under Connected apps you see every app that works in kanman as you, with its workspace and when it was last used. Click Disconnect to stop it at once. To use it again, sign in from it once more.

CI and scripts

Where nobody can sign in in a browser, use a workspace API token instead:

1. Create a token in Your settings > API tokens for the workspace.
2. Store it as a secret, for example KANMAN_API_KEY, and pass it as a header:

claude mcp add --transport http kanman https://api.kanman.ai/functions/v1/mcp \
  --header "Authorization: Bearer $KANMAN_API_KEY"

A token covers working on stories. Answering decisions, talking to kanman and the other tools that act as you need the browser sign-in.

Related

• MCP tools reference
• Use kanman without a tracker
• Decisions