The SaaS Ads Studio API
Today, That Means MCP

If you searched for the SaaS Ads Studio API, here is the honest, complete answer.

The straight answer

There is no traditional REST API today. Programmatic access to SaaS Ads Studio runs through the Connect Atlas MCP server, and that is a deliberate choice rather than a gap.

MCP (Model Context Protocol) is an open standard for letting software, especially AI assistants and agents, call tools on other systems. Our MCP server exposes Atlas as 21 documented tools over standard Streamable HTTP with OAuth 2.1 sign-in. That is an API by any practical definition: a stable set of callable operations with typed inputs, structured JSON results and documented errors. It just speaks MCP instead of plain REST, which means every MCP-capable client and SDK already knows how to talk to it, and you never handle credentials beyond a browser sign-in.

We built this interface first because it is how people actually use Atlas programmatically: through Claude, ChatGPT, Cursor and agent frameworks, not hand-rolled HTTP calls.

What you can do programmatically today

Everything below works right now, through any MCP client, for any account with an active or trialing subscription.

• Read account state and performance. Confirm the connected account, pull a Google Ads performance summary for the last 7, 30 or 90 days, and list Atlas’s automations with their enabled state.
• Review and decide on changes. List the actions Atlas has proposed or made, inspect one in detail down to individual items, then approve or reject it, in full or item by item.
• Trigger Atlas’s management. Run any of the 18 optimisation automations on demand, and set the approval tier that governs how changes apply, globally or per automation.
• Build a Google Ads campaign end to end. Set budget and countries, generate and save grouped keywords, generate and save responsive search ads, then create the campaign. Campaigns are always created paused, so nothing spends until a human unpauses it.
• Generate Meta assets. Produce audience ideas, ad copy variants and creative briefs for Facebook and Instagram. These are plans to apply yourself in Meta Ads Manager; the API never writes to your Meta account.

The tool reference documents every tool with its parameters and errors.

Quickstart

The server URL is the same for everyone, with access controlled by OAuth sign-in:

https://clgrwyawpxkagaqukmqf.supabase.co/functions/v1/mcp-server

1. Point any MCP client at that URL as a remote Streamable HTTP server. The setup guide has exact steps for Claude, Claude Code, ChatGPT and Cursor.
2. Complete the browser sign-in with your SaaS Ads Studio account the first time a tool runs.
3. Call whoami to confirm the connection, then use any of the 21 tools.

From an agent framework or script, use your language’s MCP SDK, connect to the same URL, and complete the one-time OAuth approval in a browser. Your MCP client manages tokens after that.

On the roadmap

API keys for headless access are on the roadmap: long-lived keys your servers can use without a browser sign-in, for scheduled jobs and backend integrations. We are not publishing dates or the final shape yet, and nothing on this page depends on them.

If API keys, webhooks or a plain REST surface would unlock something for you, tell us through the app. Real requests directly shape the order we build in.