Taiga MCP Server

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/xhisusx-taiga-mcp-server

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

8 read · 5 write · 1 delete

Secrets

2 (API keys, tokens or passwords)

Install scripts

Not scanned yet

Runs as

Node.js package

Tools (14)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• taiga_add_commentTaiga: comment on an item

  Post a comment on one work item. Use taiga_update_item when you also want to change fields in the same action.

• taiga_create_itemTaiga: create work item

  Create a user story, task, issue or epic. Status, assignee and sprint may be passed by name. Taiga applies the project's default status when none is given. Fields that do not exist for a kind are rejected (epics have no sprint or due date; only user stories carry points; only tasks have a parent user story; type / severity / priority are issue-only).

• taiga_create_sprintTaiga: create sprint

  Create a sprint (Taiga calls it a milestone) in a project. Afterwards its name can be used as the sprint of any user story, task or issue.

• taiga_delete_itemTaiga: delete work itemcan change or delete data

  Permanently delete one user story, task, issue or epic. There is no undo in Taiga — prefer moving the item to a closed status instead. Requires confirm: true.

• taiga_get_itemTaiga: get work itemread-only

  Full detail of one work item, including description, points, blocked state and a link to the UI. Identify it either by global "id", or by "ref" (the #number in the UI) together with "project".

• taiga_link_epicTaiga: link story to epic

  Attach a user story to an epic, or detach it again.

• taiga_list_commentsTaiga: item history and commentsread-only

  Comments on one work item, oldest first. With include_changes it also reports field changes ("status: New → In progress"), which is how you reconstruct what happened to an item.

• taiga_list_itemsTaiga: list work itemsread-only

  List user stories, tasks, issues or epics in a project. Statuses, assignees and sprints can be given by name — they are resolved against the project's catalogs. Closed items are excluded unless include_closed is true.

• taiga_list_projectsTaiga: list my projectsread-only

  Projects this account is a member of, with their slug, id and enabled modules (backlog, kanban, issues, epics, wiki).

• taiga_my_workTaiga: my assigned workread-only

  Work items assigned to the authenticated user, grouped by kind and ordered by due date. Open items only, unless include_closed is true. This is the "what am I supposed to be doing" tool.

• taiga_project_schemaTaiga: project schemaread-only

  Everything that is configured per project and needed to write to it: status names for each item kind, members and their roles, sprints, issue types / severities / priorities, the story-point scale, tags, and your own permissions. Call this before the first create or update in a project — statuses are NOT shared between projects. Cached, so repeated calls are cheap.

• taiga_searchTaiga: search a projectread-only

  Full-text search inside one project across user stories, tasks, issues and epics. Use it when the user names an item by words rather than by number.

• taiga_update_itemTaiga: update work item

  Change one work item: move it to another status, (re)assign it, put it in a sprint, edit subject or description, manage tags, set a due date, block it, estimate it — and optionally leave a comment in the same call. Pass only the fields you want to change. The item's version is sent along, so a concurrent edit by someone else is rejected instead of silently overwritten. Returns what actually changed.

• taiga_whoamiTaiga: who am Iread-only

  The Taiga account this server is authenticated as, plus the server's own limits (read-only mode, whether deletes are allowed). Call it once to learn which username "me" means.

Signals

Stars

0

Forks

0

Open issues

0

Last commit

Oct 21, 2026 (9 days ago)

Last release

Oct 21, 2026 (9 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

io.github.xHisusx/taiga-mcp-server

Version

0.1.1

Auth

API key

Packages

npm taiga-api-mcp-server

License

MIT

Repository

github.com/xHisusx/taiga-api-client

Website

github.com/xHisusx/taiga-api-client/tree/main/mcp#readme

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql