Zuuna for AI agents: agent builds, git rules move the card

Your coding agent works in your repo anyway. From now on it can see the board too: the Zuuna MCP server gives it cards, columns and comments, and Zuuna's git integration keeps the board pinned to reality rather than to the last manual update. The whole loop is four steps:

The loop in four steps

1. The agent reads the board. Over the MCP server it sees the board as it is: columns in order, cards with keys like ZNA-2001, priority, type. You name the card, or you let it pick.
2. The agent builds in the repo. Claude Code, Cursor or Codex write the code, with their own tools, in your repository. The card key goes into the commit.
3. The pull request merges. Review runs as always, through your tools and your rules. Nothing about it is automated.
4. Git links the card. Commits, PRs and releases land on the card without a single manual board update; releases and deploy gates flip when your git tag and your pipeline say so. The card moves to the next column only through an automation rule on your board, such as "pull request merged → Review". No rule is preinstalled; you add it once per board.

No more "did anyone move the card?" in standup. The board is not a reminder of what somebody should have entered. It is the record of what happened in the repo. How commits and cards get linked is covered in Link commits to cards automatically; how rules move cards on git events, in Move cards automatically with git.

The eight MCP tools

The server, mcp-server-zuuna, speaks the Zuuna v1 API and is deliberately board I/O: no deploy tool, no git write access.

Tool	What it does
zuuna_me	Token identity: organization, plan, scopes
zuuna_boards	List boards
zuuna_board	One board assembled: columns in order plus all cards
zuuna_card	Card detail by key (ZNA-2001) or id
zuuna_create_card	Create a card, column by id or title
zuuna_update_card	Edit title, description and priority
zuuna_move_card	Move a card to another column
zuuna_comment	Comment on a card

Two details that matter in practice: a hard WIP limit stays a hard WIP limit for agents too (the error comes back as a tool error carrying the API's own message), and 4xx answers are never silently retried.

How the agent runs the board itself, rather than only working cards off it, is covered in Kanban board for AI agents; how Claude Code keeps an app project on track across many sessions, in Claude Code project management.

Setup: Claude Code, Cursor, Codex

Two ingredients: an API token from your Zuuna workspace and the server itself. Give the token exactly the scopes the agent should have. A read-only observer needs only boards:read and cards:read; the full loop adds cards:write and comments:write. Creating the token is covered in Create an API token and make your first call.

As of today: the server is on npm as mcp-server-zuuna 0.1.2: publicly installable, tested (CI with ESLint, a TypeScript build and vitest), MIT-licensed. The package is public; the source repository behind it is private. The normal path is a single npx line:

It is configured through environment variables: ZUUNA_API_TOKEN (required), ZUUNA_BASE_URL (defaults to https://app.zuuna.de) and optionally ZUUNA_TIMEOUT_MS (default 15000). Node.js 20 or later.

Claude Code:

claude mcp add zuuna \
  -e ZUUNA_API_TOKEN=zk_live_your_token \
  -- npx -y mcp-server-zuuna

Cursor (in ~/.cursor/mcp.json or the project's .cursor/mcp.json):

{
  "mcpServers": {
    "zuuna": {
      "command": "npx",
      "args": ["-y", "mcp-server-zuuna"],
      "env": { "ZUUNA_API_TOKEN": "zk_live_your_token" }
    }
  }
}

Codex (in ~/.codex/config.toml):

[mcp_servers.zuuna]
command = "npx"
args = ["-y", "mcp-server-zuuna"]
env = { "ZUUNA_API_TOKEN" = "zk_live_your_token" }

From source (alternative): If you would rather build than run npx, that works too. The repository is private, so you need access. Then:

git clone https://github.com/kenzotp/mcp-server-zuuna && cd mcp-server-zuuna && npm install && npm run build

…and in all three configurations above, replace npx -y mcp-server-zuuna with node /path/to/mcp-server-zuuna/dist/index.js.

Honest scope: what Zuuna does not do for agents

• Zuuna does not write code. The agents build: Claude Code, Cursor, Codex. Zuuna provides the interface and the verifiable board truth. That is all.
• Zuuna does not decide anything. There is no built-in project-management AI that plans, prioritizes or closes work. The board mirrors the repo; agents and humans do the rest.
• Zuuna does not deploy. The MCP server is deliberately without deploy or git-write tools. Deploys run through your pipeline; the gates on the board flip only when your process says so.

See it yourself

We are happy to walk you through the loop on your own board instead of a recorded demo: get in touch. If you would rather read first: Project management for developers and Git on the board.