MCP for advertising: what it is, and what it changes
Pasting a Google Ads table into a chat loses half the context and all the history. MCP fixes that: the assistant fetches the figures itself, inside a scope you defined.
What is MCP applied to advertising?
MCP (Model Context Protocol) is an open standard that lets an AI assistant call tools provided by a third-party service. Applied to advertising, it lets Claude or ChatGPT read your ad accounts through a connector — connected accounts, spend, campaigns, search terms, recommendations — without you copying a single figure and without the assistant receiving your ad platform credentials.
The problem MCP solves
An AI assistant is excellent at explaining a table, but it can only work with what it is given. Without a connector, the user exports a CSV, pastes it into the conversation, and the assistant reasons over a frozen snapshot, with no idea which period it covers or what is missing around it.
MCP reverses the mechanism: the assistant asks, the service answers. It can refine, compare two periods, drill down to one campaign — and it always knows where the figure it quotes came from.
What the SaveAds connector exposes
The connector gives access to eight read tools. Each returns readings already synced by SaveAds, not a live call to the ad platform — an account connected five minutes ago may have nothing to show yet.
- list_ad_accounts — the connected ad accounts, their platform and their currency.
- get_performance — spend, clicks, conversions and cost per acquisition over a period.
- list_campaigns — campaigns, their budgets and their results.
- list_search_terms — search terms, including those costing money without converting.
- list_recommendations — the recommendations SaveAds produced.
- list_optimizations — what has already been applied, and its measured effect.
- search and fetch — searching within that scope and reading one specific item.
Read-only, by design
None of the eight tools modifies a campaign, a budget or a bid. An assistant connected to SaveAds can analyse, compare, explain and prepare a decision; it cannot execute one. Changes are applied from SaveAds, where safeguards and rollback exist.
The CRM, included from the Business plan, adds its own tools — and those do write, but inside SaveAds only: log a call, add a note, schedule a follow-up, advance a deal. Every change carries its author (“by the assistant”), can be undone for twenty-four hours, and anything that commits a figure — deal won, amount, merge, deletion — comes back as a proposal you confirm in one click. No campaign, budget or bid is ever touched from the connector, CRM included.
This is not a technical limitation but a deliberate boundary: a model writing directly into an ad account has no log, no undo and no cap.
What the connection costs, and what it sees
Every tool call consumes one request from your plan’s monthly AI allowance — the same allowance as the built-in assistant and SaveAds analyses. The response states what is left, so you are warned before the block rather than after.
History depth also depends on the plan: when the returned period is shorter than the one requested, the response says so explicitly instead of implying that data is missing.
Which assistant, and where to start
Claude and ChatGPT both accept a remote MCP connector, with two different setup paths — ChatGPT requires developer mode to be turned on first, Claude does not. The dedicated pages walk through each one.
Connecting an assistant in three steps
The path is the same whichever assistant you use; only the third step changes screen.
- 1Connect your platforms to SaveAdsGoogle Ads, Meta, LinkedIn, TikTok, Snapchat: one authorisation per platform, once.
- 2Create a read keyFrom the Claude / GPT tab of your dashboard. One key for both assistants, revocable in one click.
- 3Add the connectorPaste the address https://save-ads.com/api/mcp and the key into your assistant, then ask your first question.
What the connector will not do
- It writes nothing: no campaign, budget or bid is modified by an assistant.
- It never passes your ad platform credentials to the assistant.
- It returns readings already synced, not a live call to the platform.
- It consumes your monthly AI credit allowance, capped by your plan.
Frequently asked questions
Is MCP specific to Claude?
- No. The Model Context Protocol is an open standard. Claude introduced it, but other clients implement it, including ChatGPT through its custom connectors.
Does the assistant receive my Google Ads credentials?
- No. The assistant only talks to the SaveAds connector, with a key dedicated to that use. Ad platform tokens stay on the SaveAds side and never leave it.
How do I cut access?
- Revoke the key from your SaveAds dashboard. The assistant loses access immediately, with no need to touch your ad accounts.
Do I need a paid Claude or ChatGPT plan?
- Custom connectors depend on each vendor’s terms, which change over time. On the SaveAds side, the read key is included in every plan.
Connect your assistant to your ad accounts
Create a read key and ask your advertising questions where you already work.