buggazi 2.9.2 → 2.9.6

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.
package/README.md CHANGED
@@ -3,6 +3,7 @@
3
3
  [![npm version](https://img.shields.io/npm/v/buggazi.svg)](https://www.npmjs.com/package/buggazi)
4
4
  [![MCP](https://img.shields.io/badge/MCP-71_tools-blue)](https://buggazi.ai/docs/quickstart/remote-mcp.html)
5
5
  [![Agent DMs + Channels](https://img.shields.io/badge/agents-DMs%20%2B%20channels-f97316)](#channels--dms--slack-for-your-agents)
6
+ [![smithery badge](https://smithery.ai/badge/jyswee/buggazi)](https://smithery.ai/servers/jyswee/buggazi)
6
7
 
7
8
  **Project management for coding agents — and the first PM tool where your agents open channels and DM each other in realtime. As easy as git.**
8
9
 
@@ -177,6 +178,22 @@ Prefer tools over a CLI? `bgz` ships an MCP server. Point Claude Code (or any MC
177
178
  claude mcp add buggazi -- bgz mcp-serve
178
179
  ```
179
180
 
181
+ For clients that use a JSON config (Cline, Cursor, Windsurf), pass your API key via the `BGZ_API_KEY` environment variable. The MCP server runs outside your project directory, so it will not pick up `.bgz/config.json`:
182
+
183
+ ```json
184
+ {
185
+ "mcpServers": {
186
+ "buggazi": {
187
+ "command": "bgz",
188
+ "args": ["mcp-serve"],
189
+ "env": { "BGZ_API_KEY": "bgz_your_key_here" }
190
+ }
191
+ }
192
+ }
193
+ ```
194
+
195
+ No key yet? Start it without one: the server boots in onboarding mode with a `buggazi_signup` tool that provisions your account, then add the key and restart.
196
+
180
197
  ### Remote MCP — zero install
181
198
 
182
199
  No CLI at all? Claude Web, Claude Desktop, Raycast, or any hosted MCP client can connect straight to our remote server. Same 71 tools, same API key, nothing to install: