TAPD MCP Server

What TAPD MCP Server MCP server does

TAPD MCP Server MCP server exposes TAPD project data and actions to an MCP-compatible coding assistant. It covers two main work item types: stories and bugs. Agents can search lists across participating workspaces, retrieve full records, inspect comments and attachments, and filter results by supported fields. Results can identify the owning project, which is useful when one person works across several TAPD projects.

The server also supports creating stories and bugs, updating their standard and custom fields, changing status or assignees, and adding comments or descriptions. Attachment tools handle bug files and inline images. Member search helps confirm the correct TAPD nick before changing an assignee.

How it works

The client starts the package with npx -y tapd-mcp-server and passes TAPD_ACCESS_TOKEN through the MCP environment. The token is a TAPD personal access token. Read operations query TAPD without changing records. Write operations require explicit confirmation in the conversation, including creation, comments, status changes, and assignee updates.

For broader coverage, tapd_call_api can send requests to TAPD OpenAPI paths not covered by dedicated tools. POST requests through this passthrough remain disabled unless TAPD_ALLOW_RAW_WRITE=true is set, and they still require confirmation. The bundled prompts coordinate existing tools rather than adding separate write behavior. They can combine TAPD data with the current codebase when the client supports MCP prompts.

Setup and configuration

Add the server to an MCP configuration file such as .cursor/mcp.json or .vscode/mcp.json:

{
  "mcpServers": {
    "TAPD MCP": {
      "command": "npx",
      "args": ["-y", "tapd-mcp-server"],
      "env": {
        "TAPD_ACCESS_TOKEN": "your-token"
      }
    }
  }
}

TAPD_ALLOW_RAW_WRITE is optional and defaults to disabled. Set it to true only when raw POST access is needed. TAPD_MCP_SENTRY_DSN controls the default error reporting destination; setting it to an empty string disables the reporting described by the project.

Tools and capabilities

TAPD MCP Server MCP server provides 18 tools grouped around these functions:

• List and retrieve stories, bug records, changes, and linked test cases.
• Create stories or bugs and write back fields such as status, priority, iteration, labels, workload, comments, and custom fields.
• List workspaces and iterations, then search users by TAPD member information.
• Upload bug attachments up to 250 MB, or inline images up to 5 MB; one tool appends an uploaded image to an existing description without replacing it.
• Call other TAPD OpenAPI endpoints through the guarded passthrough tool.

Three prompts are included: tapd_prd_analysis, tapd_bug_fix_writeback, and tapd_test_doc. They support engineering review before a PRD presentation, a confirmed bug-resolution write-back, and test-entry assessment followed by a generated 提测文档.md file.

Limitations and notes

The toolset does not automatically authorize changes: write actions require confirmation. Raw POST calls need both the environment flag and confirmation. The test-document prompt reads code and does not modify TAPD. Team dashboards and scheduled inspections are agent workflows that combine tools and client capabilities, not single built-in tools. Visualizations depend on the client, and the README specifically gives Cursor Canvas as an example.