TaigaMcpServer MCP Server

Full-featured MCP server for Taiga project management with advanced sprint and issue tracking. Based on mcpTAIGA by adriapedralbes, enhanced with

Remote serverstreamable-http

What is the TaigaMcpServer MCP server?

TaigaMcpServer MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Full-featured MCP server for Taiga project management with advanced sprint and issue tracking. Based on mcpTAIGA by adriapedralbes, enhanced with substantial modifications. Developed collaboratively with Claude Code (AI-assisted.

What you get

A powerful Model Context Protocol (MCP) server that enables natural language interaction with Taiga project management systems. Seamlessly manage your projects, sprints, user stories, tasks, and issues through conversational AI.

What the assistant can call

Once TaigaMcpServer is connected, these are the calls the assistant has available:

  • listProjects — Get all accessible projects
  • getProject — View detailed project information
  • listMilestones — List all sprints in a project
  • getMilestone — Get complete sprint details including user stories, watchers, owner, timeline, metrics, and full JSON data
  • getMilestoneStats — Get sprint progress and statistics
  • createMilestone — Create new sprints with dates
  • getIssuesByMilestone — View all issues in a sprint
  • listIssues — List issues with sprint info
  • getIssue — Get detailed issue information
  • createIssue — Create issues with priorities/types
  • updateIssueStatus — Update issue status (e.g., "In Progress", "Done")
  • addIssueToSprint — Assign issues to sprints or remove from sprints

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration and credentials

You will need 3 environment variables: TAIGA_API_URL, TAIGA_USERNAME, TAIGA_PASSWORD. 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.

  • Node.js (v14 or higher) - Download here - Taiga account with API access

Choosing this one

Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. TaigaMcpServer's toolset — listProjects, getProject, listMilestones and 11 more — is a fair guide to whether it matches your workflow. It is maintained by greddy7574; 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.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch TaigaMcpServer.
  • 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 taigamcpserver mcp server does with a few real requests.

Available tools

ToolWhat it does
listProjectsGet all accessible projects
getProjectView detailed project information
listMilestonesList all sprints in a project
getMilestoneGet complete sprint details including user stories, watchers, owner, timeline, metrics, and full JSON data
getMilestoneStatsGet sprint progress and statistics
createMilestoneCreate new sprints with dates
getIssuesByMilestoneView all issues in a sprint
listIssuesList issues with sprint info
getIssueGet detailed issue information
createIssueCreate issues with priorities/types
updateIssueStatusUpdate issue status (e.g., "In Progress", "Done")
addIssueToSprintAssign issues to sprints or remove from sprints
assignIssueAssign issues to team members or unassign
listUserStoriesView user stories in a project

How to install the TaigaMcpServer MCP server

#### Docker Method
```json
{
  "mcpServers": {
    "taiga-mcp": {
      "command": "docker",
      "args": [
        "run", 
        "--rm", 
        "-i",
        "-e", "TAIGA_API_URL=https://api.taiga.io/api/v1",
        "-e", "TAIGA_USERNAME=your_username",
        "-e", "TAIGA_PASSWORD=your_password",
        "taiga-mcp-server:latest"
      ]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js (v14 or higher) - Download here - Taiga account with API access
VariableDescriptionRequired
TAIGA_API_URLEndpoint or connection string the server talks to.Yes
TAIGA_USERNAMEConfiguration value read at startup.Optional
TAIGA_PASSWORDConfiguration value read at startup.Optional

Example prompts to try

  • Use TaigaMcpServer to listProjects.
  • Use TaigaMcpServer to getProject.
  • Use TaigaMcpServer to listMilestones.

Frequently asked questions

It connects TaigaMcpServer to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (listProjects, getProject, listMilestones, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with TaigaMcpServer directly.