Taiga MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TAIGA_API_URL | No | Base URL of the Taiga REST API (must include /api/v1). | https://api.taiga.io/api/v1 |
| TAIGA_PASSWORD | Yes | Taiga account password. | |
| TAIGA_USERNAME | Yes | Taiga username or email. |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| projectsA | List or inspect Taiga projects and verify credentials. Credentials come from TAIGA_USERNAME and TAIGA_PASSWORD in the environment; the server authenticates on first use. Use whoami to verify them.
| ||||||||||||||||||||||||||||
| workA | Manage Taiga work items (issues, user stories, tasks, epics). Operations:
| ||||||||||||||||||||||||||||
| sprintsA | Manage Taiga sprints (milestones): list, inspect, create, or fetch statistics. Operations:
Sprint deletion is intentionally not exposed: removing a milestone detaches every story and task on it, so it is a board-wide edit that belongs in the Taiga UI. Delete individual work items with the work tool instead. | ||||||||||||||||||||||||||||
| commentsA | List, add, edit, or delete comments on issues, user stories, tasks, epics, and wiki pages. Note: Taiga soft-deletes comments on delete. | op | required args | optional args | | list | type, item | project, includeDeleted | | add | type, item, text | project | | edit | type, item, commentId, text | project | | delete | type, item, commentId | project | | ||||||||||||||||||||||||||||
| attachmentsA | List, upload, download, or delete attachments across work items and wiki pages.
| ||||||||||||||||||||||||||||
| wikiA | Create, inspect, update, delete, or watch wiki pages in a project.
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| projects | Projects visible to the authenticated user, as JSON. |
TDQS
Scored across 6 tools
Each tool maps to a distinct Taiga resource: projects, work items, sprints, comments, attachments, and wiki. Shared type/item parameters are used for child resources, but the tool purposes do not overlap.
Top-level tool names are simple lowercase resource nouns and are internally consistent. The pattern is slightly mixed because some names are plural resources while work and wiki are singular, and the internal op verbs vary between add/create and edit/update.
Six resource-scoped tools is a well-balanced surface for a project-management server. Each tool represents a meaningful functional area without making the tool list overwhelming.
The server covers most core workflows: project inspection, work-item CRUD, sprints, comments, attachments, and wiki with lifecycle operations. Deliberate gaps such as project creation/deletion and sprint update/delete prevent it from being fully complete.