AdWhiz
Grok

Google Ads MCP for Grok

AdWhiz is a hosted MCP server, which is what Grok's custom connector expects: a public HTTPS URL over Streamable HTTP. Add it once and Grok can read and change your Google Ads and Meta Ads accounts.

Get MCP Access

How to Set Up AdWhiz in Grok

  1. Generate an AdWhiz API key

    Sign up at adwhiz.ai, connect an ad account, then open Settings and create an API key. Grok authenticates with a static bearer token rather than a browser sign-in, so you do need a key for this one.

  2. Add a custom connector in Grok

    In the Grok app, open the connectors page, choose to add a connector, pick the custom option and paste the AdWhiz MCP URL. AdWhiz is already on the public internet, so no tunnelling service is involved.

    https://mcp.adwhiz.ai/mcp

  3. Supply the API key as an Authorization header

    Grok sends the token you provide on the Authorization header of every request to the MCP server. Use your AdWhiz key with the Bearer prefix. If you are calling the xAI API directly instead of using the Grok app, this is the authorization field on the remote MCP tool.

    Authorization: Bearer aw_live_your-api-key-here

  4. Ask Grok about your ad accounts

    Grok reads the AdWhiz tool list on connect. Begin with a question that only reads data, so you can confirm the account is wired up before granting anything write access.

    # Example Grok prompts:
# "List my Google Ads campaigns and their 30-day spend"
# "Find search terms with spend but no conversions"
# "Show me which ad groups are below first-page bid estimates"

AdWhiz works with any MCP-compatible AI coding tool.

Works with leading AI platforms and tools

OpenAI logoOpenAI
Gemini logoGemini
Claude Code logoClaude Code
Cursor logoCursor
Windsurf logoWindsurf
Continue.dev logoContinue.dev
Cline logoCline
Zed logoZed
OpenClaw logoOpenClaw

What You Can Do with AdWhiz in Grok

  • Works from the Grok app connectors page and from the xAI API remote MCP tool
  • Streamable HTTP over public HTTPS — the transport Grok's custom connector expects
  • Static bearer token auth, so no OAuth round trip is required
  • No tunnelling service needed — AdWhiz is hosted, not a localhost server
  • Google Ads and Meta Ads reachable through the same connector
  • Account audits, wasted spend analysis and search term reports
  • Keyword, negative keyword and bid management
  • Campaign creation, budgets and bidding strategies
  • Dry-run mode to preview API calls before they execute
  • Mutation audit log — every write is attributed and recorded

AdWhiz + Grok: Common Questions

No. Tunnelling is for MCP servers running on localhost or a private network. AdWhiz is hosted at a public HTTPS address, so you paste the URL directly.

Use an API key. AdWhiz supports both, but the xAI API's remote MCP tool authenticates only with a static token set on the Authorization header, so a key is the option that works on both Grok surfaces.

Not with AdWhiz. Grok accepts either SSE or Streamable HTTP, but AdWhiz only serves Streamable HTTP. Choose that one.

The connector is set up once in the Grok app and applies to your chats. The remote MCP tool is something you pass per request when you call the xAI API in your own code. AdWhiz works with both, and both use the same URL and key.

Yes — scope it at the AdWhiz end by only connecting the ad accounts you want reachable. Dry-run mode lets you inspect calls first, and the mutation audit log records every write.

Start Managing Google Ads from Grok

Get MCP access and connect your Google Ads account to Grok in under 5 minutes.

Leave your email and our team will help you set up and troubleshoot.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.