@autodevjapan/godd-mcp-alpha 1.40.0 → 1.41.0

package/README.md

@@ -55,7 +55,18 @@ If `godd-a install` is unavailable, you can edit `~/.cursor/mcp.json` directly.
 
 ### Claude Code CLI Setup
 
-`godd-a install` currently targets Cursor only (`~/.cursor/mcp.json`). For Claude Code CLI, register the server manually. The startup command, args, and env are identical to Cursor.
+Register the server into Claude Code CLI with the `--client=claude-code` flag:
+
+```bash
+godd-a install --client=claude-code --license-key=YOUR_LICENSE_KEY
+```
+
+This delegates registration to `claude mcp add-json` at **user scope** (`~/.claude.json`), so it merges safely alongside your other MCP servers and is re-runnable (an existing entry is refreshed). When the `claude` CLI is not on your PATH, the installer prints the exact command to run by hand instead.
+
+Without `--client`, `godd-a install` targets Cursor (`~/.cursor/mcp.json`) as before. The startup command, args, and env are identical across clients, and the license device binding is per-device — the same key works across Cursor and Claude Code CLI on the same machine.
+
+<details>
+<summary>Manual registration (if you prefer not to use <code>godd-a install</code>)</summary>
 
 ```bash
 claude mcp add godd-a \
@@ -63,7 +74,8 @@ claude mcp add godd-a \
   -- npx -y @autodevjapan/godd-mcp-alpha@latest serve
 ```
 
-Or add a project-root `.mcp.json` with the same `mcpServers` structure shown above (the `serve` argument is required). The license device binding is per-device, so the same key works across Cursor and Claude Code CLI on the same machine.
+Or add a project-root `.mcp.json` with the same `mcpServers` structure shown above (the `serve` argument is required).
+</details>
 
 ### Usage