negoro26/mcp-taiga

A TypeScript MCP server for Taiga. It gives LLM clients six tools for projects, work items, sprints, comments, attachments, and wiki pages.
The server uses MCP revision 2026-07-28, native fetch, and either stdio or streamable HTTP.
Requirements
- Node.js 24 or newer.
- A Taiga account on taiga.io or a self-hosted instance.
- TAIGA_USERNAME and TAIGA_PASSWORD.
Set TAIGA_API_URL for a self-hosted instance. Include /api/v1 in the URL.
| Variable | Purpose | Default |
| --- | --- | --- |
| TAIGA_API_URL | Taiga REST API base URL | https://api.taiga.io/api/v1 |
| TAIGA_USERNAME | Taiga username or email | Required |
| TAIGA_PASSWORD | Taiga password | Required |
| TAIGA_HTTP_PORT | Serve streamable HTTP when set | stdio |
| TAIGA_HTTP_HOST | HTTP bind address | 127.0.0.1 |
Install
Published package
Use the published package from an MCP client that accepts a stdio command:
Pass credentials through the client environment. An npx install does not load a repository .env file.
Local checkout
Fill in .env, then configure the client to run:
A local checkout loads .env with Node's built-in environment loader. Do not commit .env.
Oh My Pi
Start OMP in the checkout and run:
Choose a local stdio server, then use:
Run /mcp test taiga or /mcp list to verify the server. OMP configuration lives in ~/.omp/agent/mcp.json.
HTTP transport
Set TAIGA_HTTP_PORT to serve the same tools over streamable HTTP:
The endpoint is:
Configure URL-based clients with:
The HTTP server is stateless, validates the Host and Origin headers, and defaults to loopback. A routable bind address prints a warning because the connection is not encrypted.
Tools
The server exposes six tools and 28 operation pairs.
| Tool | Operations | Key arguments |
| --- | --- | --- |
| projects | list, get, whoami | project accepts an ID or slug |
| work | list, get, create, update, link, unlink, delete | type, project, item, subject, items |
| sprints | list, get, create, stats | project, sprint, name, start, finish |
| comments | list, add, edit, delete | type, item, text, commentId |
| attachments | list, upload, download, delete | type, item, attachmentId, filePath or fileContent, savePath |
| wiki | list, get, create, update, delete, watch | project, page, content, watch |
Input conventions
- Projects accept a numeric ID or slug.
- Work items accept a numeric ID or a #reference. A reference also needs project.
- Members accept an ID, username, full name, or me.
- Statuses, priorities, severities, issue types, and sprint names resolve to Taiga IDs.
- Batch work-item creation accepts at most 20 items.
- attachments.download returns metadata by default. Set includeContent: true to return bytes, or set savePath to write them locally.
- Listings return dense plain text. Empty lists are successful results.
Safety and reliability
- 401 responses trigger one token refresh and retry.
- 429 responses retry at most twice and honor Retry-After. Waits longer than five seconds fail with a retry message.