# @madebyclowd/taiga-mcp-server [Health: Active]

**Category:** 📋 Product Management  
**Repository:** https://github.com/madebyclowd/taiga-mcp-server  
**GitHub Stars:** 3  
**npm Downloads (last month):** 423  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/madebyclowd-taiga-mcp-server

## Description
MCP server connecting Claude, Cursor, Windsurf, and other AI assistants to Taiga (Cloud and self-hosted) — projects, epics, user stories, tasks, issues, sprints, wiki, and more.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "taiga-mcp-server": {
    "command": "npx",
    "args": ["-y","@madebyclowd/taiga-mcp-server"],
    "env": {
      "TAIGA_BASE_URL": "",
      "TAIGA_TOKEN": "",
      "TAIGA_USERNAME": "",
      "TAIGA_PASSWORD": "",
      "LOG_LEVEL": "",
      "HTTP_ALLOWED_ORIGINS": ""
    }
  }
}
```

**Requires environment variables:** `TAIGA_BASE_URL`, `TAIGA_TOKEN`, `TAIGA_USERNAME`, `TAIGA_PASSWORD`, `LOG_LEVEL`, `HTTP_ALLOWED_ORIGINS` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What @madebyclowd/taiga-mcp-server does

@madebyclowd/taiga-mcp-server exposes Taiga project-management operations to MCP-compatible AI assistants. It can work with Taiga Cloud and self-hosted instances, allowing an assistant to retrieve or modify common planning and delivery data through conversational requests.

Supported areas include projects, epics, user stories, tasks, issues, sprints or milestones, wiki pages, comments, attachments, project members, voting, watching, reference lookups, batch creation, and search. The server can resolve a person by email address or full name using the project's member list, rather than requiring the caller to supply a numeric user ID.

Responses include pagination information and support `minimal`, `standard`, or `full` verbosity. This helps keep list results manageable in an assistant conversation. Dedicated filter-data lookups can return valid IDs for user-story, task, and issue filters without traversing an entire collection. A raw-request capability covers Taiga API endpoints that do not yet have a dedicated operation, including examples such as webhooks and import/export functions.

## How it works

In the normal stdio arrangement, an MCP client launches the package locally with `npx` and communicates with it directly. The server then calls Taiga's API using either an access token or username and password. Operations remain constrained by the permissions of the Taiga account used for the connection.

An HTTP mode is also available for a shared deployment. Clients send requests to the `/mcp` endpoint and include their own Taiga token in an Authorization header. This keeps users' credentials and Taiga permissions separate instead of requiring a shared account. The package labels operations as read-only, safe to repeat, or data-changing so clients can distinguish inspection from mutation.

## Setup and configuration

The runtime requires Node.js 22.11 or newer, or Node.js 24 or newer, plus a Taiga account on Taiga Cloud or a self-hosted instance. A client can run the package on demand with `npx -y @madebyclowd/taiga-mcp-server`, or use a globally installed package.

Configure `TAIGA_BASE_URL` with the Taiga API address. The documented default is `https://api.taiga.io`; self-hosted users should replace it with their instance URL. Authentication can use `TAIGA_TOKEN`, which avoids storing a password, or the `TAIGA_USERNAME` and `TAIGA_PASSWORD` pair.

Claude Desktop, Claude Code, Cursor, and Windsurf use an `mcpServers` configuration entry with the package command and environment variables. Restarting the client or reloading its MCP connections makes the Taiga tools available.

For HTTP deployments, run the package's `taiga-mcp-server-http` command. If the service is reachable from the public internet, configure `HTTP_ALLOWED_ORIGINS` restrictively rather than relying on its permissive local or team-use default.

## Tools and capabilities

- Read and update Taiga projects, epics, user stories, tasks, issues, and sprints.
- Create, edit, and remove comments, and work with wiki pages and attachments.
- Download attachments and manage project-member-related operations.
- Apply voting and watching actions.
- Resolve Taiga references such as `#436` to the corresponding item.
- Create multiple records in a batch and search supported Taiga data.
- Look up filter IDs for user stories, tasks, and issues.
- Control response detail with the `verbosity` setting and inspect whether more pages remain.
- Use a raw API request for endpoints without a dedicated operation.

## Limitations and notes

This is an independent open-source integration rather than an official Taiga product. It does not grant permissions beyond those held by the configured Taiga account. In shared HTTP mode, each caller must provide a Taiga token with the request, and public deployments should restrict allowed origins.

_Full upstream README: https://allmcps.com/mcp/madebyclowd-taiga-mcp-server/readme_