Taiga MCP Server

Connect Claude, Cursor, Windsurf, or any other MCP-compatible AI assistant to your Taiga project management tool — read and update epics, user stories, tasks, issues, sprints, comments, and wiki pages just by chatting, in plain English. No coding required to use it.

In plain words: MCP (Model Context Protocol) is a standard that lets an AI assistant safely use outside tools — like reading your files or browsing the web. This package is that "tool" for Taiga: it's the bridge that lets your AI assistant see and change things in your Taiga account when you ask it to.

Package on npm: @madebyclowd/taiga-mcp-server

Not an official Taiga product. This is an independent, open-source integration.

---

Table of contents

• What can I actually do with this?
• Before you start
• Install
• Set it up with Claude Desktop, Claude Code, Cursor, or Windsurf
• Running it as a shared HTTP server instead
• All settings (environment variables)
• What's covered, and how it handles problems
• Frequently asked questions
• Contributing / running the tests
• Security
• License

---

What can I actually do with this?

Once it's connected, you can ask your AI assistant things like:

• "Show me all open bugs in the Website project."
• "Create a task called 'Fix login button' under the current sprint."
• "Move user story #482 to the QA column."
• "Summarize what changed on epic #12 this week."
• "Search the wiki for our deployment steps."

You don't type any code or API calls yourself — you just ask, in normal sentences, and the assistant does the rest.

Behind the scenes, the assistant does this by calling this server, which talks to Taiga's real API using your own Taiga login. It only does what your Taiga account is already allowed to do — it can't see or change anything you don't already have permission for in Taiga itself.

It supports:

• Projects, epics, user stories, tasks, issues, sprints (milestones), wiki pages, comments (including edit/delete), attachments (including download), project members, voting/watching, ref lookup (#436 → the right item), batch create, and search. If it's in Taiga, there's a good chance this covers it.
• Assign people by email or full name instead of hunting down a numeric user id — the server figures out who you mean from the project's member list.
• Every response tells the AI assistant whether more results are waiting (paging) and lets it ask for a shorter or fuller version of the data (a verbosity setting: minimal/standard/full). In plain terms: asking "list my backlog" won't dump a wall of raw data into your conversation and eat up the assistant's memory of what you've been talking about — it gets just enough to answer you.
• Cheap filter-id lookups (user_story_filters_data, task_filters_data, issue_filters_data) instead of paging through a full list just to find a valid status or tag id.
• Each tool is clearly labeled as read-only, safe-to-repeat, or something that changes data — so your AI assistant (and you) can tell at a glance what's harmless to run and what deserves a second look before confirming.
• A fallback "raw request" tool for the rare Taiga API endpoint that doesn't have a dedicated tool yet (webhooks, import/export, and similar admin-level features).

Before you start

You need:

1. A Taiga account — either on Taiga Cloud or a self-hosted Taiga instance.
2. Node.js version 22.11 or newer, or version 24 or newer.
3. An AI assistant that supports MCP — Claude Desktop, Claude Code, Cursor, Windsurf, or any other MCP-compatible client.

You do not need to install or run anything Taiga-related yourself — this connects to your existing Taiga account over the internet (or your self-hosted instance's URL).

Install

You don't need to install this by hand. Your AI assistant will download and run it automatically the first time it's used, via npx. If you'd rather install it yourself:

# Run it once, without installing anything permanently
npx -y @madebyclowd/taiga-mcp-server

Or install it globally, using whichever package manager you already use — you only need one of these:

pnpm add -g @madebyclowd/taiga-mcp-server
# or
npm install -g @madebyclowd/taiga-mcp-server

Set it up with Claude Desktop, Claude Code, Cursor, or Windsurf

All of these tools use the same kind of config file, usually a JSON file with an mcpServers section. Add this to yours:

Option A: using a Taiga access token (recommended)

This is the safer option — your password is never stored anywhere.

1. Log into Taiga in your browser.
2. Get your auth token (in Taiga Cloud, this is available via your account settings or the API; for self-hosted Taiga, ask your admin how tokens are issued).
3. Add this to your config:

{
  "mcpServers": {
    "taiga": {
      "command": "npx",
      "args": ["-y", "@madebyclowd/taiga-mcp-server"],
      "env": {
        "TAIGA_BASE_URL": "https://api.taiga.io",
        "TAIGA_TOKEN": "your-taiga-auth-token"
      }
    }
  }
}

Option B: using your username and password

{
  "mcpServers": {
    "taiga": {
      "command": "npx",
      "args": ["-y", "@madebyclowd/taiga-mcp-server"],
      "env": {
        "TAIGA_BASE_URL": "https://api.taiga.io",
        "TAIGA_USERNAME": "your-username",
        "TAIGA_PASSWORD": "your-password"
      }
    }
  }
}

Using self-hosted Taiga? Just change TAIGA_BASE_URL to your own instance's URL, for example https://taiga.mycompany.com.

After saving the config, restart your AI assistant (or reload its MCP connections). It should now show Taiga tools as available.

Running it as a shared HTTP server instead

The setup above (called "stdio") runs a private copy of the server just for you, on your own computer. If you instead want to run one shared server that a team can connect to over the network, use the HTTP mode.

The important difference: in HTTP mode, nobody's Taiga login is stored on the server. Each person connecting sends their own Taiga token with each request, so everyone keeps their own Taiga permissions and audit trail — nobody has to share one account.

# Start the HTTP server — same package, a different command it exposes
npx -y --package=@madebyclowd/taiga-mcp-server -- taiga-mcp-server-http

Each client connects by sending their Taiga token in a standard HTTP header:

POST /mcp HTTP/1.1
Host: your-server:3000
Content-Type: application/json
Authorization: Bearer <your-taiga-auth-token>

If you're exposing this server on the internet (not just on your own machine or local network), read the HTTP_ALLOWED_ORIGINS note in the settings table below — the default is permissive on purpose for easy local/team use, and you should lock it down for a public deployment.

All settings (environment variables)

Used by both modes

| Setting | Required? | What it does | Default | | :-------------------------- | :-------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | :----------------------- | | TAIGA_BASE_URL | Yes | The Taiga API address to connect to. | https://api.taiga.io | | LOG_LEVEL | No | How much the server logs (error, info, debug, etc.). | info | | TAIGA_REQUIRE_ELICITATION | No | true/1 to require a real human-in-loop confirmation for every delete. With this on, a connecting MCP client that doesn't support interactive confirmation (elicitation) can never delete anything — no fallback confirm: true two-call workaround. Leave off for the default behavior, where such clients can still delete via that two-call pattern. | unset (fallback allowed) |

Only for the normal (stdio) mode

| Setting | Required? | What it does | | :--------------- | :----------------------------------: | :--------------------------------------------------------- | | TAIGA_TOKEN | One of these three is required | Your Taiga access token. Preferred over username/password. | | TAIGA_USERNAME | Required if you're not using a token | Your Taiga username. | | TAIGA_PASSWORD | Required if you're not using a token | Your Taiga password. |

Only for HTTP server mode

In HTTP mode, the server itself doesn't hold any Taiga login — each connecting client sends its own token, so none of the settings below are about credentials.

| Setting | Required? | What it does | Default | | :--------------------- | :-------: | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :----------------------- | | HTTP_PORT | No | Which network port the server listens on. | 3000 | | HTTP_ALLOWED_ORIGINS | No | Comma-separated list of websites allowed to connect from a browser (CORS). If unset, any website is allowed — fine for local/team use, but set this explicitly if you're exposing the server publicly. | unset (any site allowed) | | HTTP_SESSION_TTL_MS | No | How long an idle connection stays open before it's automatically closed, in milliseconds. | 1800000 (30 minutes) | | `H