How to Connect Google Ads to Meta Muse: Custom Connector in 15 Minutes

Google Ads in Muse

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 Muse as a custom connector (Settings → Connectors → Add custom connector, URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID). Muse 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.

Muse 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 Muse

Muse adds remote MCP servers as custom connectors and signs in to them with OAuth.

1. In Muse, open Settings → Connectors and choose Add custom connector.
2. Paste the MCP server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.
3. Muse opens the AnythingMCP sign-in page: sign in and approve access.
4. In a chat, ask Muse for something that needs the Google Ads tools.

You can also set it up from a chat, on the web, in the iOS and Android apps or in WhatsApp. Send Muse this message:

Create a Custom Connector for a new remote MCP server, then connect to it:
Name: AnythingMCP
Transport: remote streamable HTTP
URL: https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID
Auth: OAuth

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Muse connects from Meta'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?". Muse 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 Muse

• "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

• Muse 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 Muse 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 Muse to list the client accounts first.

Where is Muse available? Meta currently offers Muse in the US and Canada, on the web, in the iOS and Android apps and in WhatsApp.

Does Meta review this connector? No. Meta doesn't review custom connectors. Muse sees only the tools you switched on for this MCP server in AnythingMCP, and you can disconnect it anytime under Settings → Connectors.

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 Search Console to Meta Muse
• Google Ads in the marketplace