Tapd MCP Server

What is Tapd MCP Server?

Tapd MCP Server is a bridge that enables AI assistants to interact with Tapd’s project management data using the Model Context Protocol. It supports querying story templates and user roles. This project is archived because Tapd now provides its own official MCP support.

How to use Tapd MCP Server?

You can run it as a STDIO server by building from source and configuring environment variables TAPD_CLIENT_ID, TAPD_CLIENT_SECRET, and TAPD_WORKSPACE_ID. Alternatively, use the SSE server by installing the Go package and creating a custom HTTP server that listens on port 8080.

Key features of Tapd MCP Server

• Return all story templates matching query criteria.
• Get project role ID‑to‑name mappings.
• Supports both STDIO and SSE transport modes.
• Configurable via environment variables for authentication.
• Written in Go; lightweight and self‑contained.

Use cases of Tapd MCP Server

• Automate retrieval of story templates for AI‑driven requirement analysis.
• Map user roles to project members to enrich AI assistant context.
• Integrate Tapd project data into an MCP‑compatible AI agent.
• Prototype custom MCP servers using Tapd’s API before official support.

FAQ from Tapd MCP Server

Why is this server archived?

Tapd now officially supports MCP, so this third‑party server is no longer maintained.

What are the runtime requirements?

You need Go to build the STDIO server or to run the SSE server. A Tapd API client ID, client secret, and workspace ID are required.

Which transports are available?

STDIO and SSE (HTTP). Configuration examples are provided for STDIO clients like Cline.

What data does it access?

It queries Tapd’s API to list story templates and retrieve project roles. No data is stored locally—all interactions go through Tapd’s API.

Is authentication handled automatically?

Yes. You provide TAPD_CLIENT_ID, TAPD_CLIENT_SECRET, and TAPD_WORKSPACE_ID as environment variables, and the server handles API authentication.