Tools
500+ Amba MCP tools, grouped by domain.
The Amba MCP server exposes 500+ tools, grouped by domain below. Every tool wraps an Admin API endpoint — see the API reference for the full request / response shapes.
Your MCP client lists the live set on connect (tools/list returns names + input schemas); the table below is for orientation.
| Domain | Count | What it covers | Sample tool |
|---|---|---|---|
setup | 1 | Platform-specific SDK setup snippets (Expo, RN, native) | amba_sdk_get_setup_instructions |
projects | 2 | List + inspect projects, read API keys | amba_projects_list |
organizations | ~11 | Org tree, app-factory provisioning, and service-account lifecycle | amba_service_accounts_create |
operations | 2 | Poll a long-running async action to succeeded / failed | amba_operations_get |
users | ~9 | List, fetch, update, create users; seed a cohort; reset one user; track events | amba_users_create_cohort |
push | 7 | Campaigns, immediate / scheduled delivery, test sends | amba_push_campaigns_create |
segments | 4 | Rule-based audience definition + on-demand re-evaluation | amba_segments_create |
config | 4 | Remote config keys with segment + percentage conditions | amba_remote_configs_create |
content | 5 | Content libraries, item bulk import, scheduled delivery | amba_content_schedules_create |
streaks | 3 | Streak definitions with grace periods + freezes | amba_streaks_create |
xp | 4 | XP rules, user XP / level lookups | amba_xp_rules_create |
achievements | 4 | Auto-unlock achievements with progress criteria | amba_achievements_create |
leaderboards | 4 | XP / streak / custom leaderboards with windowing | amba_leaderboards_create |
challenges | 4 | Time-limited challenges with rewards | amba_challenges_create |
social | 12 | Friends, groups, feed rules, messaging, reviews | amba_feeds_rules_create |
economy | 15 | Virtual currencies (grant + spend), catalog, stores, inventory, referrals | amba_currencies_grant |
platform | ~21 | Onboarding flows, roles, deep links, media + asset catalogs, moderation, cross-env config promotion (export / import) | amba_onboarding_create |
integrations | 4 | APNs / FCM / RevenueCat / Superwall config + live credential testing | amba_integrations_configure |
analytics | ~14 | Per-domain stats reads (DAU, retention, segment sizes), A/B experiments (CRUD + significance) | amba_experiments_results |
events | ~3 | Backend-side event ingestion + querying | amba_events_track |
Counts mark the current ship; new tools land alongside Admin API additions. Your agent will always see the canonical list — these tables are a map, not the territory.
Recent additions
amba_service_accounts_create/_list/_revoke— create scopedamb_dsvc_backend credentials for app-factory delegated operators. Delegated token minting is HTTP backend-to-backend with the service-account secret, not an MCP tool.amba_media_catalogs_create(+_list/_get/_update/_delete/_add_item/_remove_item) — curate a named, slug-addressable bundle of media assets your app reads in one call.amba_operations_get/amba_operations_list— poll an async action (e.g. a domain purchase) to a terminal status.amba_events_track— record a backend-side event for a user.amba_users_create_cohort— mint N anonymous users sharing properties + segments in one call.amba_users_reset_user— reset one user's state to zero (optionally delete them).amba_collections_reset_data— empty a collection's rows while keeping its schema.amba_entitlements_grant— grant or refresh a user's entitlement.amba_currencies_get_user_balance— read one user's balance for a currency.amba_admin_insert_rowas_system— write a shared null-owner row to a shared collection.amba_client_aggregate_rows— client-side group-by aggregation over a collection.
Tool naming
Every tool starts with amba_ and uses a resource-first snake_case convention:
amba_<resource>_create— make a new resource.amba_<resource>_list— paginate.amba_<resource>_get— single fetch.amba_<resource>_update— mutate.amba_<resource>_delete— remove.amba_<resource>_get_stats— analytics rollups.
(Older verb-first names like amba_create_streak remain registered as
deprecated aliases, so existing agent configs keep working.)
That uniformity matters in practice — agents pick the right tool first try because the names are predictable.
Next
- Examples — prompts that exercise these tools end-to-end.
- API reference — the underlying HTTP endpoints.