@layers/amba-mcp 4.0.3 → 4.0.5
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/dist/expo-build-prompt.js +9 -1
- package/dist/index.js +969 -142
- package/dist/lib/annotations.d.ts +0 -7
- package/dist/resources/amba-setup-infrastructure.d.ts +1 -1
- package/dist/resources/amba-setup.d.ts +1 -1
- package/dist/resources/index.d.ts +1 -1
- package/dist/tools/ai-prompts-admin.d.ts +5 -3
- package/dist/tools/ai-providers-admin.d.ts +30 -0
- package/dist/tools/event-catalog.d.ts +20 -0
- package/dist/tools/experiments.d.ts +24 -0
- package/dist/tools/functions.d.ts +1 -1
- package/dist/tools/leagues.d.ts +12 -0
- package/dist/tools/operations.d.ts +24 -0
- package/dist/tools/promotion.d.ts +28 -0
- package/package.json +1 -1
|
@@ -96,6 +96,14 @@ Tell the user where their credentials live:
|
|
|
96
96
|
|
|
97
97
|
**Already have a PAT?** Skip the signup. Call \`amba_developer_me({})\` to verify the Bearer; if it succeeds, either reuse the most recent project (\`amba_projects_list\`) or call \`amba_projects_create({ name: "<app-name>", platform: "all" })\` and then \`amba_api_keys_create\` twice to mint client + server keys for \`environment: "development"\`.
|
|
98
98
|
|
|
99
|
+
**Can't reach \`amba_developer_signup\` — it's not in your tool list, or your harness blocks the call?** Do NOT try to work around it by adding the MCP server yourself, running an installer, or editing your own settings/permissions — refusing to self-modify or widen your own permissions is the correct call, and you should not circumvent it. Instead, hand the developer **one** command to run in **their own** terminal (which is not subject to your sandbox):
|
|
100
|
+
|
|
101
|
+
\`\`\`bash
|
|
102
|
+
npx @layers/amba init
|
|
103
|
+
\`\`\`
|
|
104
|
+
|
|
105
|
+
It creates the account with no browser and writes \`AMBA_PROJECT_ID\` + \`AMBA_CLIENT_KEY\` to \`.env.local\` (and wires this MCP server up for your next session). Ask them to run it, tell you when it's done, then resume from this Step 0 by reading \`.env.local\`. Asking the developer to paste an \`amb_ck_…\` client key is the last-resort lite path — it's enough to wire \`Amba.configure()\` + runtime calls and verify events land, but a client key alone can't do admin provisioning (creating achievements, collections, segments, etc.), which needs the PAT or server key.
|
|
106
|
+
|
|
99
107
|
## Step 1 — Classify the app
|
|
100
108
|
|
|
101
109
|
Look at what the user told you and at any files they shared. You're trying to pick one of ten presets in 30 seconds, not write a treatise. Inputs:
|
|
@@ -217,7 +225,7 @@ SKIPPED (low signal — re-run with /amba <feature> if you want them)
|
|
|
217
225
|
NEEDS YOUR INPUT
|
|
218
226
|
- Apple Sign In: add the "Sign in with Apple" capability in Xcode > Signing & Capabilities.
|
|
219
227
|
- Google Sign In: paste your Google OAuth client ID into amba_projects_update({ google_oauth_client_id: "..." }).
|
|
220
|
-
- APNs / FCM:
|
|
228
|
+
- APNs / FCM: configure credentials with amba_integrations_configure (paste the .p8 / service-account JSON inline) before push delivers.
|
|
221
229
|
|
|
222
230
|
NEXT STEPS
|
|
223
231
|
- Paste AMBA_CLIENT_KEY into your build env (already shown above)
|