Zuuna MCP Server

mcp-server-zuuna

Agent-native board access for Zuuna — a Model Context Protocol server that lets coding agents (Claude Code, Cursor, Codex) read and work a Zuuna board directly.

Agents work the board. Git keeps it honest.

The agent reads the board via this MCP server, does the work in the repo with its own coding tools, and when the PR merges, a rule on your Zuuna board moves the card. Zuuna provides the interface and the verifiable board truth — the agent writes the code, not Zuuna.

Status

Working and tested, and published on npm (npx -y mcp-server-zuuna) after an auth review of the token model, scopes and tool surface. Run from source (bottom) if you want to hack on it.

Hosted alternative

The same 67 tools are also available with nothing to install: Zuuna runs a hosted MCP connector at app.zuuna.de/mcp (OAuth sign-in, Developer plan). Point Claude Code, Cursor or Codex at that URL directly and skip the token and the npx line below. This package exists for the case that does need a local process: a CI runner, an air-gapped agent, or a workflow that wants a plain bearer token instead of an OAuth sign-in. See Kanban board for AI agents for both routes side by side.

Tools

67 tools, grouped by area. Every tool works with any valid token; the Scopes column lists what else the token must carry. The 8 marked destructive refuse to run without an explicit confirm: true argument.

Identity

Groups

Boards

Cards

Comments

Checklist

Relations

Attachments

Metadata only, both ways: no tool here ever reads or writes file bytes (see "Honest scope" below).

Time tracking

Sprints

Recurring cards

Releases

Deployments

Observation only: there is no "trigger a deploy" tool, on the hosted connector either (see "Honest scope").

Webhooks

Git on board

Link commits, branches, PRs and CI status to cards. None of these move a card by themselves (see "Honest scope").

Behavioral notes:

• Errors come back as MCP tool errors with the API's own message (the v1 envelope's message plus status and machine code) — e.g. 409 wip_limit_reached when a HARD WIP limit refuses a move.
• One request, no retries: 4xx answers are never re-sent. Requests time out after 15 s (configurable) and surface as network errors.
• Card display keys like ZNA-2001 work anywhere a card is addressed — the v1 API accepts the key as the handle.
• zuuna_board pages the card list (200 cards per page, the v1 API's own cap) so a big board cannot flood the agent's context. When a page is not the whole board, the response says cardsTruncated: true and carries nextCursor; send it back as cardsCursor to fetch the next page.
• zuuna_create_card accepts an optional client-chosen idempotencyKey: re-sending the same key after a lost response or a 5xx returns the original card (200) instead of minting a duplicate.
• At startup the server reads its own token's scopes (GET /api/v1/me) and registers only the tools they cover, the same scope gating the hosted connector applies. If that read fails (no network yet, an invalid token) it registers every tool instead and prints one line to stderr saying so; every call is still enforced by the API regardless of what got registered.
• Five prompts ship alongside the tools (session_start, session_end, triage_board, standup_summary, plan_sprint), starting points for a client that surfaces MCP prompts, not required for using the tools directly.

Setup

You need an API token from your Zuuna workspace. Give it the scopes for what the agent should be allowed to do — a read-only observer needs only boards:read + cards:read.

The server is configured per client via environment variables:

Claude Code

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

or in the project's .mcp.json:

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

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" }

Run from source

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

then point the client at the built binary instead of npx:

claude mcp add zuuna -e ZUUNA_API_TOKEN=zk_live_your_token -- node /path/to/mcp-server-zuuna/dist/index.js

The loop

1. zuuna_board — the agent sees the board and picks a card (or you tell it: "do ZNA-2001").
2. The agent codes in your repo with its own tools, referencing the card key in commits.
3. The PR merges — and git truth moves the card: Zuuna's git integration (webhooks/CLI) links the commits and the PR to the card, and a rule on the board (for example "PR merged → move to Done") moves it. Linking works out of the box; the move is one rule you add once under the board's Automations. After that the agent never has to touch the board by hand, and the board cannot drift from the repository.

Guides

• Kanban board for AI agents: the agent sets up the board, writes and moves cards, comments and logs its time; the board's rules carry the cards from there.
• Claude Code project management between sessions: a CLAUDE.md routine that keeps an app's plan on the board, so each new session starts where the last one stopped.
• Zuuna for AI agents: the loop from card to merged PR, in English and German.

Honest scope

There is still no tool that triggers a deploy. zuuna_report_deployment (deployments:write) only records what a pipeline already did (building, succeeded, failed); actually shipping stays with your own CI, not the agent.

There are now three git:write tools, and what they do is narrower than the name suggests:

• zuuna_record_git_events and zuuna_report_ci_checks attach commit/branch/PR history and CI status to whichever card a smart-commit reference or description names.
• zuuna_link_git_branches replaces a repo's whole in-flight-branches snapshot in one call.

None of the three moves a card. A card moves only because a board rule matched it (see "The loop" above) or because zuuna_move_card / zuuna_update_card was called directly. Automations themselves stay read-only here too (zuuna_list_automations): no tool creates, edits or disables one. Attachments are metadata-only both ways: no tool reads or writes a file's bytes, uploading included, the same restriction the hosted connector carries.

Development

npm install
npm run lint     # eslint
npm run build    # tsc -> dist/
npm test         # vitest, fully mocked (no network)

Optional live smoke test, strictly read-only (GET /me and GET /boards only — nothing is ever created, moved or commented):

ZUUNA_E2E=1 ZUUNA_API_TOKEN=zk_live_your_token npm run test:e2e

Requires Node.js >= 20.

License

MIT