Connect Google Ads to Microsoft Copilot via MCP

Google Ads in Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Short answer: install the Google Ads connector on AnythingMCP with an OAuth client from your Google Cloud project, authorize it once, then add AnythingMCP to a Copilot Studio agent as an MCP tool (Tools → Add a tool → New tool → Model Context Protocol, URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID). Copilot can then read your campaigns, search terms, keywords, budgets, conversions and change history, and answer with your real numbers. It cannot change anything in the account.

Copilot has no built-in Google Ads connector. A remote MCP server in between is what makes it work.

Set it up

Step 1: Google Cloud project and OAuth client

1. In console.cloud.google.com, enable Google Ads API for a project and check its access level on the Google Ads API page. You need Explorer access or higher to read real accounts; a new project starts at Test access. No developer token is needed since September 2026.
2. Set the OAuth consent screen to Internal (Google Workspace) or External and In production.
3. Create an OAuth client ID of type Web application with the redirect URI https://cloud.anythingmcp.com/api/mcp-oauth/callback.

The details, including what each access level allows: Google Ads API access without a developer token.

Step 2: Install Google Ads on AnythingMCP

1. Create a workspace on AnythingMCP Cloud (7 days free) or use your self-hosted AnythingMCP.
2. In Marketplace, open Google Ads, click Install and paste the client ID and secret.
3. On the connector page click Authorize with Provider and sign in with a Google user that can see your ad accounts. A user with the Read only role in Google Ads is enough.

Step 3: Add AnythingMCP to Microsoft Copilot

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
5. Try it in the agent's Test pane: ask for something that needs the Google Ads tools.
6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Step 4: Ask

Start a new chat and ask about your account, for example "how did my Google Ads do last month?". Copilot lists your accounts, picks the right one and calls the report tools on its own.

What happens when you ask

We asked Claude, in claude.ai, how our own account did in the last 30 days. It called six tools, found that one of two accounts with the same name had been idle all year, reported spend, conversions and cost per conversion for the other, and then went further: the daily numbers showed two bursts of one-cent clicks producing most of the month's conversions, and Claude suggested checking the sign-up conversion before trusting the campaign's optimization. The step-by-step version: Google Ads audit with Claude.

Prompts to try in Copilot

• "Compare my Google Ads spend, conversions and cost per conversion this month with last month, by campaign."
• "Find search terms that cost more than €20 in the last 30 days without a conversion, and propose negative keywords."
• "Which keywords have a Quality Score below 5, and is the problem expected CTR, ad relevance or landing page?"
• "Is any campaign limited by budget? Show lost impression share to budget and to rank."
• "Which ads are disapproved or have poor ad strength?"
• "What changed in the account in the last 7 days, and who made the changes?"

Good to know

• Copilot reads money in micros from the API and converts it; the connector tells it to name the account currency.
• Today's data is partial, and conversions keep arriving for days. Ask for "the last 30 full days ending yesterday" for stable numbers.
• The OAuth client and the refresh token stay on the AnythingMCP server, encrypted. People on your team connect with their own login and never see them.

Every tool and limit in detail: Google Ads MCP server overview.

FAQ

Can Copilot pause campaigns or change bids? No. The connector only has read tools.

I manage clients through an MCC. Does that work? Yes. Put the manager's 10-digit id in GOOGLE_ADS_LOGIN_CUSTOMER_ID and ask Copilot to list the client accounts first.

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Related

• Google Ads MCP server: the overview
• Google Ads audit with Claude
• Google Ads API access without a developer token
• Connect Google Ads to Claude
• Connect Google Ads to ChatGPT
• Connect Google Ads to Cursor
• Connect Google Ads to Gemini
• Connect Google Ads to Meta Muse
• Connect Google Search Console to Microsoft Copilot
• Google Ads in the marketplace