原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

MCP Server Zuuna

作者:kenzotp版本 0.3.0i★ –i在你的电脑上运行
注册名称io.github.kenzotp/mcp-server-zuuna

安装

概览

作者提供的说明(英文原文)

MCP server for Zuuna: coding agents work your git-truth kanban board via the v1 API. 73 tools.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 开发者工具
  • 你需要填写:ZUUNA_API_TOKEN

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 需要你自己填写: ZUUNA_API_TOKEN, ZUUNA_BASE_URL, ZUUNA_TIMEOUT_MS

标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "zuuna": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-zuuna"
      ],
      "env": {
        "ZUUNA_API_TOKEN": "your-value",
        "ZUUNA_BASE_URL": "your-value",
        "ZUUNA_TIMEOUT_MS": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add zuuna --env ZUUNA_API_TOKEN=your-value --env ZUUNA_BASE_URL=your-value --env ZUUNA_TIMEOUT_MS=your-value -- npx -y mcp-server-zuuna

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "zuuna": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-zuuna"
      ],
      "env": {
        "ZUUNA_API_TOKEN": "your-value",
        "ZUUNA_BASE_URL": "your-value",
        "ZUUNA_TIMEOUT_MS": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "zuuna": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-zuuna"
      ],
      "env": {
        "ZUUNA_API_TOKEN": "your-value",
        "ZUUNA_BASE_URL": "your-value",
        "ZUUNA_TIMEOUT_MS": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • ZUUNA_API_TOKEN 机密 必填 env
    Bearer API token from your Zuuna workspace. Grant only the scopes the agent needs (boards:read + cards:read is enough for a read-only observer).
  • ZUUNA_BASE_URL env
    Zuuna base URL. Defaults to https://app.zuuna.de.
  • ZUUNA_TIMEOUT_MS env
    Per-request timeout in milliseconds. Defaults to 15000.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 kenzotp 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“开发者工具”中的其他服务器比较i

  • 星标数多于此分类中其他 5135 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 5135 个服务器的 49% 更新
  • 基础检查结果等于或优于此分类中其他 5135 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

MCP Server Zuuna 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:ZUUNA_API_TOKEN

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.3.0)于43天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

作者:github广泛使用★ 3.4万5天前更新

电脑或云端

Desktop Commander

MCP server for terminal commands, file operations, and process management

作者:wonderwhy-er广泛使用↓ 71万/周★ 1万17天前更新

在你的电脑上运行

Cloudflare MCP

Cloudflare MCP servers

作者:cloudflare正在增长★ 444614个月前更新

在云端运行✓ mcp.cloudflare.com

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

mcp-server-zuuna

Agent-native board access for [Zuuna](https://zuuna.de/en/kanban-board-for-ai-agents?utm_source=npm&utm_medium=referral&utm_campaign=mcp-server-readme) — 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 73 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

73 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
ToolMethod + pathScopes
zuuna_meGET /api/v1/menone
Groups
ToolMethod + pathScopes
zuuna_list_groupsGET /api/v1/groupsboards:read
zuuna_list_group_membersGET /api/v1/groups/{groupId}/membersboards:read
zuuna_list_epicsGET /api/v1/groups/{groupId}/epicsboards:read
zuuna_create_epicPOST /api/v1/groups/{groupId}/epicscards:write
zuuna_update_epicPATCH /api/v1/groups/{groupId}/epics/{epicId}cards:write
zuuna_list_group_cardsGET /api/v1/groups/{groupId}/cardscards:read
Boards
ToolMethod + pathScopes
zuuna_boardsGET /api/v1/boardsboards:read
zuuna_boardGET /api/v1/boards/{id}/columns + GET /api/v1/boards/{id}/cardsboards:read, cards:read
zuuna_create_boardPOST /api/v1/boardsboards:write
zuuna_list_columnsGET /api/v1/boards/{boardId}/columnsboards:read
zuuna_list_board_fieldsGET /api/v1/boards/{boardId}/fieldsboards:read
zuuna_create_columnPOST /api/v1/boards/{boardId}/columnsboards:write
zuuna_list_automationsGET /api/v1/boards/{boardId}/automationsboards:read
Cards
ToolMethod + pathScopes
zuuna_cardGET /api/v1/cards/{idOrKey}cards:read
zuuna_list_board_cardsGET /api/v1/boards/{boardId}/cardscards:read
zuuna_search_cardsGET /api/v1/cardscards:read
zuuna_create_cardPOST /api/v1/boards/{boardId}/cardscards:write
zuuna_create_cardsPOST /api/v1/boards/{boardId}/cards ({"cards":[...]})cards:write
zuuna_update_cardPATCH /api/v1/cards/{idOrKey}cards:write
zuuna_move_cardPATCH /api/v1/cards/{idOrKey}cards:write
zuuna_move_card_to_boardPOST /api/v1/cards/{cardId}/movecards:write
zuuna_archive_cardPOST /api/v1/cards/{cardId}/archivecards:write
zuuna_unarchive_cardDELETE /api/v1/cards/{cardId}/archivecards:write
zuuna_delete_card (destructive)DELETE /api/v1/cards/{cardId}cards:write
zuuna_restore_cardPOST /api/v1/cards/{cardId}/restorecards:write
Comments
ToolMethod + pathScopes
zuuna_list_commentsGET /api/v1/cards/{cardId}/commentscomments:read
zuuna_commentPOST /api/v1/cards/{cardId}/commentscomments:write
Checklist
ToolMethod + pathScopes
zuuna_list_checklistGET /api/v1/cards/{cardId}/checklistcards:read
zuuna_add_checklist_itemPOST /api/v1/cards/{cardId}/checklistcards:write
zuuna_update_checklist_itemPATCH /api/v1/cards/{cardId}/checklist/{itemId}cards:write
zuuna_delete_checklist_item (destructive)DELETE /api/v1/cards/{cardId}/checklist/{itemId}cards:write
Relations
ToolMethod + pathScopes
zuuna_list_relationsGET /api/v1/cards/{cardId}/relationscards:read
zuuna_add_relationPOST /api/v1/cards/{cardId}/relationscards:write
zuuna_delete_relation (destructive)DELETE /api/v1/cards/{cardId}/relations/{linkId}cards:write
Attachments

Upload included since ZNA-2170: zuuna_upload_attachment takes a local file path, or base64 bytes plus a filename. List and get still return metadata only, never the bytes themselves.

ToolMethod + pathScopes
zuuna_list_attachmentsGET /api/v1/cards/{cardId}/attachmentscards:read
zuuna_upload_attachmentPOST /api/v1/cards/{cardId}/attachmentscards:write
zuuna_get_attachmentGET /api/v1/cards/{cardId}/attachments/{attachmentId} (metadata only)cards:read
zuuna_delete_attachment (destructive)DELETE /api/v1/cards/{cardId}/attachments/{attachmentId}cards:write
Time tracking
ToolMethod + pathScopes
zuuna_list_card_timeGET /api/v1/cards/{cardId}/timetime:read
zuuna_log_timePOST /api/v1/cards/{cardId}/timetime:write
zuuna_start_timerPOST /api/v1/cards/{cardId}/timetime:write
zuuna_stop_timerPOST /api/v1/cards/{cardId}/timetime:write
zuuna_list_active_timersGET /api/v1/time/activetime:read
zuuna_update_time_entryPATCH /api/v1/time/{entryId}time:write
zuuna_delete_time_entry (destructive)DELETE /api/v1/time/{entryId}time:write
zuuna_import_time_entriesPOST /api/v1/time/entriestime:write
Sprints
ToolMethod + pathScopes
zuuna_list_sprintsGET /api/v1/sprintsboards:read
zuuna_get_sprintGET /api/v1/sprints/{sprintId}boards:read
zuuna_create_sprintPOST /api/v1/sprintscards:write
zuuna_update_sprintPATCH /api/v1/sprints/{sprintId}cards:write
zuuna_add_cards_to_sprintPOST /api/v1/sprints/{sprintId}/cardscards:write
zuuna_remove_card_from_sprintDELETE /api/v1/sprints/{sprintId}/cards/{cardId}cards:write
Recurring cards
ToolMethod + pathScopes
zuuna_list_recurring_cardsGET /api/v1/boards/{boardId}/recurringboards:read
zuuna_create_recurring_cardPOST /api/v1/boards/{boardId}/recurringcards:write
zuuna_update_recurring_cardPATCH /api/v1/recurring/{id}cards:write
zuuna_delete_recurring_card (destructive)DELETE /api/v1/recurring/{id}cards:write
Releases
ToolMethod + pathScopes
zuuna_list_releasesGET /api/v1/releasesboards:read
zuuna_get_releaseGET /api/v1/releases/{releaseId}boards:read
zuuna_create_releasePOST /api/v1/releasesreleases:write
zuuna_update_releasePATCH /api/v1/releases/{releaseId}releases:write
zuuna_delete_release (destructive)DELETE /api/v1/releases/{releaseId}releases:write
Deployments

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

ToolMethod + pathScopes
zuuna_list_deploymentsGET /api/v1/deploymentsboards:read
zuuna_report_deploymentPOST /api/v1/deploymentsdeployments:write
Webhooks
ToolMethod + pathScopes
zuuna_list_webhooksGET /api/v1/webhookswebhooks:manage
zuuna_create_webhookPOST /api/v1/webhookswebhooks:manage
zuuna_update_webhookPATCH /api/v1/webhooks/{id}webhooks:manage
zuuna_delete_webhook (destructive)DELETE /api/v1/webhooks/{id}webhooks:manage
zuuna_test_webhookPOST /api/v1/webhooks/{id}/testwebhooks:manage
zuuna_list_webhook_deliveriesGET /api/v1/webhooks/{id}/deliverieswebhooks:manage
Git on board

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

ToolMethod + pathScopes
zuuna_link_git_branchesPOST /api/v1/git/branchesgit:write
zuuna_report_ci_checksPOST /api/v1/git/checksgit:write
zuuna_record_git_eventsPOST /api/v1/git/eventsgit:write

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.
  • zuuna_me also returns a hiddenTools list: every tool this token's scopes hide, each with the scope or scopes that would unlock it (the same boundary the startup scope-gating applies).
  • 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:

VariableDefaultMeaning
ZUUNA_API_TOKEN— (required)Bearer API token
ZUUNA_BASE_URLhttps://app.zuuna.deZuuna base URL — must be an absolute http(s) URL (invalid values fail at startup); a plain-http value prints a cleartext-token warning to stderr
ZUUNA_TIMEOUT_MS15000Per-request timeout
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":

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx