Taiga MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Taiga MCP Server Show me the user stories in the 'Website Redesign' project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Taiga MCP Server
MCP (Model Context Protocol) server to integrate Taiga with Claude and other LLM clients.
Manage projects, sprints, user stories, tasks, issues, epics, and wiki directly from your assistant.
Requirements
Node.js >= 20
Access to a Taiga instance (cloud or self-hosted)
Taiga authentication token
Related MCP server: Taiga MCP Server
Installation
cd taiga
npm install
npm run buildGetting the Taiga token
curl -s -X POST https://<your-instance>/api/v1/auth \
-H "Content-Type: application/json" \
-d '{"type":"normal","username":"<username>","password":"<password>"}' \
| grep auth_tokenConfiguration
Environment variables
Variable | Description | Example |
| Base URL of your Taiga instance |
|
| Authentication token obtained in the previous step |
|
| Logging verbosity (default: |
|
Claude Desktop (~/.config/Claude/claude_desktop_config.json)
{
"mcpServers": {
"taiga": {
"command": "node",
"args": ["/absolute/path/to/taiga/dist/index.js"],
"env": {
"TAIGA_URL": "https://<your-instance>",
"TAIGA_AUTH_TOKEN": "<your-token>"
}
}
}
}Claude Code (.claude/settings.json)
{
"mcpServers": {
"taiga": {
"command": "node",
"args": ["/absolute/path/to/taiga/dist/index.js"],
"env": {
"TAIGA_URL": "https://taiga.mycompany.com",
"TAIGA_AUTH_TOKEN": "your-token-here"
}
}
}
}Available tools (31 total)
Projects
Tool | Description |
| List all projects |
| Project detail by ID or slug |
| Create a new project |
| List members of a project |
Sprints (Milestones)
Tool | Description |
| List sprints of a project |
| Sprint detail |
| Create a sprint |
User Stories
Tool | Description |
| List user stories with filters |
| User story detail |
| Create a user story |
| Edit a user story (requires |
| Delete a user story |
Tasks
Tool | Description |
| List tasks with filters |
| Task detail |
| Create a task |
| Edit a task (requires |
| Delete a task |
Issues
Tool | Description |
| List issues with filters |
| Issue detail |
| Create an issue |
| Edit an issue (requires |
| Delete an issue |
Epics
Tool | Description |
| List epics of a project |
| Epic detail |
| Create an epic |
| Edit an epic (requires |
Wiki & Search
Tool | Description |
| List wiki pages of a project |
| Get a wiki page by ID or slug |
| Create a wiki page |
| Edit a wiki page (requires |
| Global search within a project |
Development
npm run dev # Watch mode compilation
npm run build # Production build
npm start # Start the compiled serverArchitecture
See SPECS.md for detailed tool specifications.
See DECISIONS.md for the design decisions log.
src/
├── index.ts # Entry point and MCP server configuration
├── types.ts # TypeScript interfaces for all Taiga entities
├── formats.ts # Formatting functions for readable responses
├── logger.ts # Structured logger (DEBUG/INFO/WARN/ERROR), configurable via LOG_LEVEL
├── errors.ts # TaigaApiError class with HTTP status differentiation
├── services/
│ └── taiga.ts # HTTP client and Taiga API functions
└── tools/ # One file per entity, each registers its MCP tools
├── projects.ts
├── milestones.ts
├── userstories.ts
├── tasks.ts
├── issues.ts
├── epics.ts
└── wiki-search.tsAvailable Tools
31 toolstaiga_create_epicC
Create a new epic in a project
Inputs: subject (required), project_id (required), tags, color, +3 more.
taiga_create_issueC
Create a new issue in a project
Inputs: subject (required), project_id (required), tags, type, +6 more.
taiga_create_milestoneB
Create a new sprint in a project
Inputs: name (required), project_id (required), estimated_start (required), estimated_finish (required).
taiga_create_projectC
Create a new project in Taiga
Inputs: name (required), is_private, description.
taiga_create_taskC
Create a new task in a project
Inputs: subject (required), project_id (required), tags, status, +4 more.
taiga_create_userstoryB
Create a new user story in a project
Inputs: subject (required), project_id (required), tags, status, +3 more.
taiga_create_wiki_pageA
Create a new wiki page in a project
Inputs: slug (required), content (required), project_id (required).
taiga_delete_issueA
Permanently delete an issue
Inputs: issue_id (required).
taiga_delete_taskA
Permanently delete a task
Inputs: task_id (required).
taiga_delete_userstoryA
Permanently delete a user story
Inputs: userstory_id (required).
taiga_edit_epicA
Edit an existing epic. Fetch the current version with taiga_get_epic before editing.
Inputs: epic_id (required), version (required), tags, color, +4 more.
taiga_edit_issueA
Edit an existing issue. Fetch the current version with taiga_get_issue before editing.
Inputs: version (required), issue_id (required), tags, type, +7 more.
taiga_edit_taskA
Edit an existing task. Fetch the current version with taiga_get_task before editing.
Inputs: task_id (required), version (required), tags, status, +5 more.
taiga_edit_userstoryA
Edit an existing user story. Fetch the current version with taiga_get_userstory before editing.
Inputs: version (required), userstory_id (required), tags, status, +4 more.
taiga_edit_wiki_pageA
Edit the content of a wiki page. Fetch the current version with taiga_get_wiki_page before editing.
Inputs: content (required), page_id (required), version (required).
taiga_get_epicA
Get full details of an epic by ID
Inputs: epic_id (required).
taiga_get_issueA
Get full details of an issue by ID
Inputs: issue_id (required).
taiga_get_milestoneA
Get details of a sprint by ID, including its user stories
Inputs: milestone_id (required).
taiga_get_projectA
Get details of a project by ID or slug
Inputs: slug, project_id.
taiga_get_taskB
Get full details of a task by ID
Inputs: task_id (required).
taiga_get_userstoryA
Get full details of a user story by ID
Inputs: userstory_id (required).
taiga_get_wiki_pageA
Get a wiki page by ID, or by project + slug
Inputs: slug, page_id, project_id.
taiga_list_epicsB
List all epics in a project
Inputs: project_id (required), page, page_size.
taiga_list_issuesC
List issues with optional filters
Inputs: page, type, status, priority, +5 more.
taiga_list_membersB
List the members of a project
Inputs: project_id (required).
taiga_list_milestonesB
List sprints in a project
Inputs: project_id (required), page, closed, page_size.
taiga_list_projectsA
List all accessible Taiga projects
Inputs: page, page_size.
taiga_list_tasksC
List tasks with optional filters
Inputs: page, status, page_size, project_id, +3 more.
taiga_list_userstoriesC
List user stories with optional filters
Inputs: page, tags, status, page_size, +3 more.
taiga_list_wiki_pagesB
List all wiki pages in a project
Inputs: project_id (required), page, page_size.
taiga_searchA
Full-text search across a project (searches epics, user stories, issues, tasks, and wiki)
Inputs: text (required), project_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 31 tools
Each tool targets a distinct resource-action pair (e.g., list_issues vs. get_issue vs. create_issue), and resource types are clearly separated. The only cross-resource tool is taiga_search, which is explicitly described as full-text search, so no ambiguity exists.
All tools follow a consistent 'taiga_<verb>_<resource>' pattern with standard verbs (list, get, create, edit, delete). Plural nouns are used for list operations and singular for others, making the naming scheme highly predictable.
With 31 tools, the server far exceeds the typical well-scoped range (3-15) and even the 'heavy' range (16-25). While each tool has a clear purpose, the large number feels excessive for a single server, especially given incomplete CRUD coverage across resource types.
User stories, tasks, and issues have full CRUD operations, but projects, milestones, epics, and wiki pages lack delete operations, and projects and milestones also lack edit operations. These are notable gaps in lifecycle coverage that agents cannot fully work around.
Maintenance
Related MCP Connectors
Sprints, stories, tasks, issues, epics, wiki and attached files in Taiga; writes only when allowed.
Laviya project management: read and update tasks, wikis, sprints and test cases.
Manage projects, tasks, time tracking, and team collaboration through natural language.
Open your team's project from the AI you use: read and write its brief, documents, tasks and notes.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables seamless integration between Large Language Models and Taiga project management platform, allowing users to manage projects, user stories, tasks, and team collaboration through natural language commands.4GPL 3.0
- AlicenseDqualityDmaintenanceEnables natural language interaction with Taiga project management systems, allowing management of projects, sprints, user stories, tasks, and issues through conversational AI.4654 npm7ISC
- AlicenseCqualityDmaintenanceEnables natural language interaction with Taiga project management tool to list projects, view details, and create user stories.69ISC
- AlicenseBqualityDmaintenanceFull-featured MCP server for Taiga project management, enabling AI agents to manage projects, epics, user stories, tasks, issues, sprints, wiki pages, memberships, and roles via Taiga API v1.10039 npm6MIT