Connect Atlas
The MCP Server for Your Ads

Connect Atlas lets you plug your AI assistant straight into your ad account. Once connected, you can ask Claude, ChatGPT or Cursor to check your Google Ads performance, run an optimisation, approve changes, or build a whole campaign, all in plain language.

This page covers what Connect Atlas is, how to set it up in each client, and what to try first. For the full list of tools, see the MCP tool reference. For everything Atlas can run on a schedule, see Atlas automations.

What is Connect Atlas

MCP (Model Context Protocol) is an open standard that lets AI assistants use other software. An MCP server describes a set of tools, and any MCP client (Claude, ChatGPT, Cursor and many others) can discover those tools and call them on your behalf.

Connect Atlas is the SaaS Ads Studio MCP server. It exposes Atlas, our AI ads manager, as a set of 21 tools your assistant can use. In practice this means your assistant becomes a second interface to your ad account: you talk, Atlas does the work, and the same safety rules apply as when you use the app.

The MCP server is also our API. There is no separate REST API today, and no API keys to manage. If you want programmatic access to Atlas, MCP is the way in. The API page explains this in more detail.

What you can do

The tools fall into four groups.

Read your account. Confirm the connection, list Atlas’s automations and whether each is enabled, see recent actions Atlas has proposed or made, inspect one action in detail, and pull a Google Ads performance summary for the last 7, 30 or 90 days.

Manage Google Ads. Run any of Atlas’s 18 optimisation automations on demand, approve or reject the changes Atlas proposes (in full or item by item), and set your approval tier so changes apply the way you want. On Google, Atlas manages the account for real: approved changes are applied to Google Ads.

Build a Google Ads campaign. Go from business profile to a ready campaign in one conversation: set the budget and countries, generate and save keywords grouped into ad groups, generate and save responsive search ads, then create the campaign. Campaigns are always created paused, so nothing spends until you unpause it in Google Ads.

Generate for Meta. Generate audience ideas, ad copy variants and creative concept briefs for Facebook and Instagram. These tools produce plans for you to apply yourself in Meta Ads Manager. They never create or change anything in your Meta account.

Requirements

• A SaaS Ads Studio account with an active or trialing subscription. Without one, tools return a no_subscription error.
• For the Google Ads tools to do useful work, a Google Ads account connected in the app.
• An AI client that supports remote MCP servers over Streamable HTTP. Claude (web, desktop and Claude Code), ChatGPT with Developer mode, and Cursor all qualify.

Server details

Detail	Value
Server URL	https://clgrwyawpxkagaqukmqf.supabase.co/functions/v1/mcp-server
Transport	Streamable HTTP (stateless)
Authentication	OAuth 2.1 (sign in with your SaaS Ads Studio account)
Server name	saas-ads-studio
Tools	21 (no MCP resources or prompts)

The connection URL is the same for everyone:

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

There is nothing secret in it. Access is controlled by the OAuth sign-in, not by the URL.

Set up your AI client

Claude Code

Run this in your terminal:

claude mcp add --transport http saas-ads-studio https://clgrwyawpxkagaqukmqf.supabase.co/functions/v1/mcp-server

The first time you use a tool, your browser opens so you can sign in to SaaS Ads Studio and approve the connection.

Claude (web and desktop)

1. Open Settings, then Connectors.
2. Choose Add custom connector.
3. Give it a name (for example “Atlas”) and paste the server URL above.
4. Click Add, then sign in and approve when your browser prompts you.

Custom connectors are available on Claude Free, Pro, Max, Team and Enterprise plans.

ChatGPT

1. Open Settings, then Connectors.
2. Under Advanced, enable Developer mode.
3. Choose Create connector, paste the server URL, and set authentication to OAuth.
4. Save, then sign in and approve when your browser prompts you.

Custom MCP connectors require Developer mode, available on ChatGPT Plus, Pro, Team, Enterprise and Edu.

Cursor

1. Open Cursor Settings, then MCP.
2. Add a new server and paste the server URL as an HTTP (streamable) server.
3. The first time a tool runs, your browser opens so you can sign in and approve.

Other MCP clients

Any client or SDK that supports remote MCP servers over Streamable HTTP with OAuth should work. Point it at the server URL and complete the sign-in when prompted.

How sign in works

Connect Atlas uses OAuth 2.1, the same standard that powers “Sign in with Google”. In plain words:

1. Your AI client registers itself with our authorisation server automatically. You do not need to create anything first.
2. Your browser opens the SaaS Ads Studio consent screen.
3. You sign in with your normal account and click Allow.
4. Your client receives a token and uses it for every tool call from then on.

There are no API keys to copy, store or rotate. One honest note: a connection currently acts with your account’s full abilities, so treat it like your login. Connect assistants you trust.

You can see and revoke every connected app on the Connect Atlas page in the app. Revoking takes effect immediately.

First things to try

Ask your assistant to call whoami first. It confirms the connection works and shows which account it is acting as. Then try a few of these, in your own words:

• “Check my Google Ads performance for the last 30 days and tell me what stands out”
• “List the Atlas automations on my account and tell me which are enabled”
• “Run a mini search term review and show me anything worth blocking”
• “Show me Atlas’s pending actions and walk me through the first one”
• “Set my approval tier to smart”

Your assistant discovers the tools on its own, so you rarely need to name them. Plain requests work.

Safety and control

Everything an assistant does through Connect Atlas runs inside the same guardrails as the app.

• Approval tiers govern changes. On manual, you approve every change. On smart, low-risk changes apply automatically and the rest wait for you. On auto, changes apply automatically, still within Atlas’s safety rails. You can set a different tier per automation.
• Campaigns are created paused. A campaign built over MCP never spends a penny until you unpause it in Google Ads yourself.
• Safety rails outrank approvals. Some protections cannot be overridden, for example a converting or brand keyword cannot be blocked even if an assistant approves the block.
• Overwrite and duplicate guards. Saving keywords over an existing draft, or creating a campaign when one already exists, requires an explicit confirmation flag, so an assistant cannot clobber your work by accident.
• Cooldowns. Each automation can be run at most once an hour on demand.
• Everything is audited. Every tool call is logged against your account.
• Revoke any time. Remove a connected app on the Connect Atlas page and its access ends immediately.

Errors and troubleshooting

Tools return errors as a short code plus a human explanation. The common ones:

Error code	What it means
no_subscription	Your subscription is not active or trialing. Reactivate in the app.
missing_permission	The connection lacks the permission for that tool.
unknown_automation	The automation id was not recognised. Use list_automations to see valid ids.
not_found	The action id does not exist or belongs to another account.
query_failed	A read failed on our side. Try again shortly.
exists	Saved keywords already exist. Confirm, then retry with replace: true.
already_created	A campaign already exists. Confirm, then retry with force: true.
cooldown	That automation ran within the last hour. Wait and retry.
pending_exists	An action of that type is already awaiting review. Review it first.
generation_empty	Generation produced nothing. Fill in your business profile and retry.

Two connection-level problems worth knowing:

• 401 Unauthorized means the sign-in expired or failed. Reconnect the server in your client (sign in again).
• 503 Service Unavailable means MCP access is temporarily switched off on our side. Try again later.

If a tool misbehaves in a way these do not explain, email us at the address in the app and include roughly when you called it. Every call is logged, so we can find it quickly.