MCP Server

The Model Context Protocol is an open standard that lets AI agents call external tools with strict input schemas. The Amba MCP server exposes every Admin API capability as a typed tool — when your agent decides to "create a push campaign for inactive users," it calls amba_push_campaigns_create directly, with the right argument shape, and gets a typed response back.

Amba's MCP server covers every Admin API capability as a typed tool — projects, push, segments, remote config, content, streaks, gamification (XP, achievements, leaderboards, challenges), social (friends, groups, feeds, messaging, reviews), economy (currencies, catalog, stores, inventory, referrals), and platform (onboarding, roles, deep links, media, moderation).

Two ways to authenticate:

• Bearer token — for desktop and IDE clients (Claude Desktop, Cursor, Windsurf). Same token the CLI uses, scoped to the projects you own.
• OAuth 2.1 + PKCE — for browser-based clients (Claude.ai web). Authorize once; the connector refreshes silently after that.

Quick connect

Server URL:     https://mcp.amba.dev/mcp
Bearer auth:    Authorization: Bearer <your-developer-token>
Get a token:    https://app.amba.dev/settings/api-keys
OAuth metadata: https://mcp.amba.dev/.well-known/oauth-authorization-server

The server speaks Streamable HTTP — no local subprocess, no Node install. Add the URL to your MCP-aware client (Claude.ai web, Claude Desktop, Cursor, Windsurf) and your agent can drive Amba from chat.

Next

• Install — per-client config snippets.
• Tools — what's available, grouped by domain.
• Examples — prompts that work end-to-end.