Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Taiga is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Sprints, stories, tasks, issues, epics, wiki and attached files in Taiga; writes only when allowed.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'TAIGA_URL=${TAIGA_URL}' --transport stdio kiet0807-taiga-mcp '--' npx -y @kietdev/taiga-mcp
# 2 — ask your agent for something these tools do
# add_comment, create_item, get_attachment and 14 more
It needs TAIGA_URL: this reads it from your environment, so export it first. Remote: OAuth sign-in · Package: API key.
Taiga costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads TAIGA_URL (Address of the Taiga API host, e.g. https://api.taiga.io) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx TAIGA_URL … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'TAIGA_URL=${TAIGA_URL}' --transport stdio kiet0807-taiga-mcp '--' npx -y @kietdev/taiga-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Its publisher also runs it at https://taiga.kietnguyen.io.vn/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http kiet0807-taiga-mcp https://taiga.kietnguyen.io.vn/mcpIt reaches a system of yours, so it needs settings only you can give it: TAIGA_URL — Address of the Taiga API host, e.g. https://api.taiga.io. You set it in your own client’s config, on your machine — this marketplace never holds it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Post a comment on one user story, issue, epic or task of a Taiga project, by its reference
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | yes | — | |
| ref | yes | — | |
| text | string | yes | The comment exactly as it should appear in Taiga. Markdown works. |
Create a user story, a task or an issue in a Taiga project, as the signed-in user.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | yes | — | |
| kind | string | yes | — |
| subject | yes | Title of the new item, short and specific. | |
| description | string | no | Longer text for the item. Markdown works. |
| status | yes | — | |
| assigned_to | yes | — | |
| tags | yes | — | |
| sprint | yes | — | |
| story | integer | no | For a task: reference number of the user story it belongs to. |
| epic | integer | no | For a user story: reference number of an epic to add it to. |
| due_date | string | no | Due date as YYYY-MM-DD. |
| type | yes | — | |
| severity | yes | — | |
| priority | yes | — |
Read a file attached to a story, task, issue or epic. Images (screenshots, mock-ups, photos) come
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | yes | — | |
| ref | integer | yes | Reference number of the item the file is attached to. |
| file | yes | — | |
| sheet | string | no | Spreadsheets and CSV: the sheet to read, by name or number. |
| rows | string | no | — |
| pages | string | no | PDFs and presentations: pages or slides, e.g. "3-5". |
| find | string | no | — |
Read one user story, issue, epic or task of a Taiga project in full, by its reference number (the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | yes | — | |
| ref | integer | yes | Reference number without the #, e.g. 123. |
| comments | integer | no | — |
| changes_page | integer | no | — |
| changes | boolean | no | — |
Read what a Taiga project is made of: its description, its members with their roles, how many
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | yes | — |
Read one sprint of a Taiga project in full: dates, how many stories, tasks and points are done,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | yes | — | |
| sprint | string | no | — |
What happened in a Taiga project, newest first: who created, changed, commented on or deleted
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | yes | — | |
| by_me | boolean | no | true: only what the signed-in user did. |
| by | string | no | — |
| from | yes | — | |
| to | yes | — | |
| kind | string | no | Only activity on this kind of thing. "epic" includes linking stories to epics. |
| ref | integer | no | Only activity on this item (and, for a story, on its tasks), by reference number. |
| comments_only | boolean | no | true: only events with a comment. |
| limit | integer | no | Most events to return (default …, at most …). |
| page | integer | no | Which part of the matches, from 1, with the same limit and filters. |
List, search or count the epics of a Taiga project in board order: reference number, title, status,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | yes | — | |
| status | yes | — | |
| closed | yes | — | |
| assigned_to_me | yes | — | |
| assigned_to | yes | — | |
| tag | yes | — | |
| created_from | yes | — | |
| created_to | yes | — | |
| search | yes | — | |
| limit | yes | — | |
| page | yes | — |
List, search or count issues (bugs, questions, enhancement requests) of a Taiga project, most
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | yes | — | |
| type | yes | — | |
| status | yes | — | |
| closed | yes | — | |
| severity | yes | — | |
| priority | yes | — | |
| assigned_to_me | yes | — | |
| assigned_to | yes | — | |
| tag | yes | — | |
| created_from | yes | — | |
| created_to | yes | — | |
| finished_from | yes | — | |
| finished_to | yes | — | |
| search | yes | — | |
| limit | yes | — | |
| page | yes | — |
List the Taiga projects the signed-in user is a member of, with the name and slug of each.
No parameter schema on file.
List the sprints of a Taiga project (Taiga also calls them milestones), newest first: name, dates,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | yes | — | |
| closed | boolean | no | true: list finished sprints instead of open ones. Default false. |
| limit | yes | — | |
| page | yes | — |
List, search or count tasks of a Taiga project: the small pieces of work a user story is split
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | yes | — | |
| story | integer | no | Reference number of a user story, without the #: only the tasks of that story. |
| sprint | string | no | A sprint name from list_sprints, or "current" for the sprint running today. |
| status | yes | — | |
| closed | yes | — | |
| assigned_to_me | yes | — | |
| assigned_to | yes | — | |
| tag | yes | — | |
| created_from | yes | — | |
| created_to | yes | — | |
| finished_from | yes | — | |
| finished_to | yes | — | |
| search | yes | — | |
| limit | yes | — | |
| page | yes | — |
List, search or count user stories of a Taiga project in board order: reference number, title,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | yes | — | |
| sprint | string | no | — |
| epic | integer | no | Reference number of an epic from list_epics, without the #: only the stories under it. |
| status | yes | — | |
| closed | yes | — | |
| assigned_to_me | yes | — | |
| assigned_to | yes | — | |
| tag | yes | — | |
| created_from | yes | — | |
| created_to | yes | — | |
| finished_from | yes | — | |
| finished_to | yes | — | |
| search | yes | — | |
| limit | yes | — | |
| page | yes | — |
Search one Taiga project for words, in everything at once: user stories, tasks, issues, epics and
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | yes | — | |
| words | string | yes | The words to look for, e.g. "bank sandbox". |
| limit | integer | no | Most matches to show of each kind (default …, at most …). |
Change fields of one user story, issue, epic or task of a Taiga project, by its reference
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | yes | — | |
| ref | yes | — | |
| version | integer | no | — |
| subject | no | New title. | |
| description | string | no | — |
| status | yes | — | |
| assigned_to | yes | — | |
| sprint | yes | — | |
| add_tags | yes | — | |
| remove_tags | yes | — | |
| due_date | string | no | New due date as YYYY-MM-DD, or "none" to clear it. Not for epics. |
| blocked | boolean | no | true: mark the item blocked. false: no longer blocked. |
| blocked_note | string | no | Why it is blocked, shown in Taiga. |
| type | yes | — | |
| severity | yes | — | |
| priority | yes | — |
List the wiki pages of a Taiga project, most recently changed first: slug, title, when it last
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | yes | — | |
| limit | yes | — | |
| page | yes | — |
Read the text of one wiki page of a Taiga project, with who changed it last and when.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | yes | — | |
| page | string | yes | Slug of the page, e.g. "home", or its title in the wiki menu. |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Taiga or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (17 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| add_comment | no tags | |
| create_item | no tags | |
| get_attachment | no tags | |
| get_item | no tags | |
| get_project | no tags | |
| get_sprint | no tags | |
| list_activity | no tags | |
| list_epics | no tags | |
| list_issues | no tags | |
| list_projects | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_sprints | no tags | |
| list_tasks | no tags | |
| list_user_stories | no tags | |
| search | no tags | |
| update_item | no tags | |
| list_wiki_pages | no tags | |
| get_wiki_page | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.4.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Taiga can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.