integrations

The services you chose, wired in.

Amba configures and composes with the services already in your stack — it never replaces them. Each guide here covers the evaluation questions: exactly what syncs, what drives what downstream, and what stays with the provider. Configuration is one MCP tool call (amba_integrations_configure), verification is another (amba_integrations_test), and the step-by-step depth lives in the docs.

the guides
INTEGRATION GUIDE

RevenueCat + Amba

Connect RevenueCat to Amba: nine webhook events sync entitlements server-side, subscribers flow into segments and push, and an agent wires it all over MCP.

Read the guide →
configurable today
providerwhat it doesread more
RevenueCatSubscription state sync — webhook events become entitlements, segments, and push targetingGuide →
SuperwallPaywall management — configured and tested over the same integration toolsDocs →
APNsApple push credentials (.p8) — stored server-side, verified with a live connection testDocs →
FCMAndroid push credentials (service-account JSON) — stored server-side, verified with a live connection testDocs →
Web subscriptionsWeb checkout through your own billing account — web purchases grant the same entitlements as mobile onesDocs →

Provider list verified against the shipped integration registry, June 2026. Push credentials are passed inline at configure time and stored server-side — secrets are never returned to a client.

start in 30 seconds

Hand the docs to your agent.
Ship by lunch.

Read the docs