
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 分