jujugrowth-mcp 1.0.5 → 1.0.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 +14 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -39,9 +39,20 @@ claude mcp add jujugrowth --scope user \
|
|
|
39
39
|
The jujugrowth Settings → Developer panel generates the token and shows these
|
|
40
40
|
commands pre-filled.
|
|
41
41
|
|
|
42
|
-
3. Restart the client.
|
|
43
|
-
|
|
42
|
+
3. Restart the client. **First use:** your AI will ask to approve the jujugrowth
|
|
43
|
+
tools the first time it calls them — approve them. (In Claude Code, if it's in
|
|
44
|
+
"don't ask"/deny mode it silently refuses — toggle the permission mode or run
|
|
45
|
+
`/allowed-tools`, then approve once.)
|
|
46
|
+
|
|
47
|
+
You'll have these tools:
|
|
48
|
+
- `list_recommendations` — open recommendations (one site if the token is scoped)
|
|
44
49
|
- `get_recommendation` — the full brief for one (implement it in your repo)
|
|
45
|
-
- `mark_recommendation_handled` — mark it done
|
|
50
|
+
- `mark_recommendation_handled` — mark it done (with a note of what you changed)
|
|
51
|
+
- `request_site_advice` — Pro: trigger a fresh website analysis
|
|
52
|
+
- `request_campaign_brief` — Pro: trigger a campaign brief
|
|
53
|
+
|
|
54
|
+
A token can be scoped to one business; the server then announces itself as
|
|
55
|
+
`jujugrowth (yoursite.com)` and only ever touches that site. Generate scoped
|
|
56
|
+
tokens in jujugrowth → Settings → Developer (one per business/repo).
|
|
46
57
|
|
|
47
58
|
Requires Node ≥ 22. Optional env `JUJUGROWTH_API` (defaults to https://jujugrowth.com).
|
package/package.json
CHANGED