MCP Taiga

Communauté Productivité

Taiga project management: issues, user stories, tasks, epics, sprints, comments, attachments and wiki via a compact set of tools.

Installation

Les étapes d'installation sont dans la documentation ci-dessous. Documentation

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Taiga MCP server
  2. Requirements
  3. Install
  4. HTTP transport
  5. Tools
  6. Safety and reliability
  7. Docker
  8. Development
  9. Project layout
  10. Contributing
  11. License

Taiga MCP server

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.

VariablePurposeDefault
TAIGA_API_URLTaiga REST API base URLhttps://api.taiga.io/api/v1
TAIGA_USERNAMETaiga username or emailRequired
TAIGA_PASSWORDTaiga passwordRequired
TAIGA_HTTP_PORTServe streamable HTTP when setstdio
TAIGA_HTTP_HOSTHTTP bind address127.0.0.1

Install

Published package

Use the published package from an MCP client that accepts a stdio command:

{
  "mcpServers": {
    "taiga": {
      "command": "npx",
      "args": ["-y", "mcp-taiga"],
      "env": {
        "TAIGA_USERNAME": "your_username",
        "TAIGA_PASSWORD": "your_password"
      }
    }
  }
}

Pass credentials through the client environment. An npx install does not load a repository .env file.

Local checkout
git clone https://github.com/negoro26/mcp-taiga.git
cd mcp-taiga
npm ci
npm run build
cp .env.example .env

Fill in .env, then configure the client to run:

{
  "mcpServers": {
    "taiga": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-taiga/dist/src/index.js"],
      "cwd": "/absolute/path/to/mcp-taiga"
    }
  }
}

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:

/mcp add

Choose a local stdio server, then use:

command: node
args: /absolute/path/to/mcp-taiga/dist/src/index.js
cwd: /absolute/path/to/mcp-taiga

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:

TAIGA_HTTP_PORT=3000 npx -y mcp-taiga

The endpoint is:

http://127.0.0.1:3000/mcp

Configure URL-based clients with:

{
  "mcpServers": {
    "taiga": {
      "type": "http",
      "url": "http://127.0.0.1:3000/mcp"
    }
  }
}

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.

ToolOperationsKey arguments
projectslist, get, whoamiproject accepts an ID or slug
worklist, get, create, update, link, unlink, deletetype, project, item, subject, items
sprintslist, get, create, statsproject, sprint, name, start, finish
commentslist, add, edit, deletetype, item, text, commentId
attachmentslist, upload, download, deletetype, item, attachmentId, filePath or fileContent, savePath
wikilist, get, create, update, delete, watchproject, 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.
  • 5xx responses are not retried because a write may already have succeeded.
  • Project, user, and taxonomy metadata is cached for 60 seconds.
  • Requests time out after 30 seconds.
  • Attachment downloads reject redirects, cap reads at 10 MB, require the Taiga hostname, and do not send the bearer token to media hosts.
  • File downloads refuse to overwrite an existing file.
  • Deletes accept one target at a time. Batch creation does not imply batch deletion.

Docker

docker build -t mcp-taiga .
docker run --rm -i --env-file .env mcp-taiga

For HTTP mode:

docker run --rm -p 127.0.0.1:3000:3000 \
  -e TAIGA_HTTP_PORT=3000 \
  --env-file .env \
  mcp-taiga

The container uses Node.js 24 Alpine and runs as the non-root node user.

Development

npm ci
npm run check
npm run lint
npm test
CommandPurpose
npm run buildCompile src and test into dist
npm run checkType-check without output
npm run lintRun the TypeScript anti-slop checks with oxlint
npm testRun unit, protocol, contract, and HTTP tests
npm run test:integrationRun the live Taiga smoke test when credentials exist

The test suite covers pure helpers, the MCP stdio handshake, all tool operations against a mock Taiga server, streamable HTTP, and live Taiga reads.

Project layout

src/index.ts             server entrypoint and transport selection
src/http.ts              streamable HTTP transport
src/api.ts               authenticated fetch transport and cache
src/taiga.ts             Taiga domain resolution and patching
src/tools/*.ts           six tool implementations
test/apiContractTest.ts  mock Taiga contract tests
test/protocolTest.ts     stdio MCP tests
test/httpTest.ts         HTTP MCP tests
test/integration.ts      live Taiga smoke test

Contributing

Pull requests target dev. See CONTRIBUTING.md for the branch model and commit rules.

License

MIT

Questions fréquentes

Qu'est-ce que MCP Taiga ?

Taiga project management: issues, user stories, tasks, epics, sprints, comments, attachments and wiki via a compact set of tools.

Comment installer MCP Taiga ?

Suivez les étapes d'installation de sa documentation, affichée sur cette page et dans son dépôt.

MCP Taiga est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient MCP Taiga ?

Il est publié par negoro26. AI.tn le référence sans le maintenir ni le recommander.

Issu des listes communautaires awesome-mcp-servers et du dépôt GitHub du projet. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.