@awesomate/hosting-mcp 0.7.0 → 0.7.2

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
@@ -14,14 +14,24 @@ which redeems a setup code for a scoped access token (stored at
14
14
  (Support Plus+), and registers this server. The **`awesomate-hosting` skill**
15
15
  (bundled under `skill/`) makes Claude plan-aware and enforces snapshot-before-change.
16
16
 
17
- Manual registration:
18
-
19
- ```bash
20
- claude mcp add awesomate-hosting --env AWESOMATE_PAT=amt_pat_... -- npx -y @awesomate/hosting-mcp
17
+ Manual registration — add to `~/.claude.json` under `mcpServers` (the
18
+ bootstrap does this automatically; never bake `AWESOMATE_PAT` into the env,
19
+ that pins the registration to one stale account forever):
20
+
21
+ ```json
22
+ "awesomate-hosting": {
23
+ "command": "npx",
24
+ "args": ["-y", "--package=@awesomate/hosting-mcp", "awesomate-hosting-mcp"]
25
+ }
21
26
  ```
22
27
 
23
- Config resolution: `AWESOMATE_PAT` / `AWESOMATE_API_BASE` env vars, falling
24
- back to `~/.awesomate/credentials.json` (`{ "pat": "...", "apiBase": "..." }`).
28
+ If you use `claude mcp add` instead, keep the `--package=` form — the claude
29
+ CLI pre-scans the whole argv for its own global `-p`/`--print` flag (even
30
+ after `--`), so a bare `-p <pkg>` breaks its option parsing.
31
+
32
+ Account resolution: `AWESOMATE_PAT` env → `AWESOMATE_ACCOUNT` env →
33
+ `.awesomate.json` folder pin → sole/default profile in
34
+ `~/.awesomate/credentials.json` (multi-account since 0.7.0).
25
35
 
26
36
  ## Tools (v0.1 — read-only)
27
37