@taiga-ai/mcp-server 0.36.0 → 0.37.0-dev.1001

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 +8 -8
  2. package/dist/index.js +7088 -835
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -14,7 +14,7 @@ You need an access key, made in Taiga under **Settings > Account > MCP**, where
14
14
 
15
15
  Create the key first, and choose when it expires: in 30 days, 90 days, a year, or never. Taiga copies it to your clipboard, shows it once, and keeps it on the page until you say you have saved it, so copying the setup next does not lose it.
16
16
 
17
- The same page shows the setup for your client and environment, with the key already filled in where a config file needs it, and a one-click install for Cursor. The examples here pin a release (`@taiga-ai/mcp-server@0.36.0`), so an install runs the version you chose rather than whatever `latest` is at the next start.
17
+ The same page shows the setup for your client and environment, with the key already filled in where a config file needs it, and a one-click install for Cursor. The examples here pin a release (`@taiga-ai/mcp-server@0.37.0`), so an install runs the version you chose rather than whatever `latest` is at the next start.
18
18
 
19
19
  ## Install
20
20
 
@@ -23,21 +23,21 @@ The same page shows the setup for your client and environment, with the key alre
23
23
  Run the command. When it asks for your access key, paste it once and press Enter. Nothing appears as you paste (PowerShell shows asterisks), and the key stays out of your shell history:
24
24
 
25
25
  ```sh
26
- 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
26
+ 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.37.0
27
27
  ```
28
28
 
29
29
  ```sh
30
- printf 'Taiga access key: ' && read -rs TAIGA_API_KEY && echo && codex mcp add taiga --env TAIGA_API_KEY="$TAIGA_API_KEY" -- npx -y @taiga-ai/mcp-server@0.36.0
30
+ printf 'Taiga access key: ' && read -rs TAIGA_API_KEY && echo && codex mcp add taiga --env TAIGA_API_KEY="$TAIGA_API_KEY" -- npx -y @taiga-ai/mcp-server@0.37.0
31
31
  ```
32
32
 
33
33
  On Windows, in PowerShell (Claude Code needs `cmd /c` to start `npx`; the quoted `'--'` survives npm's PowerShell shims):
34
34
 
35
35
  ```powershell
36
- $k = Read-Host 'Taiga access key' -AsSecureString; claude mcp add taiga --scope user -e "TAIGA_API_KEY=$([Net.NetworkCredential]::new('', $k).Password)" '--' cmd /c npx -y @taiga-ai/mcp-server@0.36.0
36
+ $k = Read-Host 'Taiga access key' -AsSecureString; claude mcp add taiga --scope user -e "TAIGA_API_KEY=$([Net.NetworkCredential]::new('', $k).Password)" '--' cmd /c npx -y @taiga-ai/mcp-server@0.37.0
37
37
  ```
38
38
 
39
39
  ```powershell
40
- $k = Read-Host 'Taiga access key' -AsSecureString; codex mcp add taiga --env "TAIGA_API_KEY=$([Net.NetworkCredential]::new('', $k).Password)" '--' npx -y @taiga-ai/mcp-server@0.36.0
40
+ $k = Read-Host 'Taiga access key' -AsSecureString; codex mcp add taiga --env "TAIGA_API_KEY=$([Net.NetworkCredential]::new('', $k).Password)" '--' npx -y @taiga-ai/mcp-server@0.37.0
41
41
  ```
42
42
 
43
43
  ### Cursor, Windsurf, Claude Desktop and other MCP clients
@@ -49,7 +49,7 @@ Most clients read the same `mcpServers` block. Add it with your key in place of
49
49
  "mcpServers": {
50
50
  "taiga": {
51
51
  "command": "npx",
52
- "args": ["-y", "@taiga-ai/mcp-server@0.36.0"],
52
+ "args": ["-y", "@taiga-ai/mcp-server@0.37.0"],
53
53
  "env": { "TAIGA_API_KEY": "YOUR_ACCESS_KEY" }
54
54
  }
55
55
  }
@@ -78,7 +78,7 @@ In `.vscode/mcp.json`. VS Code reads `servers`, and prompts for the key once and
78
78
  "taiga": {
79
79
  "type": "stdio",
80
80
  "command": "npx",
81
- "args": ["-y", "@taiga-ai/mcp-server@0.36.0"],
81
+ "args": ["-y", "@taiga-ai/mcp-server@0.37.0"],
82
82
  "env": { "TAIGA_API_KEY": "${input:taiga-api-key}" }
83
83
  }
84
84
  }
@@ -127,7 +127,7 @@ This is what a security reviewer should know.
127
127
  - **Version check.** The server checks at start that the Taiga API it reached supports this version, and refuses to start if not, saying why.
128
128
  - **Nothing on stdout but the protocol.** The server writes only protocol messages to stdout. Its log goes to stderr and does not include your email.
129
129
 
130
- Organization administration stays in the web. That covers members and roles, SSO, access keys, connecting GitHub, the Discovery conversation, and deleting factories and products.
130
+ Organization administration stays in the web. That covers members and roles, SSO, access keys, connecting GitHub, GitLab or Azure DevOps, the Discovery conversation, and deleting factories and products.
131
131
 
132
132
  ## Troubleshooting
133
133