How to connect Microsoft Copilot to Google Ads

What actually works today

It is worth being plain about this before you spend any time in a settings screen, because the honest picture is not the same for every assistant. In Claude and ChatGPT a remote MCP connector is added in one click: paste the address into connector settings and you are done. Consumer Microsoft Copilot does not add an arbitrary remote MCP server the same way.

For Copilot, MCP arrives through the agent-building layer — Copilot Studio, where you author an agent and attach the connector as a tool, and Microsoft 365 Copilot, where that published agent becomes available to your users. That capability is rolling out rather than universally switched on, and it is not one-click consumer-Copilot parity. If you want the fastest possible route today, the same connector address works one-click in Claude or ChatGPT; if you are standardised on Microsoft's stack, the agent path below is how you get there.

The connector itself is issued on the MCP server page, which handles the Google sign-in once for every client rather than repeating it here. Return with something ending in /mcp and the rest of this page is Copilot alone.

1. Get your connector address. Sign in with Google, pick the accounts the connector is allowed to reach, and take the private address it hands back. This part is identical whichever assistant you are wiring up, so it is written out once on the MCP server page. The address ends in /mcp and it is the credential, so treat it like a password.
2. Register it as an MCP tool inside Copilot Studio. In Copilot Studio, create or open an agent and add a tool of type Model Context Protocol, giving it the server URL you just copied. This is the route by which an MCP server reaches Copilot — through an agent you build, not through a box in consumer Copilot's settings. There is no client ID or secret to supply; the key inside the URL is what authenticates.
3. Publish the agent and ask what it can see. Publish the agent to the channel you want it in — Microsoft 365 Copilot, Teams, or a custom surface — then open it and ask which advertising accounts are visible. What comes back should match the accounts your Google login can already open.

https://mcp.adcopilot.cloud/c/<your key>/mcp

The Copilot Studio path

Copilot Studio is where the connection actually lives. You create an agent — a named assistant with its own instructions and tools — and add the AdCopilot connector to it as an MCP tool, pointing at the address you copied. From that point the agent can call the Google Ads API through the connector exactly as Claude or ChatGPT would, and the reasoning happens in Copilot on your own tenant.

• It is an agent, not a settings toggle.The consumer Copilot box is not where an arbitrary remote MCP server goes. The tool is attached to an agent you build, which is more setup than the one-click clients but is also where the tenant's governance and publishing controls sit.
• MCP support is rolling out. Microsoft has been shipping MCP tool support into Copilot Studio progressively. If the option to add a Model Context Protocol tool is not present, that is the rollout or a tenant policy rather than a fault with the connector — and the same address works today in the one-click clients.
• Publishing is a separate step. Building the agent makes it exist; publishing it to a channel makes it usable. Until you publish, an agent that is otherwise wired up correctly will not appear where your users expect it.

The same address works in any MCP client that speaks streamable HTTP — Gemini CLI, Cursor, OpenCode and the rest are on the other clients page — and the full breakdown of what the connector exposes is on the MCP server page.

Microsoft 365 Copilot agents

Once the agent is published, Microsoft 365 Copilot is where people use it. An agent you built in Copilot Studio and gave the Google Ads connector becomes available in the surfaces your tenant allows — Microsoft 365 Copilot, Teams, or a custom channel — and a user talks to it the way they would any Copilot agent, asking about the account and, on the write-capable tier, instructing changes.

Because this all sits inside your Microsoft tenant, the controls do too. Whether members can build agents, add MCP tools, and publish them is generally governed by admin policy, so on a work account “there is no option” is more often a decision someone made than a bug. The person to ask is whoever administers the tenant. On the connector side, nothing changes: the address is the same one Claude and ChatGPT use one-click.

Your first questions

Start with something you can check yourself:

• “Which Google Ads accounts can you see?”
• “Summarise last month's spend and conversions by campaign.”
• “Find search terms from the last 90 days with spend above £50 and no conversions.”
• “Which campaigns are budget-limited?”
• “What changed in this account last week?”

Every one of those needs nothing but reading, so each works on either tier. It is worth spending a week on questions before instructions: you find out how the account really looks before you ask for anything to change.

What Copilot can and cannot change

On the full tier, which is what the pilot runs on, the connector carries thirty-two tools — campaigns including Performance Max, ad groups, responsive search ads, keywords and negative keywords, the full asset set and their links, plus geography, ad schedule and device bid adjustments. On the read-only tier it has three, none of which alters anything. Each of them is listed, with what it actually does, on the MCP server page.

It never has the four destructive tools. Those are filtered out before the model sees the tool list, so “remove” is not a thing it can attempt — and a removed mutate is refused at the server regardless — which also means a prompt injected into some page it read cannot talk it into one. Whether that fence is enough, and what else stands behind it, is the whole of the security page.

Access comes back three ways, none of which we have to agree to: revoke AdCopilot on your Google account's third-party access page, remove the tool from the agent inside Copilot Studio, or ask us to kill the address. The security page covers what each one does and how quickly.

If it seems not to work

Below are the ones peculiar to Copilot. Everything generic — a mistyped address, a truncated key, the wrong Google login, the read-only tier — sits on the MCP server page instead, since it behaves identically wherever you connect from.

• No option to add an MCP tool. Either MCP support has not reached your Copilot Studio yet as it rolls out, or a tenant administrator has decided the question. Both are covered above, and the same address works one-click in Claude or ChatGPT in the meantime.
• The agent is built but nobody can find it.Building an agent is not the same as publishing it. Publish it to the channel you want — Microsoft 365 Copilot or Teams — and check the tenant allows that surface.
• It answers without using the connector. Phrase the request so the connector is the only sensible route: name it, and ask for figures rather than views. A reply containing nothing you could trace back to a row in the account is usually a reply that never made the call.
• It works for you and not a colleague. Google access is per person: the connector reads what the signed-in Google login reaches, which is the point, and is set out on the team access page.

Frequently asked questions