taiga-mcp

MCP server for the Taiga project management API. Lets AI assistants (Claude, etc.) manage projects, issues, user stories, tasks, epics, sprints, wiki pages, and more through natural language.

Requirements

• Node.js 18+
• A running Taiga instance (cloud or self-hosted)
• Claude Code, Claude Desktop, or any MCP-compatible client

Installation

Option A — via npx (recommended)

No cloning or building required. Run once:

claude mcp add taiga -s user \
  -e TAIGA_URL=https://your-taiga-instance.com \
  -e TAIGA_USERNAME=your_username \
  -e TAIGA_PASSWORD=your_password \
  -- npx -y taiga-mcp

Option B — from source

git clone https://github.com/YOUR_USER/taiga-mcp
cd taiga-mcp
npm install && npm run build

Then register with Claude Code:

claude mcp add taiga -s user \
  -e TAIGA_URL=https://your-taiga-instance.com \
  -e TAIGA_USERNAME=your_username \
  -e TAIGA_PASSWORD=your_password \
  -- node /absolute/path/to/taiga-mcp/dist/index.js

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "taiga": {
      "command": "npx",
      "args": ["-y", "taiga-mcp"],
      "env": {
        "TAIGA_URL": "https://your-taiga-instance.com",
        "TAIGA_USERNAME": "your_username",
        "TAIGA_PASSWORD": "your_password"
      }
    }
  }
}

Environment variables

Authentication

On startup the server logs in with your credentials and stores the JWT access token in memory. On token expiry (401), it automatically refreshes using the refresh token. If the refresh token also expires, it re-logs in with your credentials. Credentials are never sent more than necessary.

Available tools

Projects

Issues

User Stories

Tasks

Milestones / Sprints

Epics

Roles

Members & Lookups

Comments & History

Search

Wiki

Delete

Verify connection

claude mcp list
# taiga: node ... - ✔ Connected

Update (npx install)

npx always pulls the latest published version. No action needed.

Update (source install)

cd taiga-mcp
git pull
npm install && npm run build

License

MIT