The Apple Ads MCP server for app growth teams

Apple Ads MCP connects your App Store advertising data to AI assistants through the Model Context Protocol. You ask Claude, ChatGPT, or another MCP client about campaigns, keywords, taps, and installs, and the AI pulls the reports and explains what changed.

Both refer to the same platform: Apple rebranded Search Ads to Apple Ads as the product grew beyond App Store search placements. People still search for both names, and this page covers the same ads either way.

No. Apple publishes the Apple Ads Campaign Management API, but no official MCP server. The ecosystem is community open-source projects, some quite deep, plus managed layers like Markifact.

The best open-source servers wrap the full v5 API including write endpoints, and they are genuinely good if you are technical. The tradeoffs: you host them, you manage Apple API keys and certificates, they cover Apple only, and when Apple retires the v5 API in January 2027 you wait on the maintainer. Markifact is hosted with OAuth, multi-account, puts Apple next to your other UA channels, and absorbs the API migration.

Not yet. Markifact's Apple Ads access is reporting-only today: campaigns, ad groups, keywords, and their performance. Write actions live on Google Ads, Meta, TikTok, and Pinterest in the same connection, always behind approval.

The apple_ads_get_report operation covers campaign, ad group, and keyword level performance including spend, impressions, taps, installs, cost per tap, and cost per install, with custom dimensions, filters, and date ranges. The apple_ads_list_report_fields operation lists everything your account can answer.

Apple has announced the v5 Campaign Management API sunsets in January 2027, with a new Apple Ads Platform API arriving before that. If you self-host an MCP server, that migration is your problem or your maintainer's. Markifact handles it server-side, and your MCP connection keeps working unchanged.

Yes, and for user acquisition teams it is the whole point. Cost per install comparisons across every channel, in one conversation, with GA4 available to check what installs do afterward.

Yes, and Apple Ads has a diagnosis trick the AI applies automatically: if taps held steady while installs fell, your ads are fine and your App Store product page is converting worse, which points at the listing, pricing, or reviews rather than bids.

No. Running an Apple Ads MCP yourself means creating API keys and managing certificate-based authentication. With Markifact you connect once with OAuth and the hosted MCP server handles it.

Yes. Connect several accounts and switch between them inside one conversation, which matters for agencies and multi-app publishers.

Markifact uses a secure OAuth-based connection for Apple Ads access. Your tokens are never exposed to the AI client, and report data is processed in real time without retention.

Yes. Sheets and Slack are Markifact operations too, so a client-ready keyword report can land in a spreadsheet, and a weekly UA summary can post to your team's channel, all from the same MCP session.