SearchAd AI exposes a Model Context Protocol (MCP) server at searchad.ai/mcp. Any MCP-compatible client (Claude Code, Cursor, Claude Desktop, Cline, Continue) can drive your Apple Search Ads account through it. Same approval gate, same audit log, same spending envelopes. You get to stay in the editor or chat surface you already prefer.
Claude Code is Anthropic's CLI agent. Drop a SearchAd MCP key into its config and your shell can read accounts, propose plans, and (within your envelope) deploy.
Read the integration IDE · CursorCursor's MCP support lets the same agent that writes your code also draft your launch campaigns. Useful for indie devs running both growth and engineering.
Read the integration Desktop · AnthropicClaude Desktop was the first widely deployed MCP host. The setup is two lines of JSON in a config file; the first prompt works immediately.
Read the integration VS Code · Open sourceCline runs an autonomous coding agent inside VS Code. Wire it to SearchAd and the same agent can launch the campaign at the end of a feature shipping session.
Read the integration IDE · Open sourceContinue runs across VS Code and JetBrains IDEs and supports MCP out of the box. Same workflow, more editors.
Read the integration ReferenceIf you built your own agent (LangGraph, Mastra, in-house Python) the raw HTTP and JSON-RPC endpoints are documented. Same tool surface, same safety primitives.
Read the MCP APIThe Model Context Protocol is the closest the AI ecosystem has to a USB-C standard for tool-using agents. By exposing one MCP server, SearchAd AI lets you bring your own client. The interesting part is that none of the safety guarantees depend on which client you bring. The approval gate is enforced server-side. The audit log records every call regardless of the originating tool. The kill switch revokes every key everywhere at once.
That means you can let an indie dev work from Cursor while a contractor uses Claude Desktop and a CI script hits the raw HTTP endpoint. Three clients, one account, one audit trail. The Apple credentials never leave Cloud Functions in any of those paths.
Your existing AI client drives your Apple Search Ads account through SearchAd AI's MCP server. You stay in the tool you already use; SearchAd AI handles authentication, the approval gate, the audit log, and the connection to Apple.
Any MCP-compatible client. Today the most popular are Claude Code, Cursor, Claude Desktop, Cline, and Continue. If your client speaks MCP, it works.
No. Each integration is a URL plus a bearer token pasted into the client's MCP config. The token is issued from your SearchAd AI dashboard. Restart the client and it can immediately read your Apple Search Ads account.
Yes, by construction. Every key carries a scope and a daily spending envelope. Anything outside the envelope requires an out-of-band approval from you. A one-tap kill switch revokes every key instantly. Apple credentials never leave Cloud Functions.
MCP calls do not cost SearchAd credits. Your client's LLM (Claude, GPT, or whatever it runs) bills against your own subscription. SearchAd's plan covers the tool surface and the underlying Apple API. Paid plans only.
Pick a client below to set up in under two minutes.