Log inSubmit server
Taiga MCP Server logo

Taiga MCP Server

by @madebyclowd

Connects MCP-compatible assistants to Taiga for querying and updating project-management data.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Taiga MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "madebyclowd-taiga-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@madebyclowd/taiga-mcp-server"
      ],
      "env": {
        "TAIGA_BASE_URL": "YOUR_VALUE_HERE",
        "TAIGA_TOKEN": "YOUR_VALUE_HERE",
        "TAIGA_USERNAME": "YOUR_VALUE_HERE",
        "TAIGA_PASSWORD": "YOUR_VALUE_HERE",
        "LOG_LEVEL": "YOUR_VALUE_HERE",
        "HTTP_ALLOWED_ORIGINS": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

@madebyclowd/taiga-mcp-server connects MCP-compatible assistants to Taiga Cloud or self-hosted Taiga through the Taiga API. It supports reading and changing projects, epics, user stories, tasks, issues, sprints, wiki pages, comments, attachments, members, votes, watches, and related data through natural-language requests. The server runs locally over stdio or as a shared HTTP service, with each HTTP request carrying the caller's Taiga token. Reach for it when an assistant needs to inspect or maintain Taiga work without custom API code.

Use cases

  • List open issues in a Taiga project
  • Create tasks under the current sprint
  • Move user stories between workflow columns
  • Summarize changes made to an epic
  • Search wiki pages for project procedures

Key features

  • Taiga Cloud and self-hosted instance support
  • CRUD access for core project-management entities
  • Natural-language reference and member lookups
  • Pagination and configurable response verbosity
  • Batch creation, search, voting, and watching
  • stdio and shared HTTP operating modes

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 1h ago via OSV.dev · @madebyclowd/taiga-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
npm downloads423Package downloads in the last 30 days.
Last commit10d agoMost recent push to the default branch.

How Taiga MCP Server works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Taiga MCP Server

@madebyclowd/taiga-mcp-server is an MCP server that connects Claude, Cursor, Windsurf, and other MCP-compatible assistants to Taiga Cloud or self-hosted Taiga. Its tools read and update projects, epics, user stories, tasks, issues, sprints, wiki pages, comments, attachments, members, votes, watches, and search results.

Install it by letting an MCP client run `npx -y @madebyclowd/taiga-mcp-server`, or install it globally with npm or pnpm. Add the package command to the client's `mcpServers` configuration and provide the Taiga URL plus token or username and password.

Yes, it works with self-hosted Taiga when `TAIGA_BASE_URL` is set to the URL of the self-hosted instance. Authentication can use a Taiga access token or the configured username and password.

Yes, run the `taiga-mcp-server-http` command to expose a shared `/mcp` endpoint. Each client sends its own Taiga token in the Authorization header, preserving individual Taiga permissions and audit trails.

Claude Desktop, Claude Code, Cursor, and Windsurf are supported MCP clients for this server. The setup uses an `mcpServers` configuration entry, and the server also supports other MCP-compatible assistants.

Related MCP servers

All in Product Management All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTaiga MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/madebyclowd-taiga-mcp-server?style=directory)](https://allmcps.com/mcp/madebyclowd-taiga-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/madebyclowd-taiga-mcp-server"><img src="https://allmcps.com/api/badge/madebyclowd-taiga-mcp-server?style=directory" alt="Taiga MCP Server on AllMCPs" /></a>