# Amply > In-app orchestration. Decide which experience each user gets, without an app release. Your app already has the screens and actions — Amply decides who sees each one, and when, from a dashboard your growth team owns. Amply is the layer between user context and in-app behavior. Engineering registers the screens and actions the app already exposes; the growth team then targets them by audience and trigger from a dashboard. No new release ships when you change a campaign. ## Docs - [Documentation](https://docs.amply.tools) - [Full LLM context](/llms-full.txt) ## How It Works (3 steps) 1. **Connect** — Engineering runs the setup autopilot in their editor: it installs the SDK, wires up events, and provisions the dashboard in one engineering sign-off. After that, approved screens and custom functions are registered so they become available to the dashboard. 2. **Create** — Growth team builds a campaign in the dashboard: pick the **When** (event that fires), the **Who** (audience), and the **What** (which registered screen or function to trigger). 3. **Run** — Launch, measure, adjust. Test new experiments as growth strategy changes — no engineering ticket required. ## Setup and AI-Agent Integration Amply ships an official MCP server and an open-source integration skill. Both run in any MCP-compatible AI agent (Model Context Protocol). These two tools are the setup autopilot in Step 1. **MCP server** — lets an AI agent sign up, create projects, register applications, mint API keys, and create and manage campaigns programmatically. No dashboard required. - Claude Code: `claude mcp add amply -- npx -y @amplytools/amply-mcp` - Codex CLI: `codex mcp add amply -- npx -y @amplytools/amply-mcp` **Integration skill** — integrates the SDK: analytics audit, event and Custom-Property mapping, SDK init, Who/When/What campaign-readiness audit, deeplink wiring, build verification, test-event confirmation. Detects the MCP and uses it for backend automation when connected. - Claude Code plugin: `/plugin marketplace add amply-tools/claude-plugins` then `/plugin install amply-integration@amply` **Repos and package** - MCP server: https://github.com/amply-tools/sdk-mcp — npm `@amplytools/amply-mcp` - Integration skill: https://github.com/amply-tools/sdk-skill - Plugin catalog: https://github.com/amply-tools/claude-plugins ## Core Concept: Who / When / What A campaign in Amply is a rule with three parts: - **When** — an event your SDK already fires (e.g. `MoodTracked`, `ExportTapped`, `DiveLogged`) - **Who** — an audience defined by custom properties (e.g. `is_premium = false`) - **What** — a registered screen, deeplink, or app-side function (e.g. native review prompt, paywall deeplink, rewarded ad gate) The decision layer is the product. Screens and actions stay in your app. ## Use Cases - Onboarding by entry — users from different ad campaigns get different first sessions - Survey after friction — when a user abandons setup or skips a key step, ask why before the context is gone - Offer at the upgrade point — when a user hits a limit, test the next best offer - Rate-review prompt at a value moment — fire a review prompt only after a positive event - Rewarded-ad gate — gate an export or premium action behind a watch-an-ad flow for non-paying users - Premium upsell on a value-moment event — deeplink to a paywall the moment the user shows intent ## Live in Production Real campaigns running on Amply today: - **Happens** (voice journal) — native review prompt on `MoodTracked`, first time - **StillFrame** (video frame grabber) — rewarded-ad gate on `ExportTapped` for non-premium users - **Seabook** (fish ID & dive log) — premium upsell deeplink on `DiveLogged` for non-premium users ## What Amply Is and Is Not **Is:** an in-app orchestration layer — a remote control for triggering experiences and actions that already exist in your app. **Is not:** a payment platform (keep RevenueCat/Adapty), an analytics suite (keep Amplitude/Mixpanel), an attribution tool (keep AppsFlyer/Adjust), an ad mediation stack, or a backend for your game economy. Amply runs alongside them and controls **when** registered in-app logic fires. ## Platform Support - iOS - Android - React Native - Unity (coming soon) - Flutter (coming soon) ## Pricing Free to start. No credit card. Annual billing saves ~20%. - **Starter — Free**: 1 project, 1,000 MAU, 3 experiments - **Core — $49/mo ($39/mo annual)**: 3 projects, 25,000 MAU/project, 20 experiments/project, remote price changes - **Growth — $149/mo ($119/mo annual)**: 10 projects, 100,000 MAU, unlimited experiments, remote price changes - **Enterprise — Custom**: custom limits, remote price changes, dedicated support ## Links - [Website](https://amply.tools) - [Documentation](https://docs.amply.tools) - [Terms](https://amply.tools/terms) - [Privacy Policy](https://amply.tools/privacy-policy) ## Contact - Email: contact@amply.tools