SolerAds runs a remote MCP server. Claude, ChatGPT and Cursor can read your accounts and propose changes. A person approves every change in the SolerAds console. The AI never changes Google Ads or Meta.
One address for every client: https://solerads.com/api/mcp. You sign in with your SolerAds account, and the consent screen lists the accounts the AI may read.
https://solerads.com/api/mcp as the URL.https://solerads.com/api/mcp as the URL.Cursor connects with an API key, not with the sign-in page. A SolerAds admin creates the key in the console, under AI access. Add this to your mcp.json:
{
"mcpServers": {
"solerads": {
"url": "https://solerads.com/api/mcp",
"headers": { "Authorization": "Bearer sk_mcp_..." }
}
}
}
Replace sk_mcp_... with the key. It is shown once when it is created and never again.
Claude and ChatGPT connect with the SolerAds sign-in page (OAuth). API keys are for Cursor and scripts only, and a SolerAds admin creates them, with an explicit list of accounts and the permission to read or to propose. The write permission is available only after your organisation has requested it and SolerAds has approved it; before that, every key and every connection is read-only. A client account never receives an API key.
In the console, under AI access, every connected app is listed. Disconnecting one revokes its access immediately, and the next call it makes is refused. The same screen shows what each app asked and what it read.