TAPD MCP Server

io.github.scizuixiangsisPublished by GitHub account scizuixiangsisv1.0.2Updated Oct 24, 2026

在 Cursor/Copilot 中查询、分析和回填 TAPD bug / 需求

Overview

AI-generated overview

A local MCP server that lets an AI assistant query, analyze and fill in TAPD bugs and requirements from Cursor or Copilot.

What you can do
Query TAPD bugs and requirements from within the assistant chat, based on the registry description; no individual tools are listed in the manifest, so exact operations are not documented here. Analyze the retrieved bug and requirement records. Write back or fill in TAPD bug and requirement entries. Intended for use inside Cursor or Copilot.
When to use it
Useful when a team tracks bugs and requirements in TAPD and wants an assistant in Cursor or Copilot to look them up, analyze them, or update them without switching to the TAPD web interface.
Requirements
Runs as a local stdio process on the user's machine, installed from the npm package tapd-mcp-server; desktop use only, not web-executable. Requires a TAPD personal access token supplied through the TAPD_ACCESS_TOKEN environment variable. Network access to TAPD is implied.
Before you install
The server needs a TAPD personal access token (TAPD_ACCESS_TOKEN), a credential that should be kept private. It can write back to TAPD bug and requirement records, so changes made through the assistant may alter shared team data; review before confirming. Bug and requirement data is sent to the assistant and the model provider.

Installation

In SourceWeft

  1. Open TAPD MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.