Connect Apple Ads to a desktop MCP client

Set up Apple Ads MCP in a desktop client. Choose remote HTTP, complete browser authorization, check account access, and troubleshoot local connection issues.

A hosted server in an installed client

A desktop MCP client can use Apple Ads MCP without running the connector on your computer. It needs remote Streamable HTTP support and an OAuth flow it can complete in a browser. Check the compatibility guide if the application only offers a command or executable field.

The server endpoint is https://appleads-mcp.com/mcp. You can authorize the desktop client now. Advertising reports need a connected Apple account; check the current connection availability on your account page.

Check Apple account connection availability

Sign in at your account page and read the Apple connection guide. Account connections are not available yet. Connection-status and feedback tools can be used now; campaign reports need a connected account.

Add the connection in your desktop application

1. Open its MCP or remote connector settings.
2. Add a remote HTTP server named Apple Ads MCP. Use https://appleads-mcp.com/mcp as the URL.
3. If the application distinguishes remote HTTP from local standard input/output, select remote HTTP. Do not enter the URL as a local launch command.
4. Start the connection and complete sign-in and consent in the browser it opens.
5. Return to the application and confirm that discovery finished and the tools are enabled.

If your application uses a configuration file instead of settings controls, use its documented remote-server schema. There is no single configuration-file format shared by every MCP client. You do not need to install a local copy of this hosted server.

Verify the selected account

Call the Apple Ads access-status and identity tools. Show the selected ad account, confirm the write tier is read, then list campaigns without changing anything.

Use apple_ads_get_access_status, apple_ads_whoami and apple_ads_get_campaigns. If you can manage several accounts, confirm the returned account ID before asking for a report or proposing a change.

Recover from desktop connection problems

• The browser closes before authorization completes: restart the connection from the desktop client and finish the consent flow.
• The browser succeeds but the application stays disconnected: check the client's callback and authentication status using its own troubleshooting instructions.
• The tools worked, then authorization expired: reauthenticate from the client.
• Apple rejects a request: check the selected ad account and connection status here.
• A tool says a write may have succeeded: inspect the resource before retrying, even if the application reports a connection error.

Keep changes deliberate

Client authorization and advertising permission are separate. A desktop connection starts with the same read-only default as a web connection. Follow the write-access guide before enabling changes. New campaigns, ad groups and targeting keywords start paused.