Apple Ads MCP: connect an AI assistant to your campaigns

The Model Context Protocol describes itself as an open-source standard for connecting AI applications to external systems. An Apple Ads MCP server is one of those connections: it holds your API credentials, calls Apple’s API on the assistant’s behalf and returns the result, so you can ask for a report or a keyword change in plain language. Apple does not list an MCP server of its own; the servers you find are built by other developers, and each is only as current as the API it calls. Apple’s new API covers campaigns, ad groups, keywords and negative keywords, ads and creatives, product pages, budget orders, reports, insights, recommendations and change history, so a server built on it can reach all of these.

Both APIs use the same OAuth 2 setup. An account administrator invites a user with an API role in Apple Ads under Account Settings > User Management. That user generates a private key with OpenSSL, extracts the public key and pastes it under Account Settings > API, which shows a clientId, teamId and keyId. From those you sign a client secret, a JWT whose expiry must be less than 180 days from when it was issued, and exchange it for an access token that lives one hour. Apple’s client libraries handle requesting and refreshing that token for you. Apple also says to keep the private key secure and never share it, and to re-create it and the client secret if it is compromised, which matters when a hosted MCP service asks you to hand the key over.

Roles are assigned in the Apple Ads interface and cannot be set through the API. Apple lists API Account Read Only for read-only access to all resources, API Account Manager for full read and write access, and two limited roles, API Read & Write and API Read Only, that apply to a limited set of resources. If you only want the assistant to answer questions about performance, a read-only API user is enough; give write access only when you want it to change bids, keywords or budgets. The Platform API’s GET /v1/acls call returns each ad account a token can reach and the role on it, which is a quick way to confirm what a server can do.

Apple’s Campaign Management API pages now carry the notice that it is deprecated and will be sunset on January 26, 2027. For an MCP server, the questions are simple: which API does it call, and does its developer plan to move it. The new API scopes requests to an ad account rather than an organization, with an X-AP-Context: adAccountId header instead of orgId, and covers Apple Maps campaigns as well as the App Store. To run App Store campaigns, the ad account needs the APPSTORE_APP_MANUAL product feature and a content provider delegation. Every response carries rate-limit headers, and on a 429 Apple asks clients to wait the Retry-After seconds and back off, which an automated assistant making many calls will run into.

Apple Ads can place an app in search results, on the Search tab, on the Today tab and on other apps’ product pages. What those ads send people to is still your product page, so the basics in the ASO checklist and App Store keywords apply, and how to promote an iOS app covers the free App Store tools. Censuus ranks apps by the real visit traffic they draw on the web; adding your app is free on the submit page, and sponsorship raises placement and adds a followed link to your website, see the sponsor page. We do not promise installs or store rankings.