Taiga integration
Taiga is an open-source agile project management platform, self-hosted or on taiga.io. This integration covers its REST API v1: exchange a username and password for a bearer token, then read projects and sprints and manage the backlog through user stories, tasks and issues. The instance host and the token both come from the connected credential.
Say what should happen.
The workflow builds itself.
Common Taiga use cases
- reporting on open bugs by severity
- resolving a project id from its name
- checking a stored token is still valid
- listing the remaining tasks of a story
- closing an issue when the fix is deployed
- moving a story to Done when work finishes
- moving a task to Done when a build passes
- obtaining a token before the first Taiga call
- removing a story created in the wrong project
- breaking a story down into tasks automatically
What you can do with Taiga
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
User story, 5 operations
create_user_storyCreate user storyPOSTCreates a Taiga user story in a project, optionally planned into a sprint.delete_user_storyDelete user storyDELETEDeletes a Taiga user story permanently.get_user_storyGet user storyGETRetrieves a single Taiga user story by identifier.list_user_storiesList user storiesGETLists Taiga user stories with filtering on project, sprint, status and assignee.update_user_storyUpdate user storyPATCHUpdates a Taiga user story, changing its status, assignee or sprint.
Issue, 4 operations
create_issueCreate issuePOSTCreates a Taiga issue with a type, severity and priority.get_issueGet issueGETRetrieves a single Taiga issue by identifier.list_issuesList issuesGETLists Taiga issues with filtering on project, status, type and severity.update_issueUpdate issuePATCHUpdates a Taiga issue.
Task, 4 operations
create_taskCreate taskPOSTCreates a Taiga task in a project, optionally under a user story.get_taskGet taskGETRetrieves a single Taiga task by identifier.list_tasksList tasksGETLists Taiga tasks with filtering on project, story, sprint and assignee.update_taskUpdate taskPATCHUpdates a Taiga task.
Project, 2 operations
get_projectGet projectGETRetrieves a single Taiga project with the status lists its items use.list_projectsList projectsGETLists the Taiga projects visible to the token.
Milestone, 1 operation
list_milestonesList milestonesGETLists Taiga sprints with their dates, points and closed state.
Session, 1 operation
auth_loginAuth loginPOSTLogs in to a Taiga instance and returns the bearer token to use afterwards.
User, 1 operation
get_meGet meGETRetrieves the authenticated Taiga user.
Use Taiga from Claude Code, Cursor or Codex
Connect Taiga in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Taiga operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect Taiga
- Create your workspace
Sign up free. Nothing to install.
- Connect Taiga once
Add your Taiga connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
Taiga integration FAQ
What can you do with the Taiga integration?
LiveContext exposes 18 operations on Taiga, covering user story, issue, task and project. Common uses include reporting on open bugs by severity, resolving a project id from its name and checking a stored token is still valid.
