taiga-delegate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | HTTP port used when MCP_TRANSPORT=http. Default is 8765. | 8765 |
| TAIGA_URL | Yes | Taiga API base URL (e.g. https://taiga.example.com or https://api.taiga.io). | |
| TAIGA_TOKEN | No | Alternative to TAIGA_USERNAME/TAIGA_PASSWORD for Taiga authentication. | |
| MCP_TRANSPORT | No | Transport mode: stdio (default) or http. | stdio |
| MCP_USAGE_LOG | No | Path to the usage JSONL log. Default is usage.jsonl. | usage.jsonl |
| MCP_AUTH_TOKEN | No | Full-access bearer token. Required in HTTP mode. | |
| TAIGA_PASSWORD | No | Agent account password for Taiga authentication. | |
| TAIGA_USERNAME | No | Agent account username for Taiga authentication. | |
| MCP_SCOPED_TOKENS | No | Scoped collaborator tokens in the format label:token:project_id:epic_id[,epic_id...][;more]. |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| taiga_list_projectsA | List all accessible Taiga projects with ID, name, slug. |
| taiga_get_projectB | Get project details: members, statuses, roles, priorities, issue types. |
| taiga_create_projectB | Create a new Taiga project (owned by the connected account). Returns id and slug. |
| taiga_add_project_memberA | Invite a user to a project by email with a role (e.g. 'Product Owner', 'Back'). Existing Taiga users are added; unknown emails get an invitation. |
| taiga_list_user_storiesB | List user stories. Filter by status, sprint_id, epic_id, or assigned_to username. |
| taiga_get_user_storyB | Get full story details including description, tasks, and comments. |
| taiga_create_user_storyA | Create a user story with subject, description (acceptance criteria), tags, sprint, assignee, and optional epic. IMPORTANT: epic_id must be the internal numeric ID, NOT the ref # shown in the UI — call taiga_list_epics or taiga_resolve_ref first to get the internal ID. |
| taiga_bulk_create_storiesA | Create multiple user stories. Each needs 'subject', optionally 'description', 'tags'. IMPORTANT: epic_id must be the internal numeric ID (not ref #) — call taiga_list_epics first to get it. |
| taiga_update_user_storyC | Update story fields: subject, description, status (by name), sprint_id, assigned_to, tags. Pass 'comment' to post a comment in the same call. |
| taiga_delete_user_storyA | Permanently delete a user story. Irreversible — confirm with the user before bulk deletions. |
| taiga_list_epicsB | List all epics in a project with their status, assignee, and story count. |
| taiga_get_epicB | Get full epic details including description and linked user stories. |
| taiga_create_epicB | Create an epic to group related user stories under a high-level goal. |
| taiga_update_epicB | Update epic fields: subject, description, status (by name), assigned_to, tags, color. Pass 'comment' to post a comment in the same call. |
| taiga_delete_epicA | Permanently delete an epic (its stories survive, unlinked). Irreversible. |
| taiga_link_story_to_epicA | Link an existing user story to an epic. Both epic_id and story_id must be internal IDs (not ref #s). Use taiga_resolve_ref to convert ref numbers first. |
| taiga_unlink_story_from_epicC | Remove a user story from an epic. |
| taiga_list_issuesA | List all issues in a project. Returns summary fields only — use taiga_get_issue for the description and comments. |
| taiga_get_issueA | Get full issue details including description AND comments. taiga_list_issues returns only subject/status/assignee, so this is the only way to read what an issue actually says. Takes the internal id — use taiga_resolve_ref to convert a # ref first. |
| taiga_create_issueC | Create an issue with type, priority, severity. |
| taiga_update_issueA | Update an issue: subject, description, status (e.g. 'Closed' to resolve), priority, severity, assignee, tags. Pass 'comment' to post a comment in the same call. |
| taiga_delete_issueB | Permanently delete an issue. Irreversible. |
| taiga_list_sprintsC | List all sprints/milestones for a project. |
| taiga_get_sprintC | Get sprint details with all stories in the sprint. |
| taiga_create_sprintC | Create a new sprint. Dates in YYYY-MM-DD format. |
| taiga_create_taskC | Create a task, optionally linked to a user story or sprint. |
| taiga_list_wiki_pagesC | List all wiki pages in a project (slug and title). |
| taiga_get_wiki_pageC | Get the full content of a wiki page by its slug. |
| taiga_create_wiki_pageC | Create a new wiki page. Slug should be lowercase with hyphens (e.g. 'sprint-retrospective'). |
| taiga_update_wiki_pageB | Update the content of an existing wiki page by slug. Creates it if it doesn't exist. |
| taiga_delete_wiki_pageC | Permanently delete a wiki page by slug. Irreversible. |
| taiga_add_commentC | Add a comment to a userstory, task, issue, or epic. |
| taiga_searchC | Search across stories, tasks, issues, wiki in a project. |
| taiga_resolve_refA | Convert a display reference number (e.g. #12 shown in the UI) to the internal ID. ALWAYS use this before commenting on or updating a story/task/issue by its # number. |
| mcp_usage_statsA | Per-token MCP usage stats: total calls, denials, top tools, first/last seen for each token label. Owner (full token) only. |
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 35 tools
Most tools are cleanly separated by resource and CRUD verb. Minor overlap exists between taiga_create_user_story and taiga_bulk_create_stories, and between taiga_add_comment and update tools that accept inline comments, but boundaries remain understandable. mcp_usage_stats is unrelated to the Taiga domain and slightly muddies the set.
Nearly all tools follow a predictable taiga_verb_noun convention with snake_case. The lone mcp_usage_stats tool breaks both the prefix and domain pattern. Aside from that outlier, naming is highly consistent.
At 35 tools, the surface is heavy for a project-management server and exceeds the rubric's 25+ threshold. While Taiga has many resources, the count feels inflated by partial CRUD sets and utility tools rather than a tightly scoped surface.
Coverage is strong for stories, issues, epics, and wiki pages, including delete operations. However, tasks only support create with no list/get/update/delete, sprints lack update/delete, projects lack update/delete, and membership/comments only support add. These gaps will block common agent workflows.