Getting started
AdPilot MCP connects Apple Ads and RevenueCat to the AI assistant you already use—ChatGPT, Claude, Cursor, Codex, or another MCP-compatible client.
You configure apps, connections, and limits once in the control panel. Your assistant then analyzes performance and executes requested changes directly within those limits. AdPilot is not a new chat UI; the work happens in your AI client.
- The path to your first question
- What lives where
- What “complete days” means
- Before enabling campaign writes
- First-review checklist
- How AdPilot uses this setup
- Next steps
- Official sources
The path to your first question
- Create a workspace — Sign up and confirm your email. AdPilot creates a workspace for your apps and MCP access.
- Invite a teammate (optional) — Solo includes one teammate seat and Studio includes four. Open Settings → Members, enter the teammate's email, choose a role, and send the invitation. See Invite and manage workspace members.
- Add and describe an app — Import the app from the App Store and confirm its strategy profile (goals, protected terms, notes). This context travels with every MCP request.
- Prepare Apple API access — Set up Apple Ads under the correct individual or legal entity, link App Store Connect, retain an Account Admin, and invite a dedicated Apple Account with an API role. AdPilot supports customer-managed API credentials; review the supported setup in Set up an Apple Ads account and API user.
- Connect Apple Ads — Generate a P-256 signing key in AdPilot, create the customer-managed Apple API client with its public key, enter the Client, Team, and Key IDs, and test the connection.
- Connect RevenueCat (recommended) — Link RevenueCat so mapped Apple spend can be compared with blended app-level proceeds. Without it, profitability questions stay incomplete.
- Set limits — Configure the workspace spend ceiling, bid cap, countries, and evaluation window on Limits. Optionally confirm an app-level monthly ad-spend cap under the app strategy. The workspace ceiling is required before a campaign can be enabled, restored, or given a higher usable budget. See Spend limits and projections.
- Connect an AI client — Add your workspace MCP endpoint in your assistant. OAuth authorizes the client; it appears under MCP Clients.
- Ask a question — Start with a read-only review, for example: Review all campaigns for this app for the last 30 complete days.
Analytics become available after Apple campaigns are mapped to an app and a metrics synchronization completes. Run a manual sync from Connections, or wait for the daily scheduled metrics sync. Every built-in skill is ready automatically; explore workflows and example requests from Skills.
Every new workspace starts on Free. Free supports the owner only, one app, one MCP client, 30 days of history, and read-only analysis. Upgrade to Solo to invite one teammate or Studio to invite up to four. See Plans, pricing, and subscription limits before you need shared access, more apps, direct operations, or scheduled reports.
What lives where
| Place | Purpose |
|---|---|
| Home | Setup checklist, connection status, starter prompts |
| Apps | App inventory, strategy profiles, RevenueCat mapping |
| Connections | Apple Ads and sync status |
| Settings → Workspace | Workspace name, country, currency, and timezone |
| Settings → Members | Invitations, roles, member access, and ownership |
| MCP Clients | Authorized assistants and the MCP URL |
| Skills | Ready-to-use workflows your assistant can follow |
| Changes | Review operations, external changes, and activity |
| Limits | Spend, bid, country, evaluation, and plan limits |
What “complete days” means
Analysis tools use finished calendar days in your workspace timezone. Partial today data is excluded so day-over-day comparisons stay fair. When you ask for “last 30 days,” expect thirty complete days ending yesterday.
Before enabling campaign writes
The workspace ceiling and app cap are authorization thresholds; they do not rewrite Apple campaign budgets. Review the Maximum projected month on Limits before your first write. It represents possible daily-budget exposure, so it can be higher than recent actual spend.
If the projection is already above a cap, AdPilot still allows operations that reduce exposure, such as pausing a campaign or lowering an active budget. It blocks new increases until the proposed projection fits the applicable workspace and confirmed app limits.
First-review checklist
- The Apple API user accepted the invitation with the invited email address.
- The Apple Ads connection test passes and the latest metrics sync completed.
- Campaigns are mapped to the correct app.
- RevenueCat is connected before you interpret proceeds or ROAS.
- Workspace currency, timezone, limits, and protected terms are correct.
- Your first request is read-only and names an app plus a complete-day range.
How AdPilot uses this setup
AdPilot combines the app profile, Apple campaign mapping, synchronized metrics, optional RevenueCat proceeds, available skills, and workspace limits for each MCP request. Missing or stale inputs appear as data-quality warnings instead of being silently treated as zero.
Next steps
- Mobile app marketing fundamentals
- Apple Ads metrics and formulas
- Connect your AI client
- Invite and manage workspace members
- Set up an Apple Ads account and API user
- Apple Ads connection
- Spend limits, projection, and audit
- Plans, pricing, and subscription limits
- What to ask