Taiga MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging verbosity (debug, info, warn, error, silent) | info |
| TAIGA_URL | Yes | Base URL of your Taiga instance | |
| TAIGA_AUTH_TOKEN | Yes | Authentication token obtained from Taiga |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| taiga_list_projectsA | List all accessible Taiga projects |
| taiga_get_projectA | Get details of a project by ID or slug |
| taiga_create_projectC | Create a new project in Taiga |
| taiga_list_membersB | List the members of a project |
| taiga_list_milestonesB | List sprints in a project |
| taiga_get_milestoneA | Get details of a sprint by ID, including its user stories |
| taiga_create_milestoneB | Create a new sprint in a project |
| taiga_list_userstoriesC | List user stories with optional filters |
| taiga_get_userstoryA | Get full details of a user story by ID |
| taiga_create_userstoryB | Create a new user story in a project |
| taiga_edit_userstoryA | Edit an existing user story. Fetch the current version with taiga_get_userstory before editing. |
| taiga_delete_userstoryA | Permanently delete a user story |
| taiga_list_tasksC | List tasks with optional filters |
| taiga_get_taskB | Get full details of a task by ID |
| taiga_create_taskC | Create a new task in a project |
| taiga_edit_taskA | Edit an existing task. Fetch the current version with taiga_get_task before editing. |
| taiga_delete_taskA | Permanently delete a task |
| taiga_list_issuesC | List issues with optional filters |
| taiga_get_issueA | Get full details of an issue by ID |
| taiga_create_issueC | Create a new issue in a project |
| taiga_edit_issueA | Edit an existing issue. Fetch the current version with taiga_get_issue before editing. |
| taiga_delete_issueA | Permanently delete an issue |
| taiga_list_epicsB | List all epics in a project |
| taiga_get_epicA | Get full details of an epic by ID |
| taiga_create_epicC | Create a new epic in a project |
| taiga_edit_epicA | Edit an existing epic. Fetch the current version with taiga_get_epic before editing. |
| taiga_list_wiki_pagesB | List all wiki pages in a project |
| taiga_get_wiki_pageA | Get a wiki page by ID, or by project + slug |
| taiga_create_wiki_pageA | Create a new wiki page in a project |
| taiga_edit_wiki_pageA | Edit the content of a wiki page. Fetch the current version with taiga_get_wiki_page before editing. |
| taiga_searchA | Full-text search across a project (searches epics, user stories, issues, tasks, and wiki) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.