To connect Google Ads to Claude, you need to add an MCP server to Claude using a custom connector. The fastest way to do this is through Adsroid MCP, which gives Claude live access to your Google Ads account via a single endpoint: mcp.adsroid.com/mcp. The setup takes under two minutes and requires no developer environment or config files.

This guide walks through the exact steps for both Claude.ai (web) and Claude Desktop, from creating your Adsroid account to running your first Google Ads prompt inside Claude.

What Is MCP and Why Does It Matter for Google Ads?

Model Context Protocol (MCP) is an open standard that allows AI assistants to connect to external tools and data sources. Instead of copy-pasting reports into a chat window, MCP gives Claude actual tool access: it can call an API, read live data, and in some cases take actions on your behalf.

For Google Ads, this means Claude can pull real campaign data, analyze performance, adjust bids, modify budgets, create new campaigns, and more, without you exporting a spreadsheet or writing a single line of code.

The important distinction here is that not all MCP servers for Google Ads are equal. The official Google Ads MCP server, for example, is read-only. It can analyze data but cannot create campaigns, change budgets, or modify any live settings. If you want write access through Claude, you need a third-party MCP server that supports those actions.

What Is Adsroid MCP?

Adsroid MCP is the Model Context Protocol server built by Adsroid. It is not a standalone product. It is one of several ways to access the Adsroid platform, alongside the Adsroid web app, Slack, Copilot, and the Adsroid REST API.

When you connect Adsroid MCP to Claude, the AI assistant gets access to more than 140 tools across Google Ads, Meta Ads, Google Search Console, Google Analytics 4, and Ad Radar (a competitor ad monitoring tool). The tool set covers four action types: Analyze, Manage, Create, and Test.

One feature worth highlighting before you start: every Adsroid project includes a Business Context layer. This is a dedicated tool that loads your business identity, your offer, target audience, positioning, and customer pain points, before Claude acts. It means that when you ask Claude to write ad copy or suggest a campaign structure, it works from your actual business context, not generic templates.

For agencies, Adsroid MCP supports multi-account use. A single API key gives access to every client project in your organization, with full data isolation between projects.

Before You Start: What You Need

• A Claude Pro or Claude Team account (custom connectors require a paid plan on Claude.ai)
• An Adsroid account (free to create at app.adsroid.com/register)
• A Google Ads account connected to your Adsroid project
• Your Adsroid API key

If you also want Claude to access Meta Ads in the same session, you connect Meta through the same Adsroid project. The same MCP endpoint handles everything.

Step 1: Create an Adsroid Account and Connect Google Ads

Go to app.adsroid.com and create an account if you do not have one. Once inside, create a new project and give it a name that matches the client or business you are working on.

Inside the project, navigate to the integrations section and connect your Google Ads account. This uses standard OAuth, so you will be redirected to Google to authorize access. No credentials are stored on Adsroid servers. The connection is live and resolves in real time each time Claude calls a tool.

If you want to also connect Meta Ads, Google Search Console, or Google Analytics 4, you can do that from the same integrations screen. Everything connected here will be accessible to Claude once the MCP server is added.

At this point, also fill in the Business Context section of your project. This is the information Claude will automatically load before making recommendations or generating content. The more accurate and specific it is, the more useful Claude’s responses will be.

Step 2: Get Your Adsroid API Key

In your Adsroid account settings, find the API section and generate an API key. Copy it and keep it somewhere safe for the next step.

This key identifies your organization and gives access to every project within it. If you are an agency, you can use the same key across multiple Claude conversations while keeping each client’s data fully isolated at the project level.

Step 3: Add the Adsroid MCP Server to Claude.ai (Web)

This is the main setup step for most users who work in the Claude.ai browser interface.

1. Open Claude.ai and sign in to your account.
2. Click on your profile icon or account menu, then navigate to Settings.
3. Find the Integrations or Connectors section. The exact label depends on your Claude plan and interface version.
4. Click Add custom connector or Add MCP server.
5. Enter the Adsroid MCP endpoint URL: https://mcp.adsroid.com/mcp
6. When prompted for authentication, enter your Adsroid API key.
7. Save the connector.

Claude will verify the connection and load the available tools from the Adsroid MCP server. You should see the tool count appear in the connector details once it connects successfully.

Claude.ai’s custom connector setup uses OAuth-style authentication, so the process is a few clicks rather than editing configuration files manually. If the connection fails, double-check that you copied the API key without trailing spaces.

Step 4: Add the Adsroid MCP Server to Claude Desktop

If you use the Claude Desktop application rather than the browser interface, the process is slightly different because Claude Desktop uses a local configuration file to register MCP servers.

Locating the Configuration File

On macOS, the Claude Desktop config file is located at:

~/Library/Application Support/Claude/claude_desktop_config.json

On Windows, it is typically at:

%APPDATA%Claudeclaude_desktop_config.json

Editing the Configuration

Open the file in any text editor. If it does not exist yet, create it. Add or update the mcpServers section to include the Adsroid endpoint:

{
  "mcpServers": {
    "adsroid": {
      "url": "https://mcp.adsroid.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ADSROID_API_KEY"
      }
    }
  }
}

Replace YOUR_ADSROID_API_KEY with the key you copied in Step 2. Save the file and restart Claude Desktop. The Adsroid tools will appear as available in the tool panel on the left side of the interface.

Verifying the Connection in Claude Desktop

After restarting, look for the tool icon or hammer icon in the Claude Desktop interface. Click it to see the list of available MCP tools. If the Adsroid connection is working, you will see the full list of available tools, organized by platform and action type.

Step 5: Run Your First Google Ads Prompt in Claude

With the MCP server connected, start a new conversation in Claude and select the Adsroid connector or make sure the tools are enabled for the session.

Here are some useful first prompts to verify the connection is working and get familiar with what Claude can do:

Check Account Access

Start simple: ask Claude to list the Google Ads campaigns in your account. This confirms the connection is live and that the right account is loaded.

Example: