taigaMcpServer

Taiga MCP Server provides a natural language interface to manage Taiga project management items such as projects, sprints, user stories, tasks, issues, and more. It exposes a conversational layer that translates prompts into Taiga API actions, enabling you to list, create, update, and query elements like sprints, user stories, and issues. The server includes capabilities for batch operations, advanced query syntax, comment threads, attachments, and wiki pages, making it possible to perform complex project management tasks through natural language.

To use the server, run it via the recommended NPX method or install it globally and run taiga-mcp-server. Once running, connect your Claude Desktop instance or any compatible client by configuring an MCP server with the provided settings. You can then ask for sprint progress, fetch issue details, create multiple items in a batch, search with SQL-like queries, and manage comments or attachments. The tooling is designed to handle errors gracefully, reporting per-item outcomes in batch operations so failures don’t derail the entire request.

Prerequisites:

• Node.js v14 or higher
• npm (comes with Node.js)
• A Taiga account with API access

Option 1: NPX (Recommended)

• No installation required; runs the latest version directly:

# NPM Registry (official)
npx taiga-mcp-server

# GitHub Package Registry (alternative)
npx @greddy7574/taiga-mcp-server

Option 2: Global Installation

# From NPM Registry
npm install -g taiga-mcp-server
taiga-mcp

# From GitHub Packages
npm install -g @greddy7574/taiga-mcp-server

Option 3: Docker Deployment

# Build the image
docker build -t taiga-mcp-server .

# Run with environment file
docker run --rm -i --env-file .env taiga-mcp-server

# Or with environment variables
docker run --rm -i \
  -e TAIGA_API_URL=https://api.taiga.io/api/v1 \
  -e TAIGA_USERNAME=your_username \
  -e TAIGA_PASSWORD=your_password \
  taiga-mcp-server

# Using docker-compose
docker-compose up --build

Tips and common considerations:

• The MCP server expects Taiga API credentials; store them securely (e.g., environment variables, secret management).
• When using batch operations, the server returns per-item results so you can identify successes and failures individually.
• For self-hosted Taiga instances, update TAIGA_API_URL in your environment config to point to your instance's API.
• If you’re integrating with Claude Desktop, add the server configuration to your config.json under mcpServers, matching the example command/args settings.
• Docker deployments can leverage .env files for sensitive values; avoid committing secrets to version control.