
Taiga MCP Server: Setup for Claude, Cursor and Other Apps
@taiga-ai/mcp-serverLets Claude, Cursor and other assistants read your Taiga products, policies and findings and move work through the line.
This is Taiga's own server. It lets your assistant read where a product stands, queue and review initiatives, follow coding runs and manage findings, documents and setup. It needs a Taiga account and an access key.
It runs on your computer and calls the Taiga API with that key. You create the key in Taiga under Settings, Account, MCP, and pick its permissions and expiry there. The key acts as you and can do no more than your role allows. The package is proprietary and is not open source.
Good for
- Engineers who use Taiga to plan and ship work with coding agents
- Team leads who review plans, pull requests and what waits on people
- Security and compliance owners who track findings, licenses and policies
- Platform admins who set up factories, products and repositories
Works in
12 should work
Tap an app to see how to set it up and any known problems.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Client does not support this transport.
Client does not support this transport.
Install @taiga-ai/mcp-server
Claude Code
- 1
Copy this prompt.
Add the @taiga-ai/mcp-server server to Claude Code. Run this command: printf 'Taiga access key: ' && read -rs TAIGA_API_KEY && echo && claude mcp add taiga --scope user -e TAIGA_API_KEY="$TAIGA_API_KEY" -- npx -y @taiga-ai/mcp-server@0.36.0 Ask me for TAIGA_API_KEY and only put the values in that config, nowhere else. Then check that it loaded and tell me if I need to sign in or restart.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires Node.js, Taiga access key.
The README pins release 0.36.0 and prompts for the key so it stays out of your shell history. Create the key first under Settings, Account, MCP in Taiga.
From the project README. Source.
Tools
Shows where a product stands in one call
The first thing to read about a product: its status, what it needs next and what is in flight. Name the product by ID, slug or the git remote of your checkout.
Try: “Where does my current product stand?”
Network ·
taiga_get_product_contextShows who your key acts as and which tools it has
Reports your role, what the key can do, and which toolsets and tools are on or off.
Try: “Which Taiga tools can my key use?”
Network ·
taiga_whoamiLists what is waiting on a person
Shows reviews to make and setup only a person can do, with how long each has waited.
Try: “What is waiting on me in Taiga?”
Network ·
taiga_list_action_requiredLists setup you must do outside Taiga
Names the secrets, variables and accounts a product needs, where to create them and how urgent each is.
Try: “What setup does this product still need from me?”
Network ·
taiga_list_setup_tasksLists your organization's factories
Returns the groups that own products, with IDs, and can search by name.
Try: “List our Taiga factories.”
Network ·
taiga_list_factoriesLists your organization's products
Returns products with IDs, factory and status, and can search by name or slug.
Try: “List all products in the Payments factory.”
Network ·
taiga_list_productsReads a product's settings
Returns a product's kind, autonomy, what Taiga builds for it, network access and, during setup, what it still needs.
Try: “Show the settings of the checkout product.”
Network ·
taiga_get_productLists a product's initiatives
Shows units of work newest first, with board column, whose turn it is and a sentence on where each stands.
Try: “What initiatives are open on this product?”
Network ·
taiga_list_initiativesReads one initiative
Returns its column, turn, next step, latest run and description.
Try: “Show initiative 42 with its full description.”
Network ·
taiga_get_initiativeReads an initiative's plan step by step
Shows what each step builds, which files it reads and writes and what it depends on, enough to approve or reject it.
Try: “Show me the plan for initiative 42.”
Network ·
taiga_get_planLists coding agent runs
Shows runs newest first with one sentence on each: running, waiting to merge, merged, failed or stopped.
Try: “Which runs failed this week?”
Network ·
taiga_list_runsReads one coding agent run
Returns the outcome, pull request, security pass and each step with its commit and files, and why it failed if it did.
Try: “Why did run 17 fail?”
Network ·
taiga_get_runShows a product's work queue
Shows the queue the coding agent works through one initiative at a time and what it is waiting on.
Try: “What is in the line for this product?”
Network ·
taiga_get_lineReads one agent job
Returns the status, progress and outcome of an import, document or initiative request job.
Try: “How is job abc doing?”
Network ·
taiga_get_jobWaits for work to change instead of polling
Waits until an initiative, run or job reaches a state you name, such as plan ready, pull request open or done.
Try: “Wait until initiative 42 has a pull request.”
Network ·
taiga_waitReads a product's documents
Returns the plan documents (what to build) or the reality documents (what the code does).
Try: “Read the architecture document of this product.”
Network ·
taiga_get_product_documentReads organization policies and documents
Lists or opens the documents that apply to every product, such as policies, by section.
Try: “Show the security policy.”
Network ·
taiga_get_organization_documentReads a factory's instructions
Returns the domain, tech preferences and conventions the factory's products follow.
Try: “What are the instructions for the Payments factory?”
Network ·
taiga_get_factory_documentReads the organization's design tokens
Returns colors, spacing and type from the design standards, and whether text and tokens match.
Try: “What colors do our design tokens define?”
Network ·
taiga_get_design_tokensFollows a design token sync
Waits for a token sync job to finish and returns the result.
Try: “Is the token sync finished?”
Network ·
taiga_get_design_token_syncLists security and dependency problems
Returns vulnerable dependencies, secrets and insecure code found in a product, with urgency and location.
Try: “List critical findings on this product.”
Network ·
taiga_list_findingsReads one finding in detail
Shows how likely exploitation is, the advisory and fixed version, where it is, and any fix under way.
Try: “Explain finding 88.”
Network ·
taiga_get_findingShows how a product meets policies
Returns which controls are met, violated or not assessed, with the worst violations.
Try: “Does this product meet our policies?”
Network ·
taiga_get_policy_standingLists a product's packages
Shows each package with version, license and whether it is direct, dev only or pulled in by another.
Try: “Which packages does this product use?”
Network ·
taiga_list_packagesLists licenses in use
Shows the approved license list and every license used across products, with where each is used.
Try: “Which licenses are not approved yet?”
Network ·
taiga_list_licensesDownloads a repository's software bill of materials
Fetches a CycloneDX 1.6 bill of materials for one repository. It can be large.
Try: “Get the SBOM for the api repo.”
Network ·
taiga_get_sbomGets a repository's third-party notices
Returns the licenses and copyright holders of every package a repository ships, as attribution text.
Try: “Show third-party notices for the web repo.”
Network ·
taiga_get_noticesLists the reference files agents search
Shows knowledge files for the organization, a factory or a product, and whether each is processed.
Try: “What knowledge files does this product have?”
Network ·
taiga_list_knowledgeReads one knowledge file
Returns a Markdown or text file inline, or a download link for others.
Try: “Open the onboarding guide knowledge file.”
Network ·
taiga_get_knowledgeShows what is deployed where
Lists a product's environments and recent deployments with commit, pull request and status.
Try: “What is deployed to production?”
Network ·
taiga_get_deploymentsShows delivery performance
Returns deploy frequency, lead time, recovery time and failure rates over 30, 60 or 90 days.
Try: “How is our delivery performance over 90 days?”
Network ·
taiga_get_delivery_metricsShows environment health
Returns health, uptime and last check, with web vitals and error signals for one environment.
Try: “Is production healthy?”
Network ·
taiga_get_monitoringLists a product's linked repositories
Shows each linked repository with its working branch and whether it can build.
Try: “Which repos are linked to this product?”
Network ·
taiga_list_product_repositoriesLists branches of a linked repository
Returns branches so you can choose the one Taiga works on.
Try: “List branches of the api repo.”
Network ·
taiga_list_repository_branchesLists repositories you could link
Shows GitHub and GitLab repositories your organization's connections can reach.
Try: “Which repos can I link to this product?”
Network ·
taiga_list_linkable_repositoriesShows who gains or loses access to a move
Previews the access change if a product moves to another factory.
Try: “Who loses access if I move this product to Platform?”
Network ·
taiga_preview_product_moveTurns described work into initiatives
Asks an agent to write initiatives into the backlog from your description and returns a job. Ask first: the package marks this as paid agent work.
Try: “Add initiatives for a password reset flow.”
Write ·
taiga_request_initiativesStarts work on an initiative
Puts it on the product's line, where the agent plans, builds and opens a pull request. Ask first: the package marks this as paid agent work.
Try: “Queue initiative 42.”
Write ·
taiga_queue_initiativeApproves or rejects a plan
Approve starts the run that builds the plan. Reject sends it back with your comment for a new plan. Ask first: the package marks this as paid agent work.
Try: “Approve the plan for initiative 42.”
Write ·
taiga_review_planAsks for changes to a run
Tells Taiga what to change in a run still building or one whose pull request awaits review. Ask first: the package marks this as paid agent work.
Try: “Ask the run to add tests for the new endpoint.”
Write ·
taiga_request_changesCarries on a stopped or failed initiative
Plans a failed plan again, or resumes a stopped run from its first unfinished step. Ask first: the package marks this as paid agent work.
Try: “Resume initiative 42.”
Write ·
taiga_resume_initiativeReplaces an initiative's plan
Swaps the plan of an initiative in Build for a new one, and keeps the old plan. Ask first: the package marks this as paid agent work.
Try: “Plan initiative 42 again.”
Write ·
taiga_plan_againMoves an initiative on the board
Changes its column, takes it off the line or reorders it. Moving it out of Build stops its work, and some moves close its pull request. Ask first: the package marks this as paid agent work.
Try: “Move initiative 42 back to the backlog.”
Write ·
taiga_move_initiativeStops a run in an emergency
Halts a run whose initiative cannot be moved out of Build. The branch and any draft pull request stay. Ask first: the package marks this as paid agent work.
Try: “Stop run 17 now.”
Write ·
taiga_stop_runPauses or resumes a product's line
Pausing stops the plan and run in flight and starts nothing new. Ask first: the package marks this as paid agent work.
Try: “Pause the line for this product.”
Write ·
taiga_pause_lineSets whether plans build at once
Chooses for one initiative whether plans build immediately or wait for approval. Ask first: the package marks this as paid agent work.
Try: “Make initiative 42 wait for plan approval.”
Write ·
taiga_set_auto_buildSets whether a pull request merges itself
Chooses for one initiative whether its pull request merges after checks pass or waits for a person.
Try: “Do not auto-merge initiative 42.”
Write ·
taiga_set_auto_mergeSets a product's automation defaults
Changes whether plans build at once, whether pull requests merge themselves and how far Taiga goes on its own.
Try: “Turn off auto-merge for this product.”
Write ·
taiga_set_product_autonomyStarts a fix for a finding
Raises an initiative that fixes a finding and ends in a pull request. It merges on its own only where auto-merge allows. Ask first: the package marks this as paid agent work.
Try: “Fix finding 88.”
Write ·
taiga_fix_findingStarts a fix for policy violations
Raises an initiative that fixes the violations of one control or one violation. Ask first: the package marks this as paid agent work.
Try: “Fix the encryption policy violations.”
Write ·
taiga_fix_policy_violationBuilds open-source notices into a web app
Raises an initiative that makes each production build write license texts and notices for its bundled packages. Ask first: the package marks this as paid agent work.
Try: “Ship license notices for the web app.”
Write ·
taiga_ship_noticesIgnores or reopens a finding
Marks a finding ignored with a reason such as false positive or accepted risk, optionally with an expiry, or reopens it.
Try: “Ignore finding 88 as a false positive.”
Write ·
taiga_ignore_findingAllows a license in one product
Ignores every open finding of that license in a product, without approving it for the organization.
Try: “Allow the MPL license in this product.”
Write ·
taiga_allow_licenseApproves or removes a license organization-wide
Adds or removes a license on the approved list. It takes effect at once on every product.
Try: “Approve the Apache-2.0 license for the organization.”
Write ·
taiga_change_licenseMarks an Action Required item
Sets an item done, dismissed, in progress or snoozed for everybody. It does not approve or merge anything itself.
Try: “Mark the setup item for the Stripe key as done.”
Write ·
taiga_resolve_actionEdits one section of an organization document
Changes a section of the draft, such as a policy. People keep seeing the published version until it is published.
Try: “Update the access policy draft to require MFA.”
Write ·
taiga_update_organization_documentPublishes an organization document
Makes the draft the next version that every agent and person follows.
Try: “Publish the security policy draft.”
Write ·
taiga_publish_organization_documentEdits a factory's instructions draft
Changes the draft, while products follow the published version.
Try: “Add a testing convention to the factory instructions.”
Write ·
taiga_update_factory_documentPublishes a factory's instructions
Makes the draft the version the factory's products follow.
Try: “Publish the factory instructions.”
Write ·
taiga_publish_factory_documentEdits one section of a product document
Changes a section of the plan documents' draft. It is refused once setup is finished.
Try: “Edit the threat model section.”
Write ·
taiga_update_product_documentPublishes a product document
Publishes the draft and marks documents built from it outdated.
Try: “Publish the architecture draft.”
Write ·
taiga_publish_product_documentRecords that a person reviewed a document
Use only when the person says they read it.
Try: “I read the specification, mark it reviewed.”
Write ·
taiga_mark_product_document_reviewedRegenerates one product document
Rebuilds a document from those it depends on and returns a job. Ask first: the package marks this as paid agent work.
Try: “Regenerate the architecture document.”
Write ·
taiga_regenerate_product_documentGenerates all missing product documents
Creates every missing or outdated document in order and returns the jobs. Ask first: the package marks this as paid agent work.
Try: “Generate all missing documents.”
Write ·
taiga_generate_product_documentsStops document generation
Cancels documents in progress and keeps published ones. Ask first: the package marks this as paid agent work.
Try: “Stop generating documents.”
Write ·
taiga_stop_generating_documentsRe-reads the code into reality documents
Re-derives documents that describe what the code does, all or named ones, and returns a job. Ask first: the package marks this as paid agent work.
Try: “Refresh the reality documents.”
Write ·
taiga_refresh_reality_documentsChanges design tokens in the draft
Applies 1 to 50 token changes, all or nothing.
Try: “Change the primary color token to #0a5.”
Write ·
taiga_update_design_tokensRewrites tokens to match edited text
Has the design agent align the draft's tokens with its text and returns a job. Ask first: the package marks this as paid agent work.
Try: “Sync design tokens with the standards text.”
Write ·
taiga_sync_design_tokensAdds a knowledge document
Adds a Markdown or text file that agents search, for a product, factory or organization (owners and admins only). Ask first: the package marks this as paid agent work.
Try: “Add this runbook as product knowledge.”
Write ·
taiga_add_knowledgeRetries a failed knowledge file
Runs processing again for a file that failed. Ask first: the package marks this as paid agent work.
Try: “Retry the failed knowledge file.”
Write ·
taiga_retry_knowledgeDeletes a knowledge file
Removes a file and agents stop reading it at once. It cannot be undone.
Try: “Delete the outdated onboarding knowledge file.”
Delete ·
taiga_delete_knowledgeAdds an environment
Creates an environment a product runs in, tracked for deployments and monitoring.
Try: “Add a staging environment.”
Write ·
taiga_create_environmentEdits an environment
Renames it, changes its kind or sets the app URL Taiga monitors.
Try: “Set the staging app URL.”
Write ·
taiga_update_environmentLinks a repository to a product
Connects a GitHub repository or GitLab project and can replace an existing link.
Try: “Link the api repo to this product.”
Write ·
taiga_link_repositoryChooses the working branch
Sets the branch Taiga branches from and opens pull requests against.
Try: “Use the develop branch.”
Write ·
taiga_set_repository_branchUnlinks a repository from a product
Stops building and sweeping that repository. The repository itself is untouched.
Try: “Unlink the old repo.”
Write ·
taiga_unlink_repositoryCreates a factory
Makes a group of products that share members, knowledge and instructions. Owners and admins only.
Try: “Create a factory called Payments.”
Write ·
taiga_create_factoryRenames a factory
Changes the name, which also changes its slug and links.
Try: “Rename Payments to Billing.”
Write ·
taiga_rename_factoryCreates a product
Makes a product in a factory, from scratch or to import from code.
Try: “Create a product called Checkout in Payments.”
Write ·
taiga_create_productEdits a product
Changes name, what Taiga builds for it, or its allowed network connections.
Try: “Allow the product to reach api.example.com.”
Write ·
taiga_update_productMoves a product to another factory
Changes who can reach the product. It is refused while a plan or run is in flight.
Try: “Move Checkout to the Platform factory.”
Write ·
taiga_move_productImports a product from its code
Reads the linked repository, writes its documents, then sweeps and assesses it. It takes a while. Ask first: the package marks this as paid agent work.
Try: “Import this product from its repository.”
Write ·
taiga_start_importFinishes a product's setup
Locks its documents and starts planning the first initiatives. Ask first: the package marks this as paid agent work.
Try: “Finish setup for this product.”
Write ·
taiga_finish_discoveryReopens a finished product's setup
Lets documents be changed again, and setup must be finished again afterwards.
Try: “Reopen setup for this product.”
Write ·
taiga_reopen_discovery
Read from the source code
Permissions
high risk · 4 things to watch
High risk
The assistant can change Taiga settings, start coding agent work, approve plans and delete knowledge files with your permissions. Create a key with only the toolsets you need, and approve every write and every tool that starts agent work.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
It can delete knowledge files
The delete tool removes a reference file at once and cannot be undone. Organization files need an owner or admin key. npmjs.com
22 tools start or change paid agent work
The package marks these tools "Ask first (paid agent work)" in their descriptions: queue, plan review, resume, move, stop, pause, fixes, imports, document generation and knowledge processing. The README says each tool is one risk class, so allow reads and prompt on the rest. Keep your client's approval prompt on. npmjs.com
It can publish policies and change settings
Tools publish organization policies, switch on auto-merge and change repository links. Review each call before you accept it. npmjs.com
It trusts record text as data only
Initiative, finding and document text is written by people or agents. The server tells the assistant to treat it as data, but you should still read what comes back. npmjs.com
Security advisories
No published security advisories as of Nov 1, 2026.
Technical details
| Talks to | Taiga API (https://api.eu.tai.ga by default) |
|---|---|
| Sign-in and keys | The key is passed to the server in the TAIGA_API_KEY environment variable and shown once in Taiga when you create it. |
| Scopes |
|
Questions
Is the Taiga MCP server official?
Yes. It is Taiga's own package, and its README calls it the Taiga MCP server.
How do I get the access key?
Sign in to Taiga and open Settings, Account, MCP. Create a key, choose its permissions and expiry, and copy it, because Taiga shows it once.
Is it free and open source?
The package is proprietary and is provided for use with a Taiga account. It is not open source, and it does nothing without an account and key.
Can I limit what it can do?
Yes, in part. The tools come in five toolsets that you choose when you create the key, or override with the TAIGA_TOOLSETS setting. There is no read-only switch, and the core set also holds design token tools.
Why do I see fewer tools than this page lists?
The server registers only the tools your key and role can use. A key with fewer toolsets or a lower role shows fewer.
What can it not do?
Organization administration stays in the web app: members and roles, SSO, access keys, connecting GitHub, and deleting factories and products.
Does it run on my computer or in the cloud?
The server runs on your computer. It sends requests to the Taiga API, which is hosted in the EU by default.
How do I add it to Claude Code?
Use the Claude Code tab in the install box above, and paste your access key where it shows the placeholder. Taiga also offers a ready-made command that asks for the key without saving it in your shell history.
Information
updated Nov 2, 2026
- Publisher
- Official
- Package
@taiga-ai/mcp-server- Registry
- npm
- Transport
- stdio
- Auth
- token in env
- Version
- 0.36.0
- License
- Proprietary
Sources
Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.
Show all 2Hide
- www.npmjs.com · npmjs.com
- docs.tai.ga · docs.tai.ga