Tapd MCP Server Setup (Archived): A Guide to Legacy Integrations

This article provides information on the archived go-tapd/mcp project for integrating with Tapd. Note that official support for MCP is now available. This project is no longer maintained. If you're looking for actively supported solutions, consider exploring Tapd's official documentation for current integration methods. If needed, you still can use the archived project with this guide.

Understanding the go-tapd/mcp Project (Archived)

The go-tapd/mcp project aimed to facilitate integration with Tapd using MCP (MCP Servers). While no longer maintained, its legacy setup might be useful in specific situations. This guide will focus on the command-line setup.

Setting up the STDIO Server for Tapd

This method involves building and running the tapd-mcp-server command-line application.

• Clone the repository: Begin by cloning the go-tapd/mcp repository from GitHub:

  git clone [email protected]:go-tapd/mcp.git
  

• Build the server: Navigate to the cloned directory and build the tapd-mcp-server executable:

  cd mcp && make build/cmd/tapd-mcp-server
  

• Run the server: Execute the built server using the following command:

  ./bin/tapd-mcp-server
  

This command starts the STDIO server, which listens for requests and interacts with the Tapd API.

Configuring the MCP Server for Tapd Integration

To configure the server, you need to provide your Tapd credentials and workspace ID. Here's an example configuration using Cline:

• Configuration structure: The configuration requires specifying the command to execute the server and environment variables for authentication:

  {
    "mcpServers": {
      "github.com/go-tapd/mcp": {
        "command": "{path}/tapd-mcp-server",
        "env": {
          "TAPD_CLIENT_ID": "<YOUR_CLIENT_ID>",
          "TAPD_CLIENT_SECRET": "<YOUR_CLIENT_SECRET>",
          "TAPD_WORKSPACE_ID": "<YOUR_WORKSPACE_ID>"
        }
      }
    }
  }
  

  Copy
• Replace placeholders: Replace <YOUR_CLIENT_ID>, <YOUR_CLIENT_SECRET>, and <YOUR_WORKSPACE_ID> with your actual Tapd API credentials and workspace ID.

Working with SSE Server

Alternatively, you could set up an SSE server. This legacy method offers more complexity.

• Install the package:

  go get github.com/go-tapd/mcp
  

  Copy
• Create a server: Here is example code:

  package main
  import (
  	"log"
  	"net/http"
  	"github.com/go-tapd/mcp"
  	"github.com/go-tapd/tapd"
  )
  func main() {
  	client, err := tapd.NewClient("client_id", "client_secret")
  	if err != nil {
  		log.Fatal(err)
  	}
  	workspaceID := 123456 // replace with your workspace ID
  	srv, err := mcp.NewServer(workspaceID, client)
  	if err != nil {
  		log.Fatal(err)
  	}
  	http.HandleFunc("/", srv.ServeHTTP)
  	if err := http.ListenAndServe(":8080", nil); err != nil {
  		log.Fatal(err)
  	}
  }
  

  Copy
• Visit: Open http://localhost:8080/sse to get the SSE stream.

Legacy Features of the go-tapd/mcp Project

The archived go-tapd/mcp project included features for retrieving requirements and user information from Tapd.

• Requirements: You could retrieve all requirement templates that match specified query criteria.
• Users: The project allowed fetching the mapping of project role IDs.

Important Considerations

• Project is archived: Note that the go-tapd/mcp project is no longer actively maintained. Use it with caution and be aware of potential security vulnerabilities or compatibility issues.
• Explore alternatives: Consider exploring official Tapd integration methods for actively supported and more robust solutions.
• License: The go-tapd/mcp project is licensed under the MIT License.