addCommentLABSCO SUMMARY
It reaches past tickets into the structure around them — epics, sprints, a wiki — and gives you a query language for finding things in it.
Two parts do the heavy lifting. Batch creation takes up to twenty items at once and reports each outcome separately, so a sprint's worth of stories is one call instead of twenty. And the query syntax is precise enough to be worth learning — run it past the help and validation tools first rather than guessing at the operators.
What it is
An MCP server over the Taiga API, authenticated with your own account, covering the whole board rather than just the ticket list.
What you get
- Projects and sprints: list projects and read one, list milestones, create one, read its progress statistics, and pull the issues inside it
- User stories: list, read, create, assign to a sprint and update status
- Tasks created against a user story
- Issues end to end: list, read, create, add to a sprint, assign, and update status
- Batch creation for issues, user stories and tasks — up to twenty at a time, with each item's success or failure reported separately so one bad row does not sink the rest
- An SQL-like query language: field:operator:value combined with AND, OR and NOT, fuzzy and wildcard text matching, date ranges, and ORDER BY and LIMIT — with a help tool that explains the syntax and a validator that checks a query before you run it
- Comments on any work item: add, list, edit and delete
- Attachments uploaded from a file path or as base64, then listed, downloaded and deleted
- Epics for the layer above stories: create, list, read and update them, and link or unlink user stories
- A wiki: create, list, read, update, delete and watch pages
Requirements
A Taiga account with API access, and Node.js v14 or higher. Three environment variables carry the connection: TAIGA_API_URL (https://api.taiga.io/api/v1 for the hosted service, or your own instance's /api/v1 endpoint), TAIGA_USERNAME and TAIGA_PASSWORD. Run it over stdio with npx taiga-mcp-server, or as a Docker container reading the same variables from an env file or -e flags.
Setup effort
One command plus credentials — npx taiga-mcp-server, then supply credentials
USE CASES
Getting connected and seeing what you have access to
Authenticate, then list the projects the account can reach.
Planning a sprint in one pass
Create the milestone, batch-create the stories, then assign them to it.
Seeing where the sprint actually stands
Read the milestone's completion statistics, then the issues still open inside it.
Finding work with a precise filter rather than scrolling
Read the query syntax, validate the query you wrote, then run the search.
Discussing an item where the work lives
Read the existing thread, then add your comment to it.
Organising above the story level
Create the epic, then link the stories that belong under it.
46 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
addIssueToSprintadvancedSearchassignIssueassignUserStoryToSprintauthenticatebatchCreateIssuesbatchCreateTasksbatchCreateUserStoriescreateEpiccreateIssuecreateMilestonecreateTaskcreateUserStorycreateWikiPagedeleteAttachmentdeleteCommentdeleteWikiPagedownloadAttachmenteditCommentgetEpicgetIssuegetIssuesByMilestonegetMilestonegetMilestoneStatsgetProjectgetUserStorygetWikiPagelinkStoryToEpiclistAttachmentslistCommentslistEpicslistIssueslistMilestoneslistProjectslistUserStorieslistWikiPagesqueryHelpunlinkStoryFromEpicupdateEpicupdateIssueStatusupdateUserStoryStatusupdateWikiPageuploadAttachmentvalidateQuerywatchWikiPageBEFORE YOU INSTALL
What to know first
Tools you get
46 tools when we connected. updateUserStoryStatus, which moves a user story to a new status such as Done, is undocumented, and the documentation's totals (42, 45 and 39) are all out of date. Tool names are camelCase.
Requires
- npx on PATH
- Node.js
- TAIGA_USERNAME in your environment
- TAIGA_PASSWORD in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Moderate Standing cost
Rated by the size of the 46 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
npx taiga-mcp-serverMCP Clients
Claude Desktop — npx
{
"mcpServers": {
"taiga-mcp": {
"command": "npx",
"args": [
"taiga-mcp-server"
],
"env": {
"TAIGA_API_URL": "https://api.taiga.io/api/v1",
"TAIGA_USERNAME": "<YOUR_TAIGA_USERNAME>",
"TAIGA_PASSWORD": "<YOUR_TAIGA_PASSWORD>"
}
}
}
}