Managed Apple Ads MCP

Give your AI Apple Ads tools, not private keys.

Lily is the connection layer between your AI workspace and Apple Ads. Ask for live reports, revenue diagnostics, keyword plans, and controlled campaign actions without wiring the Campaign Management API yourself.

Connect Lily Read the MCP docs

Lily Ads

Scoped connection

Which keywords spent more than $50 without creating a paying user this month?

Lily checked Apple Ads cost against connected revenue and found four terms to review. No campaign changes were made.

Transport

Remote MCP

Authentication

Scoped OAuth

Writes

Approval-first

One managed connection

Skip JWT signing, pagination, retries, and API migrations.

Open-source endpoint wrappers are useful when you want to own every infrastructure detail. Lily manages the remote connection and exposes workflows shaped around Apple Ads decisions rather than raw endpoints.

Campaign, ad group, keyword, search-term, and country reporting
Revenue-aware analysis through RevenueCat or AppsFlyer
Dry-run plans and staged write operations

Credential boundary

The AI client never receives your Apple Ads credentials.

You authorize Lily. The AI client receives scoped Lily tools through OAuth. This separates the conversation surface from Apple Ads account credentials, billing, and organization administration.

Built for outcomes

Ask for the campaign package, not a sequence of endpoints.

Lily can research performance, validate a budget, prepare campaign structure, and return a reviewable plan. New campaign packages stay paused or dry-run until confirmed.

How it works

A clear path from connection to decision.

01
Connect Apple Ads in Lily
Choose the app and account that should become available to your AI workspace.
02
Authorize your AI client
Add Lily from ChatGPT, Claude, Codex, or another compatible client using scoped OAuth.
03
Ask, inspect, approve
Start with reporting, then review any prepared write as a discrete action before it is applied.

Questions

Before you connect

Is Lily an official Apple MCP server?

No. Apple publishes the Apple Ads APIs. Lily is an independent managed MCP and workflow layer built on authorized Apple Ads access.

Does the MCP expose destructive delete operations?

Customer-facing workflows favor reversible actions such as pause. Writes are scoped, logged, and require approval in self-serve mode.

Can I use Lily MCP without revenue data?

Yes. Apple Ads reporting and campaign workflows work without RevenueCat or AppsFlyer. A revenue connection adds paying-user and ROAS context.

Next step

Put your Apple Ads data into the conversation.

Connect Lily