MCP Quick Start

Get connected in under 5 minutes

Connect your AI tool (Claude Code, Cursor, Windsurf, or others) to AdWhiz in under 5 minutes. Includes config snippets for every supported client.

Before you start#

Make sure you have these three things ready before setting up MCP:

  • **An AdWhiz subscription** — you need an active Pro, Business, or Enterprise plan. MCP tools are not available on the free tier. See Subscription Plans if you need to sign up.
  • **An AI tool that supports MCP** — such as Claude Code, Cursor, Windsurf, OpenClaw, or any other MCP-compatible client.
  • **Your Google Ads or Meta Ads account connected to AdWhiz** — you must have at least one ad platform connected in your AdWhiz dashboard before MCP can access it.

This is the easiest way to connect. Your AI tool opens a browser window, you sign in with your Google account, and you're done. There are no API keys to copy or paste. This method uses OAuth 2.0 with PKCE for maximum security.

1

Open your AI tool's MCP settings

Every AI tool has a place where you configure MCP servers. In Claude Code, it's a terminal command. In Cursor and Windsurf, it's a JSON config file. We'll show the exact config for each tool below.

2

Add AdWhiz as an MCP server

Add the AdWhiz MCP server URL to your tool's configuration. The URL is: https://mcp.adwhiz.ai

3

Sign in with Google when prompted

When you use an AdWhiz tool for the first time, a browser window will open asking you to sign in with Google. Choose the same Google account you use for AdWhiz, and click "Allow".

4

You're connected!

That's it. Your AI tool is now connected to your ad accounts through AdWhiz. Try asking it: "List my Google Ads campaigns" to make sure everything works.

For Claude Code, the fastest way is a single terminal command:

Terminal
claude mcp add adwhiz -- npx adwhiz-mcp-client@latest

Or, if you prefer to configure it manually with a JSON file:

~/.claude/mcp.json
{
  "mcpServers": {
    "adwhiz": {
      "command": "npx",
      "args": ["adwhiz-mcp-client@latest"],
      "env": {}
    }
  }
}

When you run your first AdWhiz command, a browser window will open for you to sign in with Google. After that, the session is cached and you won't need to sign in again for 30 days.

Option 2: API Key#

If browser sign-in doesn't work in your environment (for example, on a remote server or in a CI pipeline), you can use an API key instead. The API key authenticates you directly without needing a browser.

1

Go to Dashboard > Integrations

In your AdWhiz dashboard, go to Settings → Integrations. This page shows all available API connections and your MCP server credentials.

2

Click "Create API Key"

Click the button to generate a new API key. Give it a name so you can remember what it's for (e.g., "Cursor on MacBook" or "CI server").

3

Copy the key

Click 'Generate API Key'. A new key starting with aw_ will appear. Copy it immediately — for security, AdWhiz only shows the full key once. Store it somewhere safe.

4

Add it to your AI tool's MCP configuration

Put the API key in your tool's MCP config as a Bearer token in the Authorization header. See the examples below for each tool.

Here's the generic JSON config with an API key:

MCP config (generic)
{
  "mcpServers": {
    "adwhiz": {
      "url": "https://mcp.adwhiz.ai/sse",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY_HERE"
      }
    }
  }
}

Configuration for each AI tool#

Below are the exact configuration files for the most popular AI tools. Pick the one you use.

Claude Code#

The quickest way is the one-line install command:

Terminal
claude mcp add adwhiz -- npx adwhiz-mcp-client@latest

This sets up browser-based OAuth automatically. If you prefer API key auth, edit your Claude MCP config:

~/.claude/mcp.json
{
  "mcpServers": {
    "adwhiz": {
      "url": "https://mcp.adwhiz.ai/sse",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY_HERE"
      }
    }
  }
}

Cursor#

Create or edit the MCP config file in your project root. Cursor reads this file automatically when the project opens:

.cursor/mcp.json
{
  "mcpServers": {
    "adwhiz": {
      "command": "npx",
      "args": ["adwhiz-mcp-client@latest"]
    }
  }
}

To use an API key instead of browser sign-in:

.cursor/mcp.json
{
  "mcpServers": {
    "adwhiz": {
      "url": "https://mcp.adwhiz.ai/sse",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY_HERE"
      }
    }
  }
}

Windsurf#

Windsurf reads MCP config from a global config file in your home directory:

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "adwhiz": {
      "command": "npx",
      "args": ["adwhiz-mcp-client@latest"]
    }
  }
}

To use an API key instead of browser sign-in:

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "adwhiz": {
      "url": "https://mcp.adwhiz.ai/sse",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY_HERE"
      }
    }
  }
}

OpenClaw#

OpenClaw is the simplest option — one command installs and configures everything:

Terminal
clawhub install adwhiz

After running this command, AdWhiz is automatically available in every MCP-compatible AI tool on your machine. A browser window will open for sign-in the first time you use it.

💡

Verify your connection

After connecting, try asking your AI tool: "List my Google Ads campaigns." If you see a list of your campaigns, everything is working! If you see an error, double-check your API key or try the browser sign-in method instead.

⚠️

Keep your API key secret

Your API key gives access to your ad accounts. Never share it in public code repositories, chat messages, or screenshots. If you accidentally leak your key, go to Dashboard > Integrations immediately and delete it, then create a new one.

Troubleshooting#

Browser sign-in window doesn't appear#

Make sure your browser allows pop-ups for mcp.adwhiz.ai. Some browsers block pop-ups by default. You can also try opening https://mcp.adwhiz.ai in your browser manually to check if the server is reachable.

"Unauthorized" error with API key#

Double-check that you copied the full API key (it starts with "aw_"). Make sure there are no extra spaces before or after the key in your config file. Also confirm that your subscription is active — API keys only work with an active Pro, Business, or Enterprise plan.

"No ad accounts found" error#

This means your AdWhiz account doesn't have any ad platforms connected yet. Sign in to adwhiz.ai/app and connect your Google Ads or Meta Ads account first. Once connected, try your MCP tool again.

Still stuck?#

Email us at support@adwhiz.ai with a description of the error and which AI tool you're using. We'll help you get connected.