K
kiet0807/taiga-mcp
A Model Context Protocol server for Taiga.
★ 1·updated 2026-11-18
View on GitHub ↗Direct link · no redirect page
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 1 ★ · kiet0807/taiga-mcp · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 1 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
kiet0807/taiga-mcp;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# taiga-mcp
Excerpted from the repository README (abridged)
A Model Context Protocol server for Taiga. It lets an AI assistant such as Claude, ChatGPT, Copilot or Cursor answer questions about your Taiga projects without you opening Taiga: sprints, user stories, tasks, issues, epics and the wiki. It reads by default; if you switch it on, it can also create items, change them and comment. It can never delete anything.
## Try it in 30 seconds
Nothing to install. In Claude, open Settings → Connectors → Add custom connector and paste:
text
https://taiga.kietnguyen.io.vn/mcp
Sign in with your own Taiga account, on Taiga cloud or any Taiga reachable from the internet, then ask:
"What is left in the current sprint?"
"What does #123 say, and who has it?"
"Read the spreadsheet attached to #456 and list the rows marked urgent."
Other apps (ChatGPT, Claude Code, Cursor, VS Code, Gemini CLI, Codex, Windsurf): see Connecting an app. Your password is passed to Taiga once and never stored (how signing in works); if you would rather nobody else's server saw it, run it on your machine or host your own.
## Why this one
Reads what is attached. PDFs, Word, Excel, PowerPoint, CSV and pictures attached to an item, in parts when they are large.
Nothing to install for a team. One address, and each person signs in with their own Taiga account (OAuth). No keys to hand around, no database.
Writes only when allowed, never deletes. Creating, changing and commenting are off until switched on, refuse to overwrite someone else's change, and show every field before and after.
Sprints the way a team talks about them. Points done, stories done, burndown day by day, and what happened this week, by person.
Names, not ids. Statuses, people, sprints and tags by name (no accents needed), items by #123; errors say what to try next.
Any Taiga. Taiga cloud or self-hosted (for a Taiga inside a company network, host your own); sign-in pages in English and Vietnamese.
How it works inside, flow by flow, with links into the code: docs/how-it-works.md.
It runs in two ways:
On your machine (stdio), for one person, with the Taiga account in its settings. See Setup.
Hosted (HTTP), for a team, including people who never open a terminal: they paste one address into their AI assistant and sign in with their own Taiga account. See Hosted server.
Status: fourteen tools that read and three that write (off unless switched on), covered by tests against a fake Taiga; the reading tools are also checked against a public project on Taiga cloud. A hosted instance runs at taiga.kietnguyen.io.vn.
## Tools
| Tool | What it answers |
| list_projects | The projects you are a member of, with their slugs |
| get_project | One project: members and roles, statuses (and which count as closed), issue types, severities, priorities, tags, fields |
| list_sprints | Sprints with dates, stories done, points done, and which one runs today |
| get_sprint | One sprint: stories, tasks and points done, and the burndown day by day up to today |
| list_user_stories | Stories with status, assignee, points and sprint |
| list_tasks | Tasks with status, assignee, and the story and sprint they belong to |
| list_issues | Issues with type, status, severity, priority and assignee |
## Try it in 30 seconds
Nothing to install. In Claude, open Settings → Connectors → Add custom connector and paste:
text
https://taiga.kietnguyen.io.vn/mcp
Sign in with your own Taiga account, on Taiga cloud or any Taiga reachable from the internet, then ask:
"What is left in the current sprint?"
"What does #123 say, and who has it?"
"Read the spreadsheet attached to #456 and list the rows marked urgent."
Other apps (ChatGPT, Claude Code, Cursor, VS Code, Gemini CLI, Codex, Windsurf): see Connecting an app. Your password is passed to Taiga once and never stored (how signing in works); if you would rather nobody else's server saw it, run it on your machine or host your own.
## Why this one
Reads what is attached. PDFs, Word, Excel, PowerPoint, CSV and pictures attached to an item, in parts when they are large.
Nothing to install for a team. One address, and each person signs in with their own Taiga account (OAuth). No keys to hand around, no database.
Writes only when allowed, never deletes. Creating, changing and commenting are off until switched on, refuse to overwrite someone else's change, and show every field before and after.
Sprints the way a team talks about them. Points done, stories done, burndown day by day, and what happened this week, by person.
Names, not ids. Statuses, people, sprints and tags by name (no accents needed), items by #123; errors say what to try next.
Any Taiga. Taiga cloud or self-hosted (for a Taiga inside a company network, host your own); sign-in pages in English and Vietnamese.
How it works inside, flow by flow, with links into the code: docs/how-it-works.md.
It runs in two ways:
On your machine (stdio), for one person, with the Taiga account in its settings. See Setup.
Hosted (HTTP), for a team, including people who never open a terminal: they paste one address into their AI assistant and sign in with their own Taiga account. See Hosted server.
Status: fourteen tools that read and three that write (off unless switched on), covered by tests against a fake Taiga; the reading tools are also checked against a public project on Taiga cloud. A hosted instance runs at taiga.kietnguyen.io.vn.
## Tools
| Tool | What it answers |
| list_projects | The projects you are a member of, with their slugs |
| get_project | One project: members and roles, statuses (and which count as closed), issue types, severities, priorities, tags, fields |
| list_sprints | Sprints with dates, stories done, points done, and which one runs today |
| get_sprint | One sprint: stories, tasks and points done, and the burndown day by day up to today |
| list_user_stories | Stories with status, assignee, points and sprint |
| list_tasks | Tasks with status, assignee, and the story and sprint they belong to |
| list_issues | Issues with type, status, severity, priority and assignee |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/kiet0807-taiga-mcp/)
- Source
- awesome · https://github.com/kiet0807/taiga-mcp
- Browse by field
- MCP servers
- Traction
- 1 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.