
Taiga Mcp Server
io.github.xHisusx由 GitHub 账号 xHisusx 发布v0.5.0更新于 Oct 29, 2026
Read and manage your own Taiga projects: items, statuses, assignees, sprints, comments
概览
把助手连接到 Taiga 项目跟踪系统的 MCP 服务器,可读取和管理用户故事、任务、问题、史诗、迭代与评论。
- 可以做什么
- 读取和管理项目条目:用户故事、任务、问题与史诗,包括创建、编辑、指派和估点
- 在状态之间移动条目、规划迭代并添加评论,状态、成员和迭代按名称指定
- 用时间线工具汇总某段时间的工作,按卡片返回状态变更、关闭、评论、迭代移动和附件
- 可选删除条目,仅在显式开启删除时才可用
- 适用场景
- 适合团队用 Taiga 跟踪工作、希望助手回答“分配给我什么”或“某段时间发生了什么”,并在对话中直接创建和更新故事、任务与问题的场景。
- 运行要求
- 以 stdio 方式在本机运行,通常通过 npx 启动,需要 Node.js 18 或更高版本。需要 TAIGA_URL(实例根地址,不含 /api/v1,例如 Taiga Cloud 的 API 主机),以及 TAIGA_APP_TOKEN,或 TAIGA_USERNAME 配 TAIGA_PASSWORD。可选:TAIGA_PROJECT 设置默认项目,TAIGA_MCP_READ_ONLY 与 TAIGA_MCP_ALLOW_DELETE 开关。需要能访问该 Taiga 实例的网络。
安装
在 SourceWeft 中
- 打开 控制台中的 Taiga Mcp Server,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
taiga-api-client
[npm version] [npm downloads] [bundle size] [types] [license] [CI] [GitHub stars]
🇬🇧 English version — you are here · 🇷🇺 Русская версия
A TypeScript client for the Taiga REST API. Zero runtime dependencies, dual ESM + CJS, runs on Node ≥18, Bun ≥1.0 and any environment with a global fetch.
- 🔐 Bearer authentication with automatic token refresh and deduplication of concurrent refreshes
- 📦 Fully typed: types for every resource, payload and parameter
- 🚫 Zero runtime dependencies
- 🔄 Async iterators for pagination
- ⚠️ Typed errors (
TaigaApiError,TaigaAuthError,TaigaRateLimitError,TaigaNetworkError) - 🚀 Dual ESM + CJS build with
.d.ts/.d.ctstype maps
Installation
Quick start
🤖 MCP server: Taiga for AI agents
This repository also ships taiga-api-mcp-server — a Model Context Protocol server built on this client. Point an MCP client (Claude Code, Claude Desktop, Cursor, …) at your Taiga account and it can read what is assigned to you, move items between statuses, create user stories, tasks, issues and epics, assign people, estimate, comment and plan sprints — with your own permissions and nothing more.
Statuses, members and sprints are addressed by name; the server resolves them against the project's own catalogs, so an agent never has to guess a numeric ID.
It also answers "what did we do last week" in one call: taiga_activity walks the project
timeline and returns, per card touched in the window, what actually happened to it — status
moves, closures (including the ones entered days later), comments, sprint moves, attachments.
Taiga's list endpoints have no date filters, so this is the only way to get a period of work.
Whether a story is finished comes from its tasks (tasks_done of tasks_total) and whether
it was closed from the project's own statuses — the dates and the closed flag are filled in by
hand, and often not at all. Both are answered twice over, as of today and as of the end of the
window, because a card moved to Done three days later is not last week's work.
📖 Setup, tool reference and examples: mcp/README.md
💡 Looking up catalog IDs? Use filters_data
Most write operations need numeric IDs of project-specific catalog values (status, type, severity, priority, assignee, …). Don't fetch each catalog separately — every resource exposes a filters_data method that returns all of them in one request, scoped to the project.
📖 Read the full guide: docs/filters-data.md — caching, available endpoints per resource, when it is not enough.
Creating the client
Minimum:
baseUrl is the only required option. Everything else is optional.
Full example:
TaigaClientOptions
Authentication
Three modes are supported:
Automatic token refresh
With autoRefresh: true (the default), the client transparently intercepts 401 responses, calls POST /auth/refresh, and retries the original request once. Concurrent 401s are deduplicated — /auth/refresh is called exactly once even if 10 requests fail simultaneously. If the refresh itself fails, tokens are cleared and a TaigaAuthError is thrown.
Persisting tokens across process restarts
onTokenChange is invoked:
- after
client.auth.login(...)— with the new token pair; - after a successful auto-refresh — with the new pair;
- after
client.auth.logout()— withnull.
The returned Promise is awaited before the request is retried, so your persistence is guaranteed to complete before the next request goes out.
Resources and methods
Every resource extends BaseResource, which provides standard CRUD. Specific resources add their own methods on top.
BaseResource<T> — common CRUD
client.auth — authentication
client.users — users
Base CRUD plus:
⚠️
users.create()intentionally throws — registration uses dedicated endpoints (out of scope in v0.1).
client.projects — projects
Base CRUD plus:
client.memberships — project memberships
Base CRUD plus:
client.userStories — user stories
Base CRUD plus:
client.tasks — tasks
Base CRUD plus:
client.issues — issues
Base CRUD plus:
client.epics — epics
Base CRUD plus:
ℹ️ Epics must be enabled on the project (
is_epics_activated: true) for these endpoints to work.
client.milestones — sprints
Base CRUD plus:
Pagination
list() always returns the first page of the response. There are three ways to iterate the full set:
⚠️
disablePaginationsends thex-disable-pagination: Trueheader. Use it only on small collections — for large ones Taiga may respond with an error or time out.
Errors
Every error inherits from the abstract TaigaError:
Optimistic Concurrency Control (OCC)
Taiga prevents lost updates between concurrent users via a version field. When calling patch(), pass the version you received with the object — if someone updated it first, Taiga responds with 400 / 412 and you learn about the conflict.
Low-level access
For endpoints that are not yet wrapped as resources, use client.http directly:
The available methods are get, post, put, patch, delete. They all accept the same RequestOptions: { query, body, headers, signal, disablePagination, skipAuth }.
Coverage
Implemented:
- Auth: login, refresh, logout, application token, session restore, auto-refresh with deduplication
- Users: profile, list, update, change password, stats
- Projects: CRUD, by_slug, stats, modules config
- Memberships: CRUD, bulk_create, resend invitation
- User Stories: CRUD, bulk_create, bulk_update_order for every board, filters_data
- Tasks: CRUD, bulk_create, filters_data
- Issues: CRUD, filters_data, voters, watchers, upvote/downvote, watch/unwatch
- Milestones: CRUD, stats
- Epics (new in v0.2): CRUD, bulk_create, filters_data, related_userstories (list/add/remove), voters, watchers, upvote/downvote, watch/unwatch
Not implemented yet (planned for upcoming releases): wiki, webhooks, attachments, custom attributes, history/comments, importers (Trello/Jira/GitHub), project templates, GitHub OAuth flow.
If the endpoint you need is not covered, fall back to client.http and/or open an issue.
Compatibility
License
来源:README.md,提交 8546124
工具
0版本历史
2- v0.5.0最新Oct 29, 2026
- v0.1.1Oct 21, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分