Apple Ads MCP client compatibility
Check Apple Ads MCP client requirements: remote Streamable HTTP, OAuth, tool discovery and account access, with web and desktop setup guides.
One hosted endpoint
Apple Ads MCP exposes its tools at https://appleads-mcp.com/mcp. A compatible client must speak remote Streamable HTTP and complete OAuth authorization. Support for a local MCP process alone is not enough for this hosted endpoint. See the MCP transport specification for the distinction between standard input/output and Streamable HTTP.
Check these capabilities
| Capability | What to check |
|---|---|
| Remote transport | The client accepts a server URL over Streamable HTTP. |
| Authorization | The client supports browser-based OAuth for a protected remote MCP server. |
| Discovery | The client can discover tools after authorization and expose them in the current conversation. |
| Account policy | Your plan or workspace permits custom remote connections. |
| Results | The client can present structured tool results, including errors and continuation fields. |
Web and desktop connections
A web client typically manages connectors in its account or workspace settings. A desktop client may use settings or a configuration file and send you to a browser for authorization. Follow the web setup guide or desktop setup guide for the service-specific sequence, then use your client's documentation for its exact controls.
MCP standardizes communication, not the names of settings screens or configuration-file keys. A JSON block accepted by one client is not automatically valid in another. Prefer the client's native remote-server support when available.
Authorization is separate from the Apple key
Sign in here and check the Apple account connection guide. Account-status and feedback calls work before an advertising account is connected. The remote client receives an OAuth authorization to this service. Saved Apple credentials stay encrypted on the server. The MCP authorization specification describes the remote authorization flow.
Prove the connection with a read
Call apple_ads_get_access_status, apple_ads_whoami and apple_ads_get_campaigns. Confirm the default ad-account ID and read tier. These checks distinguish a working remote connection from a client that saved a URL but did not authorize successfully.
Local-only clients and recovery
If a client only accepts a local executable, it cannot call this endpoint directly as a standard-input/output server. Check whether its current release supports remote HTTP or a supported adapter. Any adapter must also handle this service's OAuth requirements; changing the transport alone does not grant access.
After an expired client authorization, reconnect from the client. After an Apple credential failure, check the connection status on your account page. Use the troubleshooting guide to identify which connection needs attention.