Tapd MCP Server

TAPD MCP Server - 在 Cursor/Copilot 中查询、分析和回填 TAPD bug / 需求. The tapd mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

Agent 会先用 tapd_search_users 确认各成员 nick，再用 tapd_list_bugs（跨项目聚合）逐个统计，汇总出全组视图：每人的未关闭、今日新增、超 24h / 72h、挂起等数量，并可按成员拆分明细。配合客户端的可视化能力（如 Cursor Canvas），还能直接生成下面这样的看板，组长盯进度一目了然。

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Its toolset

Everything the assistant can do here goes through one of these:

• TAPD_ACCESS_TOKEN — 必填。TAPD 个人访问令牌，获取路径：TAPD 个人设置 → 个人访问令牌。请只放在本机 MCP 配置里，不要提交到代码仓库
• TAPD_ALLOW_RAW_WRITE — 可选，默认关闭。设为 true 后才允许 tapd_call_api 发起 POST 写操作（每次调用仍需你在对话中确认），详见下文「通用透传」
• TAPD_MCP_SENTRY_DSN — 可选。默认已启用错误上报（详见下文「错误上报与隐私」）；设为空字符串可关闭，或填自己的 DSN 覆盖默认上报目标
• tapd_list_stories — 查询需求列表，支持跨项目聚合与多字段过滤
• tapd_get_stories — 获取需求完整详情（描述、评论、附件、内嵌媒体）
• tapd_create_story — 创建需求，支持处理人、优先级、迭代、父需求、标签、排期、工时、自定义字段等
• tapd_writeback_story — 回填需求评论 / 描述 / 状态 / 处理人，及标题、优先级、迭代、工时、标签等标准字段和自定义字段
• tapd_list_story_changes — 查询需求变更历史
• tapd_list_story_test_cases — 查询需求关联的测试用例
• tapd_list_bugs — 查询缺陷列表，支持跨项目聚合与多字段过滤
• tapd_get_bugs — 获取缺陷完整详情（描述、复现、评论、附件、内嵌媒体）
• tapd_create_bug — 创建缺陷，支持处理人、优先级、严重程度、版本、迭代、排期、各类人员、工时、自定义字段等

Configuration

You will need 2 environment variables: TAPD_ACCESS_TOKEN, TAPD_MCP_SENTRY_DSN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Tapd.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the tapd mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Tapd's toolset — TAPD_ACCESS_TOKEN, TAPD_ALLOW_RAW_WRITE, TAPD_MCP_SENTRY_DSN and 11 more — is a fair guide to whether it matches your workflow. It is maintained by scizuixiangsis; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.