AdWhiz
Hermes

Google Ads MCP for Hermes

Hermes is the open agent from Nous Research. AdWhiz plugs into it as a remote MCP server, so a Hermes run can audit spend, pull search terms and change campaigns in your own Google Ads and Meta Ads accounts.

Get MCP Access

How to Set Up AdWhiz in Hermes

  1. Create your AdWhiz account and connect an ad account

    Sign up at adwhiz.ai and link the Google Ads or Meta Ads accounts you want Hermes to reach. You do not need an API key for this integration — Hermes authenticates through your browser instead.

  2. Add AdWhiz to your Hermes config

    Hermes reads remote MCP servers from the mcp_servers block of its config file. AdWhiz is hosted, so the URL is all it needs. Setting auth to oauth turns on the browser sign-in flow.

    mcp_servers:
  adwhiz:
    url: https://mcp.adwhiz.ai/mcp
    auth: oauth

  3. Approve the connection once in your browser

    On first use Hermes opens an AdWhiz consent page. Because AdWhiz publishes a Dynamic Client Registration endpoint, Hermes registers itself automatically — there is no client ID or client secret to create or paste. Approve the scopes and the token refreshes on its own from then on.

  4. Ask Hermes to work on your account

    Hermes discovers the AdWhiz tool list at connection time and calls what it needs. Start with a read-only question so you can see the account data flowing before you let it write anything.

    # Example Hermes prompts:
# "Audit my Google Ads account and list the top 5 waste areas"
# "Which search terms spent over $50 last month with zero conversions?"
# "Pause every ad group whose CPA is above $150"

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 Hermes

  • OAuth 2.1 with PKCE — no API key stored in your Hermes config file
  • Dynamic Client Registration — Hermes registers itself, nothing to pre-provision
  • Refresh tokens, so a long-running Hermes deployment does not need re-authorising
  • Streamable HTTP transport — hosted, with no local process to supervise
  • Google Ads and Meta Ads reachable through the same connection
  • Search term reports and negative keyword discovery
  • Budget, bidding strategy and campaign status changes
  • Conversion action setup and tracking validation
  • Dry-run mode so an autonomous run can be inspected before it writes
  • Mutation audit log — every write is attributed and recorded

AdWhiz + Hermes: Common Questions

No. Hermes identifies itself with a Client ID Metadata Document where a server supports one, and falls back to Dynamic Client Registration where it does not. AdWhiz exposes a registration endpoint, so Hermes takes the second path automatically and no client ID or secret is ever created by hand.

Nous Research. This page is about the open agent project, not the parcel carrier and not the fashion house that share the name.

You can — AdWhiz accepts an aw_live_ key as a bearer token on the same endpoint. OAuth is still the better choice here because the credential never sits in a config file and it refreshes without you.

Streamable HTTP only. There is no SSE endpoint and no stdio option, because AdWhiz runs on our servers rather than on your machine.

That depends on how you run it. Hermes can be configured to approve tool calls automatically, so treat write access the way you would treat any other credential you hand an autonomous agent. Dry-run mode and the mutation audit log exist for exactly this reason.

Start Managing Google Ads from Hermes

Get MCP access and connect your Google Ads account to Hermes 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.