@taiga-ai/mcp-server 0.26.0-dev.528 → 0.26.0-dev.529

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +19 -4
  2. package/dist/index.js +2913 -2700
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -76,10 +76,25 @@ env = { TAIGA_API_KEY = "your-key-here" }
76
76
 
77
77
  ## Configuration
78
78
 
79
- | Variable | Required | Meaning |
80
- | --------------- | -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
81
- | `TAIGA_API_KEY` | Yes | Your API key. |
82
- | `TAIGA_API_URL` | For `@dev` and `@staging` builds | The Taiga API. A release defaults to `https://api.eu.tai.ga`. It must be https (plain http only for `localhost`), with no query or fragment. |
79
+ | Variable | Required | Meaning |
80
+ | ---------------- | -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
81
+ | `TAIGA_API_KEY` | Yes | Your API key. |
82
+ | `TAIGA_API_URL` | For `@dev` and `@staging` builds | The Taiga API. A release defaults to `https://api.eu.tai.ga`. It must be https (plain http only for `localhost`), with no query or fragment. |
83
+ | `TAIGA_TOOLSETS` | No | Toolsets to turn on besides the default, comma-separated, or `all`. See [Toolsets](#toolsets). |
84
+
85
+ ## Toolsets
86
+
87
+ The tools come in five toolsets, so an assistant sees the ones for the job rather than all of them.
88
+
89
+ | Toolset | For |
90
+ | ----------- | ---------------------------------------------------------------------------- |
91
+ | `core` | Reading where products, initiatives, runs, policies and findings stand. |
92
+ | `operate` | Moving work: queueing, approving plans, stopping runs, fixing findings. |
93
+ | `setup` | Creating factories and products, linking repositories, imports, autonomy. |
94
+ | `observe` | Deployments, monitoring, delivery metrics, packages and the SBOM. |
95
+ | `documents` | Factory documents, writing and publishing documents, and the knowledge base. |
96
+
97
+ A key with the viewer role gets every toolset, which for it holds only reads. Every other role gets `core` and `operate`. Set `TAIGA_TOOLSETS` to turn on more, for example `setup` or `setup,observe`, or `all`, then restart the server; it adds to the default, never takes from it. A toolset never adds a tool your key does not allow. `taiga_whoami` lists the toolsets that are on and the tools in the ones that are off.
83
98
 
84
99
  ## First steps
85
100