By Ira Bodnar, Ryze AI · Updated · Connector tested November 13, 2026
Quick answer
The main way to connect Hermes Agent to Google Ads is the Ryze AI connector. Link Google Ads once in a Ryze AI workspace with your Google login, add a ryze entry with the URL https://connector.get-ryze.ai/mcp and auth: oauth under mcp_servers in ~/.hermes/config.yaml, then run hermes mcp login ryze and click Allow connection. Start a new session and ask for a Google Ads report.
- In Ryze AI open Integrations, find Google Ads and click Connect with your Google login
- Add the ryze entry to the mcp_servers block of ~/.hermes/config.yaml
- Run hermes mcp login ryze and click Allow connection on the Ryze AI page
- Start a new session or run /reload-mcp, then ask your first Google Ads question
Hermes Agent to Google Ads at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, a remote HTTP MCP server that Hermes Agent reads from one ryze entry under mcp_servers in ~/.hermes/config.yaml |
| Connector address | https://connector.get-ryze.ai/mcp, identical for every user |
| How Hermes Agent signs in | OAuth with auth: oauth, completed once with hermes mcp login ryze. A Ryze AI API key sent as a bearer header from ~/.hermes/.env is the alternative |
| Google Ads tools | 16 in total: 8 that read, 7 that write and 1 that deletes |
| Changes to the account | Possible when the connected Google user has Standard or Admin access. Setting trust: untrusted on the ryze entry makes Hermes Agent ask before write-capable calls |
| Other data in the same chat | Any other Ryze AI platform connected in the workspace, such as Meta Ads, GA4 or Search Console, is available at the same address. This guide covers Google Ads |
| Hermes Agent plan | None. Hermes Agent is open source under the MIT license per its GitHub repository and runs on your own machine or server |
| Ryze AI price | Paid Ads costs $89 per month after a 7-day free trial. Adding the connector costs nothing |
| Google's own option | google-ads-mcp, open source, which you run yourself. 7 tools: GAQL reports plus asset, video and label changes. Google's guide does not name Hermes Agent |
| Google sign-in scope | One Google Ads scope covers reading and changing. The user's access level inside Google Ads decides which of the two works |
| Last tested | Connector calls on November 13, 2026. The steps inside Hermes Agent were not run |
Before you start
- Hermes Agent installed. It is open source from Nous Research, licensed MIT per its GitHub repository, and self-hosted, so there is no plan tier to buy. MCP support ships with the standard install and the configuration lives in ~/.hermes/config.yaml.
- A Google login with access to your Google Ads accounts. Standard or admin access is needed to allow changes. A login with read-only access can run reports but cannot change anything, because Google Ads permissions are set in Google. Agencies connect the manager (MCC) login once.
- A Ryze AI workspace on a plan or free trial. Paid Ads is $89 per month with a 7-day free trial; Agency is $279 per month. Connecting the connector is free, but the Google Ads tools need an active plan or trial.
How to connect Hermes Agent to Google Ads with OAuth
Two steps happen in Ryze AI and Google, the rest in Hermes Agent. The connector URL is the same for every user.
Connect Google Ads in Ryze AI
Create a Ryze AI account or sign in, open Integrations in the left sidebar and find Google Ads under Advertising. Click Connect, sign in to Google with the login that has access to your ad accounts and approve access with every requested permission checked.
Check the connection
Back in Ryze AI the Google Ads card shows Connected. There is no account to pick: Ryze AI sees every Google Ads account that login can reach. To choose the accounts the agent works with first, click View on the card and use Agent default accounts.
Add the ryze entry to config.yaml
Open ~/.hermes/config.yaml and add a ryze server under mcp_servers. Do this with Hermes Agent closed, or add the entry and then run the login in the next step, because a running session reloads MCP with a 30-second timeout, which is too short for a browser sign-in.
mcp_servers: ryze: url: "https://connector.get-ryze.ai/mcp" auth: oauthSign in to the connector
Run hermes mcp login ryze. Hermes Agent prints an authorize URL and opens your browser when it can. Sign in on the Ryze AI page and click Allow connection. Hermes Agent caches the tokens at ~/.hermes/mcp-tokens/ryze.json and reuses them until a refresh fails.
Load the tools
Start a new session, or run /reload-mcp inside a running one. Hermes Agent lists the server's tools and registers each one with the prefix mcp_<server>_<tool>. To see what the server answers, run hermes mcp test ryze.
Ask your first question
Ask: Use GAQL to list my Google Ads campaigns with cost, conversions and conversion value for the last 30 days, ordered by cost.
The Ryze AI help article for Google Ads covers the Google side of the connection, and the Ryze AI help article on API keys and the MCP endpoint covers the connector URL.
Source for the Hermes Agent steps: Hermes Agent MCP documentation, opened November 16, 2026.
API key, tool filters and headless hosts
Hermes Agent keeps every MCP server in one file, ~/.hermes/config.yaml. These are the variations that matter for this connector.
A Ryze AI API key instead of OAuth
Create a key in Ryze AI under Workspace Settings > Profile > API keys > Create key and copy it, because it is shown once. Put RYZE_API_KEY with the rk_live_ key in ~/.hermes/.env and reference it in the header, since Hermes Agent substitutes ${VAR} placeholders in headers from the environment, which includes that file. Run /reload-mcp afterwards. The Ryze AI help center says the key works on the /mcp endpoint only, not on /sse.
mcp_servers:
ryze:
url: "https://connector.get-ryze.ai/mcp"
headers:
Authorization: "Bearer ${RYZE_API_KEY}"Show Hermes Agent only the read tools
Each server entry accepts tools.include and tools.exclude, and both take exact tool names or glob patterns. This entry registers the 8 Google Ads read tools and nothing else from the connector, which also hides the tools of every other platform in the workspace. It hides tools from Hermes Agent only. For a hard read-only guarantee, connect a Google login that has read-only access.
mcp_servers:
ryze:
url: "https://connector.get-ryze.ai/mcp"
auth: oauth
tools:
include:
- google_ads__getAccountSummary
- google_ads__getAccountHierarchy
- google_ads__listAccessibleCustomers
- google_ads__listConversionActions
- google_ads__listRecommendations
- google_ads__runRawGaql
- google_ads__generateKeywordIdeas
- google_ads__generateKeywordHistoricalMetricsA remote or headless host
When Hermes Agent runs on a server and your browser is on another machine, the local callback cannot reach the browser. The Hermes Agent documentation lists these ways around it: paste the redirect URL back at the prompt that hermes mcp login prints, forward the callback port over SSH, or complete the sign-in from the Hermes Desktop app. A device-code flow (hermes mcp login ryze --flow device) works only when the authorization server advertises a device endpoint, and this guide did not check whether the Ryze AI connector does.
hermes mcp login ryzeThe messaging gateway and unattended runs
A running gateway (hermes gateway run) never opens a browser, so sign in with hermes mcp login ryze first. The gateway picks up a new mcp_servers entry within about a minute. When a refresh token dies, the documentation says the server is parked with a warning in gateway.log until you log in again.
Reloading and timeouts
The Hermes Agent pages read for this guide give no default for the tool-call timeout. A GAQL query that Google does not finish within 150 seconds comes back as a timeout, according to the connector's tool description. If long reports are cut short on the Hermes Agent side, set timeout on the ryze entry above 150. connect_timeout bounds the first connection, and oauth.timeout lets the browser sign-in run longer than the 5 minutes the documentation mentions.
mcp_servers:
ryze:
url: "https://connector.get-ryze.ai/mcp"
auth: oauth
timeout: 180
connect_timeout: 60Hermes Agent and MCP: the facts in one table
| Topic | What the Hermes Agent documentation says |
|---|---|
| Where servers are added | ~/.hermes/config.yaml under mcp_servers, or with hermes mcp install for the catalog of Nous-approved servers. The catalog entries are stored in the hermes-agent repository; this guide found no Google Ads entry named in the documentation |
| Transports | Local stdio servers (command and args) and remote HTTP servers (url). transport: sse selects the legacy SSE transport for a server that speaks only SSE |
| Sign-in | auth: oauth does discovery, PKCE, token exchange and refresh. Hermes Agent tries a Client ID Metadata Document first and falls back to dynamic client registration. Static bearer headers also work |
| Token storage | ~/.hermes/mcp-tokens/<server>.json, written with 0600 permissions and reused until refresh fails |
| Tool names | mcp_<server_name>_<tool_name>, so a server named ryze registers its tools under names that start with mcp_ryze_ |
| Approval | A server entry can set trust: untrusted so that write-capable calls ask first. Tools annotated readOnlyHint stay unprompted. /yolo, --yolo and approvals.mode: off skip that prompt |
| Filtering | tools.include and tools.exclude per server, with glob support. include wins when both are set. enabled: false skips a server |
| Reload | /reload-mcp, or a new session. The CLI also reloads when config.yaml changes in a running session, with a 30-second timeout |
| Proxies | HTTP servers honor HTTPS_PROXY, HTTP_PROXY, ALL_PROXY and NO_PROXY |
| Plan | None. Open source, self-hosted |
Sources: Hermes Agent MCP documentation, NousResearch/hermes-agent on GitHub. Opened November 16, 2026.
Other clients
The same URL works in other MCP clients. Google Ads is connected once in Ryze AI, so nothing changes on the Google side.
Claude Code
Run claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp, then claude mcp login ryze. Add --scope user to make the server available in every project. Hermes Agent can also import an existing Claude Code mcpServers block with hermes import-agent claude-code, according to its documentation.
Claude and ChatGPT
In Claude open Customize > Connectors, choose Add custom connector and enter https://connector.get-ryze.ai/mcp. In ChatGPT the full custom MCP flow is for Business and Enterprise/Edu plans, and Pro users get read and fetch permissions only. The Ryze AI help center has the exact screens for both.
Codex and Cursor
Codex takes codex mcp add ryze --url https://connector.get-ryze.ai/mcp followed by codex mcp login ryze. Cursor reads the same URL from its mcp.json file. Google Ads is linked once in Ryze AI, so the Google side does not change from client to client.
Google Ads permissions and Hermes settings
Two sides decide what Hermes Agent can reach in Google Ads: the Google login you connect in Ryze AI, and the settings on the ryze entry in Hermes Agent. The Ryze AI connector uses no API key, developer token or Google Cloud project of your own by default.
- The Google login
- Signs in with OAuth. It needs access to at least one Google Ads account, and standard or admin access to allow changes. Every request runs with that login's rights.
- Which accounts
- Every Google Ads account the login can reach, including client accounts under a manager (MCC) login that was connected. Agent default accounts picks the ones the agent works with first.
- The Ryze AI sign-in from Hermes Agent
- hermes mcp login ryze, or an API key in a bearer header. Both reach the same workspace tools. The OAuth screen lets you choose which workspaces the client can use.
- The Hermes Agent settings
- trust, tools.include and tools.exclude on the ryze entry decide which tools Hermes Agent sees and when it asks first. They are client-side settings and do not change what the Google login may do.
The 4 Google OAuth scopes of the connection
When you link Google Ads in Ryze AI, the Google sign-in asks for four OAuth scopes. The scope names come from the Ryze AI Google Ads facts. The descriptions are Google's wording on its OAuth 2.0 scopes page, opened November 14, 2026.
| Scope | Google's description |
|---|---|
| https://www.googleapis.com/auth/adwords | See, edit, create, and delete your Google Ads accounts and data. |
| openid | Associate you with your personal info on Google |
| See your primary Google Account email address | |
| profile | See your personal info, including any personal info you've made publicly available |
Who can read and who can change
Google Ads has one OAuth scope for reading and writing. Google's access model page says the API uses the same scopes for read-only and read-write operations, so the connected user's access level inside Google Ads decides what works. This table follows Google's help page on access levels.
| What the Google user can do | Access levels that allow it |
|---|---|
| View campaigns and use planning tools | Read-only, Standard, Admin |
| Edit and run campaign performance reports | Read-only, Standard, Admin |
| Edit campaigns | Standard, Admin |
| View users, managers and product links | Read-only, Standard, Admin |
| Add or remove product links | Admin |
| Give account access, change access levels and cancel invitations from other users | Admin |
| View billing information | Billing, Read-only, Standard, Admin |
For agencies: a user invited to a manager account reaches the accounts linked below it, and a role granted at manager level is inherited by those accounts. The account list call returns only accounts the login reaches directly, so a client account under a manager can be missing from it. Calls that run through a manager need that manager's customer ID as loginCustomerId, and leaving it out gives AuthorizationError.USER_PERMISSION_DENIED. Over MCP every Google Ads tool also takes an optional connection_id to pick a connected Google login.
What the default connection leaves out: accounts the connected login cannot open, client accounts under a manager login that was not connected, changes when the Google user has read-only access, video file uploads (a video ad needs a YouTube link), removing people from a Customer Match list (the upload tool only adds members) and any undo of a removal, since Google Ads has none. The Google Ads API access level of the Google Cloud project behind the connection, and so its daily operation ceiling, is not published and was not checked.
Sources: Google OAuth 2.0 scopes, Google Ads API access model, Google Ads access levels, Google Ads API call structure, Google Ads API OAuth overview. Checked November 14, 2026.
Removing access
To remove access, click View on the Google Ads card in Ryze AI and disconnect the login. Google lists third-party access on its Google Account permissions page at myaccount.google.com/permissions, where you can revoke it. In Hermes Agent, set enabled: false on the ryze entry or delete it from config.yaml, and delete ~/.hermes/mcp-tokens/ryze.json to drop the cached tokens.
What Hermes Agent can do in Google Ads
The Ryze AI connector exposes 16 Google Ads tools: 8 read, 7 write and 1 delete. Calls go through Google's official API, and each one runs with the permissions of the Google login you connected. In Hermes Agent the names appear with the mcp_ryze_ prefix.
| Tool | Type | What it does |
|---|---|---|
| google_ads__getAccountSummary | Read | Totals for spend, clicks and the other account metrics over a date range you name. |
| google_ads__getAccountHierarchy | Read | Shows which sub-accounts sit under a manager account. |
| google_ads__listAccessibleCustomers | Read | Shows every customer account the connected Google login can open. |
| google_ads__listConversionActions | Read | Shows the conversion actions defined in an account. |
| google_ads__listRecommendations | Read | Shows the optimization recommendations Google has for an account. |
| google_ads__runRawGaql | Read | Runs any GAQL query you write, change history from change_event included. |
| google_ads__generateKeywordIdeas | Read | Returns Keyword Planner ideas for seed keywords, a URL or both. |
| google_ads__generateKeywordHistoricalMetrics | Read | Returns average monthly searches, competition and the top-of-page bid range for keywords you already have. |
| google_ads__runRawMutate | Write | Creates or edits campaigns, budgets, ad groups, ads, keywords, criteria and assets through a raw mutate. |
| google_ads__runRawCustomAudienceMutate | Write | Creates or edits custom audiences built from keywords, URLs, place categories or apps. |
| google_ads__runRawUserListMutate | Write | Creates or edits user lists, Customer Match lists included. |
| google_ads__uploadCustomerMatchMembers | Write | Adds people to a Customer Match list, with every identifier normalized and SHA-256 hashed by the server before Google sees it. It cannot remove members. |
| google_ads__uploadImageAsset | Write | Fetches an image from a URL and stores it as an image asset for campaigns, ad groups, asset groups or ads. |
| google_ads__applyRecommendation | Write | Accepts Google recommendations and applies them. |
| google_ads__dismissRecommendation | Write | Dismisses Google recommendations. |
| google_ads__runRawMutateDelete | Delete | Removes resources for good. Its description asks the agent to use it only on a list you approved item by item. |
Approvals in Hermes Agent
In Hermes Agent, approval for MCP tools is set per server. Adding trust: untrusted to the ryze entry makes every write-capable call on that server ask first, and tools annotated readOnlyHint stay unprompted. The documentation names no default for an entry without a trust key, so set it explicitly if you want the prompt. /yolo, --yolo and approvals.mode: off skip the prompt, and scheduled tasks on the Ryze AI side run without an approval step. Whether the Ryze AI tools carry the readOnlyHint annotation was not checked, so expect prompts on some reads as well.
mcp_servers:
ryze:
url: "https://connector.get-ryze.ai/mcp"
auth: oauth
trust: untrustedGoogle Ads limits in numbers
Google meters the Google Ads API per Google Cloud project and per account, and every figure below comes from a Google page named in the sources line. The last two rows are input limits from the connector's tool definitions as listed on November 13, 2026.
| Limit | Number |
|---|---|
| Operations per day | 2,880 against production accounts with Explorer access, 15,000 with Basic access, and no daily cap with Standard access. Google counts a sliding 24 hours per Google Cloud project |
| What one operation is | One Search or SearchStream request, however many batches it streams. Refused requests count; next pages fetched with a valid page token do not |
| Rate limits | Requests per second are metered per customer ID and per Google Cloud project, with no fixed number published. An overload returns RESOURCE_TEMPORARILY_EXHAUSTED, and Google advises exponential backoff, for example 2, 4, then 8 seconds |
| Rows per report page | Up to 10,000. The page size is fixed; setting page_size returns PAGE_SIZE_NOT_SUPPORTED. A page token expires after about two hours |
| Change history | The past 30 days. A change_event query needs a date filter and a LIMIT of at most 10,000, and a change can take up to 3 minutes to appear |
| Keyword Planner | 1 request per second per customer ID. A history request takes up to 10,000 keywords and up to 10 locations |
| Changes in one request | At most 10,000 mutate operations |
| Data freshness | In most cases clicks, impressions and cost refresh hourly. Impression share and auction insights usually update once a day. Conversions counted with attribution models other than last click arrive later |
| GAQL query through Ryze AI | 1 to 10,000 characters. A query Google does not finish within 150 seconds comes back as a timeout |
| Customer Match upload through Ryze AI | 1 to 100,000 members per call, passed to Google in chunks of 10,000 |
Sources: Google Ads API quotas, API access levels, rate limits, paging, change event, keyword historical metrics, Google Ads data freshness. Checked November 14, 2026. The two Ryze AI rows come from the connector's tool definitions as listed on November 13, 2026.
Google Ads calls in the test
On November 13, 2026 nine Google Ads calls went through the Ryze AI connector from Claude Code, on the default connection to a real account. Two were meant to return data and seven were built to fail. Account IDs and every number from the account are left off this page. These calls did not come from Hermes Agent.
| Tool | What the call asked for | Result |
|---|---|---|
| google_ads__listAccessibleCustomers | The accounts the connected login reaches directly | Worked. A list of resource names of the form customers/<ID> |
| google_ads__generateKeywordHistoricalMetrics | History for google ads mcp, connect chatgpt to google ads and google ads api, United States, English, Google Search | Worked. For each keyword: average monthly searches, competition, a competition index, a top-of-page bid range and 12 monthly values |
| google_ads__runRawGaql | A field that does not exist, campaign.daily_budget | Refused, HTTP 400, UNRECOGNIZED_FIELD |
| google_ads__runRawGaql | A resource that does not exist, campaign_experiment | Refused, HTTP 400, UNRECOGNIZED_FIELD |
| google_ads__runRawGaql | SELECT misspelled as SELEC | Refused, HTTP 400, EXPECTED_SELECT |
| google_ads__runRawGaql | change_event with no LIMIT | Refused, HTTP 400, LIMIT_NOT_SPECIFIED |
| google_ads__runRawGaql | change_event with LIMIT 10001 | Refused, HTTP 400, INVALID_LIMIT_CLAUSE |
| google_ads__runRawGaql | An invented 10-digit customer ID | Refused, HTTP 401, CUSTOMER_NOT_FOUND |
| google_ads__generateKeywordHistoricalMetrics | Language and location sent as bare numbers, 1000 and 2840 | Refused, HTTP 400, RESOURCE_NAME_MALFORMED |
None of the nine responses carried a quota counter or a rate-limit header. The error payloads name Google Ads API version v24. No report that returns account data, no write tool and no delete tool was run, because the account is real.
First 3 prompts to run
Each answer comes from your own account, so this page describes what comes back instead of showing a result. Hermes Agent picks the tool itself; the names are listed so you can check which one ran.
1. List the accounts the login can reach
List every Google Ads account my connected login can open, and show which ones sit under a manager account.
Tools used: google_ads__listAccessibleCustomers, google_ads__getAccountHierarchy
What comes back: The accounts under the connected login with their customer IDs, and the manager and sub-account structure. Use an ID from this list in later questions.
2. Spend by campaign
Use GAQL to list my Google Ads campaigns with cost, conversions and conversion value for the last 30 days, ordered by cost.
Tools used: google_ads__runRawGaql
What comes back: One row per campaign with the three metrics you asked for, drawn from the report Google returns for that date range.
3. Who changed what
Show me every change made in the Google Ads account in the last 14 days: who made it, what changed and when. Cap the query at 1,000 rows.
Tools used: google_ads__runRawGaql (change_event)
What comes back: Changes with the user, the client type and the old and new values, within Google's 30-day change history. The query carries a LIMIT because change_event requires one.
When you want a change, describe it in plain words, such as adding negative keywords or pausing a campaign. With trust: untrusted on the ryze entry, Hermes Agent asks before it runs a write-capable call.
10 jobs to hand to Hermes Agent
Ten jobs you can give Hermes Agent, each with the tool that does the work. In the connector test only the two calls marked as tested were run, and no job below was run from Hermes Agent.
| Job | Ask Hermes Agent | Tool | Works on the default connection |
|---|---|---|---|
| Spend, conversions and ROAS by campaign | Show spend, conversions and ROAS by campaign for last month. | google_ads__getAccountSummary, google_ads__runRawGaql | Works |
| Recent changes | Show who changed what in the last 14 days. | google_ads__runRawGaql (change_event) | Works. Google keeps 30 days of history and the query needs a LIMIT of 10,000 or less. Only the two LIMIT refusals were run |
| Account structure | List every account this login can reach and show the manager hierarchy. | google_ads__listAccessibleCustomers, google_ads__getAccountHierarchy | Works. The account list call was tested on November 13, 2026 |
| Keyword ideas | Give me Keyword Planner ideas from these seed keywords or from this landing page URL. | google_ads__generateKeywordIdeas | Works |
| Keyword search volume | Show average monthly searches, competition and the top-of-page bid range for this keyword list. | google_ads__generateKeywordHistoricalMetrics | Works. Tested on November 13, 2026 for three keywords |
| Conversion tracking check | List the conversion actions in this account. | google_ads__listConversionActions | Works |
| Google recommendations | List Google's recommendations, then apply or dismiss the ones I name. | google_ads__listRecommendations, google_ads__applyRecommendation, google_ads__dismissRecommendation | Listing works. Applying or dismissing works with Standard or Admin access |
| Campaign edits | Add these negative keywords, pause this campaign or change this budget. | google_ads__runRawMutate | Works with Standard or Admin access. Fails with Read-only access |
| Image assets | Upload this image from a URL and link it to a campaign, ad group or Performance Max asset group. | google_ads__uploadImageAsset, google_ads__runRawMutate | Works with Standard or Admin access. Video files cannot be uploaded; a video ad needs a YouTube link |
| Customer Match and audiences | Create a Customer Match list and add the contacts from this CSV, or build a custom audience from keywords and URLs. | google_ads__runRawUserListMutate, google_ads__uploadCustomerMatchMembers, google_ads__runRawCustomAudienceMutate | Works with Standard or Admin access. Contacts are hashed with SHA-256 on the server before Google sees them. The upload only adds members |
5 ways to connect Hermes Agent to Google Ads
Five routes give Hermes Agent access to Google Ads data. This guide treats the Ryze AI connector as the main way: Hermes Agent adds one hosted address, the Google sign-in happens once in Ryze AI, and no Google Cloud project, OAuth client or developer token is needed. Each setup cell says how the route would work in Hermes Agent; none of them was run there.
| Way | Runs where | Setup in Hermes Agent | What it can do in Google Ads | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI, one address for every user | A ryze entry with url and auth: oauth, then hermes mcp login ryze. Or a bearer header with a Ryze AI API key read from ~/.hermes/.env | 16 tools: GAQL reports and change history, Keyword Planner, recommendations, edits to campaigns, budgets, bids, keywords, ads and assets, audiences and Customer Match, plus one delete tool. The same address carries the other platforms connected in the workspace | Paid Ads is $89 per month with a 7-day free trial; Agency is $279 per month |
| Google Ads MCP server (google-ads-mcp), from Google | On your computer over stdio, or on a deployment of your own such as Cloud Run | Hermes Agent supports stdio servers by command and args, so Google's pipx entry can be written under mcp_servers. Google's guide and README do not name Hermes Agent. It needs Python 3.10 or later, pipx, a Google Cloud project with the Google Ads API enabled and Explorer, Basic or Standard API access, and Application Default Credentials | 7 tools: 3 that read (any GAQL report, the account list, field metadata) and 4 that create assets, upload videos and manage labels through a propose-and-confirm step. It cannot create, change, pause or enable campaigns, ad groups, ads, budgets or bids | Google's page states no price. Open source under Apache-2.0, version 0.0.6 published November 2, 2026 |
| Composio | Hosted | Composio lists Hermes on its Google Ads page. Ryze AI's older guide to Hermes Agent uses a config.yaml entry for https://connect.composio.dev/mcp with a Composio API key header, or the Composio CLI. Google Ads is authorized through Composio's managed OAuth app | 78 Google Ads tools that read and write, among them batch mutates, customer lists, experiments and three Keyword Planner tools | Composio's pricing page: the free plan stops at 10,000 app tool calls a month, and Standard is $18 per seat per month |
| Zapier MCP | Hosted | Generate a Zapier MCP URL, choose the Google Ads actions, then add the URL as a remote HTTP server. Zapier says it works with any MCP client that supports Streamable HTTP and does not list Hermes Agent in the names recorded for this guide | A fixed action list: 2 triggers, 10 create or update actions, 4 searches and 1 find-or-create, including Create Report, Set Campaign Status and a raw API Request. No action is built for GAQL or for building a campaign | Each successful tool call uses 2 tasks from your Zapier plan; failed calls use none |
| Coupler.io Custom MCP | Hosted, on synced copies of your data | Coupler.io says that for other clients you choose Custom MCP as the destination, generate a token, and paste the server URL and an Authorization: Bearer header into the client's config. That maps to the headers key of an mcp_servers entry. Hermes Agent is not named on its Google Ads page | Read-only. The page says the connector doesn't write changes back to Google Ads and that your AI tool never queries Google Ads directly. Data syncs on your schedule | Free plan: 1 account, 100 rows per run, manual refresh. Starter is $32 per month ($24 billed annually) |
Ryze AI's older post, How to connect Google and Meta Ads with Hermes Agent, sets up Composio. It is a different route from this guide and both can stay in config.yaml under different server names. Google's developer-token page says tokens were sunset on September 9, 2026 and are ignored if sent, so neither Google's server nor the Ryze AI connector asks you for one. Google's MCP guide describes no Google Ads endpoint that Google hosts for you. With the Ryze AI connector your Google Ads data passes through Ryze AI.
Google Ads options that do not fit Hermes Agent
- Google Ads API agent skills (google/skills). Instruction packs for coding agents, with install lines for Claude Code, Codex, Cursor and Antigravity. Hermes Agent is not named, and Google's page describes no account connection of their own, so they do not count as a way to connect.
- Google Ads API Developer Assistant v4.0.0. A plugin built for Google Antigravity and Claude Code. It runs read-only reports and writes changes out as code without executing them. Hermes Agent is not named.
- Windsor.ai. A hosted data connector that can also pause campaigns and adjust budgets from ChatGPT and Claude. Its page names Claude, ChatGPT, Perplexity, Cursor, Gemini and Copilot, not Hermes Agent, and its setup steps are plugin installs.
- cohnen/mcp-google-ads, open source. Five reporting tools. The README has setup sections for Claude Desktop and Cursor and still asks for a developer token that Google now ignores. It runs as a Python process on your computer, which Hermes Agent could start by command, but the README does not cover that.
Which one to pick
Ryze AI is the best way to connect Hermes Agent to Google Ads for reports and campaign changes from one hosted address, with these caveats: you need a Ryze AI plan once the trial ends, your Google Ads data passes through Ryze AI, the Hermes Agent steps in this guide come from its documentation rather than a test run, and video uploads and removing Customer Match members stay out of reach. Run Google's google-ads-mcp instead if you would rather keep a third party out and can look after a Google Cloud project and an OAuth client; it covers GAQL reports plus assets and labels. Composio, Zapier and Coupler.io make sense when your team already pays for one of them.
Sources: Google Ads API MCP server guide, googleads/google-ads-mcp, Google developer token sunset, Google Ads API agent skills, Google Ads API Developer Assistant, Composio Google Ads toolkit, Composio pricing, Zapier MCP for Google Ads, Zapier MCP quickstart, Coupler.io Google Ads MCP, Windsor MCP, cohnen/mcp-google-ads, Hermes Agent MCP documentation. Checked November 14, 2026.
Hermes Agent, Google Ads and MCP: dates that matter
| Date | What happened |
|---|---|
| October 7, 2025 | Google announced the open source release of the Google Ads API MCP server. The first release was read-only. |
| April 1, 2026 | Google restricted UserDataService and OfflineUserDataJobService for new adopters. New Customer Match integrations must use the Data Manager API. |
| June 15, 2026 | Google restricted ConversionUploadService.UploadClickConversions for new adopters. New conversion upload integrations must use the Data Manager API. |
| September 9, 2026 | Google Ads API developer tokens were sunset. API access levels now belong to the Google Cloud project, and a token sent in the header is ignored. |
| October 14, 2026 | Google Ads API v26 released. The oldest version still available on November 13, 2026 was v23, which sunsets in February 2027. |
| November 2, 2026 | google-ads-mcp 0.0.6 added asset and label management with a propose-and-confirm flow, the first release of Google's server with tools that change an account. |
| November 13, 2026 | Google's MCP server guide showed Last updated 2026-11-13 UTC when it was read on November 14. |
| November 16, 2026 | The Hermes Agent GitHub releases page listed canary builds of v0.23.1, the newest tagged November 16. Its MCP documentation can change between builds, so run hermes mcp test ryze after an update. |
Sources: Hermes Agent releases, Google Ads Developer Blog, October 2025, developer token page, Google Ads API sunset dates, google-ads-mcp releases, Google Ads API MCP server guide. Checked November 14, 2026.
How this guide was tested
The Ryze AI connector was checked on November 13, 2026 from Claude Code, the Google pages behind this guide were read on November 14, 2026, and the Hermes Agent documentation was read on November 16, 2026. Each row is something that was run or read, with what it returned.
| What was run | What came back |
|---|---|
| The tool list, loaded in Claude Code signed in to the connector | 16 Google Ads tools under the names in the tools table: 8 read, 7 write, 1 delete. |
| Two Google Ads reads that return data | Both worked: the list of reachable accounts and Keyword Planner history for three keywords. The values stay off this page. |
| Seven Google Ads calls built to fail | Each was refused by the Google Ads API with the message shown under errors and fixes. |
| Quota during the nine calls | No rate limit or daily quota was reached, so no quota error message was collected. |
| The Hermes Agent MCP and security documentation, read on November 16, 2026 | It describes remote HTTP servers with auth: oauth, a fallback to dynamic client registration, the token cache path, hermes mcp login, /reload-mcp, tool filters and the trust setting. Those pages are the source of every Hermes Agent step on this page. |
Not run for this guide: every step inside Hermes Agent. Hermes Agent was not installed, so hermes mcp login ryze and the config.yaml entries follow its documentation as read on November 16, 2026. On paper the sign-in fits: Hermes Agent falls back to dynamic client registration, which is the only registration method the Ryze AI connector supports. The Ryze AI help center has no page for Hermes Agent, and Ryze AI was not tested there. The write and delete tools were not run, and no report that returns account data was run.
Hermes Agent and Google Ads errors and fixes
Exact error messages from the test
The Google Ads API sent back these messages in the test on November 13, 2026. Each 400 came with the outer message Request contains an invalid argument. If Hermes Agent shows one of them, the cause is in the request, not in the connection.
| Message | What it means | What to do |
|---|---|---|
| Unrecognized field in the query: 'campaign.daily_budget'. | The field does not exist on that resource in the API version in use (queryError UNRECOGNIZED_FIELD). The tool description names the right one, campaign_budget.amount_micros selected FROM campaign. | Ask Hermes Agent to check the field name and run the query again. |
| Unrecognized field in the query: 'campaign_experiment.name'. | The resource does not exist. Google Ads reports an unknown resource as an unrecognized field. Experiments live in the experiment resource. | Query the experiment resource instead. |
| Error in query: expected SELECT instead of SELEC. | The GAQL text is malformed (queryError EXPECTED_SELECT). | Ask again; the agent rewrites the query. |
| Change event requests must specify a LIMIT in query and LIMIT should be less than or equal to 10k. | A change history query had no LIMIT (changeEventError LIMIT_NOT_SPECIFIED). | Add LIMIT with a value of 10000 or less. |
| Change event requests must specify a LIMIT less than or equal to 10k. | A change history query asked for more than 10,000 rows (changeEventError INVALID_LIMIT_CLAUSE). | Lower the LIMIT, or split the date range and continue after the last timestamp. |
| No customer found for the provided customer id. | The customer ID does not exist (HTTP 401, authenticationError CUSTOMER_NOT_FOUND). The outer message talks about missing credentials, but the cause was the ID: the same connection answered other calls seconds earlier. | List the accounts with google_ads__listAccessibleCustomers and use an ID from that list. |
| Resource name '1000' is malformed: expected 'languageConstants/{criterion_id}'. | Keyword Planner wants full resource names, for example languageConstants/1000 and geoTargetConstants/2840, not bare numbers (requestError RESOURCE_NAME_MALFORMED). | Ask again; the agent resends full resource names. |
Other problems
- The tools do not show up in Hermes Agent
- Start a new session or run /reload-mcp. Then run hermes mcp test ryze, which reports what the server answered. The documentation lists a failed connection, failed discovery, a tools.include or tools.exclude filter and enabled: false as causes.
- The browser sign-in times out
- Editing config.yaml inside a running session triggers an automatic MCP reload with a 30-second timeout, too short for OAuth. Add the entry, then run hermes mcp login ryze. If you need longer than 5 minutes to approve, set oauth.timeout on the entry.
- Hermes Agent cannot reach the callback on a server
- Use the paste-back prompt that hermes mcp login prints, forward the callback port over SSH, or sign in from the Hermes Desktop app.
- A 401 or 403 from the connector
- The Hermes Agent documentation says a 401 or 403 means the token or OAuth grant is wrong. Run hermes mcp login ryze again. With an API key, check that RYZE_API_KEY is set in ~/.hermes/.env and that the header reads Bearer followed by the rk_live_ key.
- The server stopped working after days of use
- A refresh token can die. The documentation says the server is parked with a warning in gateway.log and you re-authorize once with hermes mcp login ryze.
- A write fails with a permission error
- The connected Google user probably has Read-only access. Google Ads permissions are set in Google, not in Ryze AI or Hermes Agent. Use a login with Standard or Admin access.
- A client account under a manager is missing
- The account list returns only accounts the login reaches directly. Pass the manager's customer ID as loginCustomerId, or leave it out and get AuthorizationError.USER_PERMISSION_DENIED.
- Requests fail behind a proxy
- HTTP servers honor HTTPS_PROXY, HTTP_PROXY and NO_PROXY, so set them in the environment Hermes Agent starts from.
Terms on this page
- Hermes Agent
- An open source AI agent from Nous Research that you run on your own machine or server. Its MCP servers are listed in ~/.hermes/config.yaml under mcp_servers.
- MCP
- Model Context Protocol, an open standard that lets large language models interact with external data and applications. The Ryze AI connector is a remote MCP server.
- GAQL
- Google Ads Query Language, the query language of the Google Ads API. A query selects fields FROM one resource and returns rows with attributes, segments and metrics.
- Customer ID and login-customer-id
- The customer ID is the 10-digit number of a Google Ads account, written without hyphens in API calls. login-customer-id is the manager account's ID, required when access to a client account runs through a manager.
- Manager account (MCC)
- A Google Ads account that lets you view and manage multiple Google Ads accounts, including other manager accounts, from a single location.
- Access level (two meanings)
- In a Google Ads account, a user's access level is Email-only, Billing, Read-only, Standard or Admin and decides whether they can edit campaigns. In the Google Ads API, a Google Cloud project's access level is Test, Explorer, Basic or Standard and decides the daily number of operations.
- Dynamic client registration
- A way for an OAuth client to register itself with the authorization server. Hermes Agent uses it when the server does not support a Client ID Metadata Document, and the Ryze AI connector supports only this method.
Sources: GAQL overview, Google Ads API call structure, change event, Google Ads API MCP server guide, Hermes Agent MCP documentation. Checked November 14, 2026.
Frequently asked questions
How do I connect Hermes Agent to Google Ads?
Link Google Ads in Ryze AI, add a ryze entry with the URL https://connector.get-ryze.ai/mcp and auth: oauth under mcp_servers in ~/.hermes/config.yaml, run hermes mcp login ryze and click Allow connection. Then start a new session or run /reload-mcp and ask for a Google Ads report.
Is there a Google Ads MCP connector for Hermes Agent?
Yes, the Ryze AI connector at https://connector.get-ryze.ai/mcp. It is a remote MCP server with 16 Google Ads tools, and Hermes Agent supports remote HTTP servers with OAuth. Google's guide describes no Google Ads endpoint hosted by Google, and the Hermes Agent documentation read for this guide names no Google Ads catalog entry.
Does Hermes Agent have a Google Ads MCP server?
Hermes Agent connects to MCP servers such as the Ryze AI connector, and the pages read for this guide name no Google Ads server that ships with it. Google publishes its own open source google-ads-mcp, which you run yourself and which the Hermes Agent documentation does not mention.
Can I use Google's google-ads-mcp with Hermes Agent?
Probably, because Hermes Agent starts stdio servers from a command and args, and google-ads-mcp is started with pipx. Google's guide and README do not name Hermes Agent and this was not tested. The server has 7 tools, 3 that read and 4 that create assets, upload videos and manage labels, and it cannot change campaigns, ads, budgets or bids.
Is this the same as the Composio setup in the older Ryze AI post?
No. The older post, How to connect Google and Meta Ads with Hermes Agent, sets up Composio with its own endpoint and API key header. This guide uses the Ryze AI connector, which has its own sign-in and its own 16 Google Ads tools. Both can sit in config.yaml under different server names.
Does Hermes Agent need a paid plan for MCP?
No. Hermes Agent is open source under the MIT license per its GitHub repository and self-hosted, and MCP support ships with the standard install. The Ryze AI side needs a plan or trial for the Google Ads tools: Paid Ads at $89 per month with a 7-day free trial.
Should I use OAuth or an API key?
Use OAuth when you can open a browser, because hermes mcp login ryze handles the sign-in and Hermes Agent refreshes the tokens. Use a Ryze AI API key in a bearer header for servers and scripts where nobody can click Allow connection. The key works on the /mcp endpoint only.
Can Hermes Agent change my Google Ads account?
Yes, when the connected Google user has Standard or Admin access, because 7 of the 16 tools write and 1 deletes. With Read-only access every change fails. To have Hermes Agent ask first, set trust: untrusted on the ryze entry.
How do I make it read-only?
Connect a Google login that only has read access, which is a hard guarantee. In Hermes Agent you can also list the 8 read tools under tools.include on the ryze entry, which hides the write and delete tools from the agent but is not enforced by Google.
Does it work on a headless server or a VPS?
Yes, with an extra step for the sign-in. Paste the redirect URL back at the prompt that hermes mcp login prints, forward the callback port over SSH, or use the Hermes Desktop app. An API key avoids the browser entirely.
Does it work through the Hermes Agent messaging gateway?
The gateway connects servers from config.yaml but never opens a browser, so run hermes mcp login ryze once first. The documentation says a server with a dead refresh token is parked with a warning in gateway.log until you log in again.
Can I manage client accounts under a manager account?
Yes. One Google login reaches every account it can access, including client accounts under a manager (MCC) login that you connected. Calls that run through the manager need its customer ID as loginCustomerId.
Why do the Google Ads tools not show up in Hermes Agent?
Start a new session or run /reload-mcp, then run hermes mcp test ryze. Check that no tools.include or tools.exclude filter hides them and that the entry is not set to enabled: false. Also confirm that Google Ads shows Connected in Ryze AI.
How much does it cost?
Adding the connector is free. The Google Ads tools need a Ryze AI plan or trial: Paid Ads is $89 per month with a 7-day free trial, Agency is $279 per month, and annual billing takes 30% off the first year. Hermes Agent itself is free software.
How do I disconnect Google Ads from Hermes Agent?
Set enabled: false on the ryze entry or delete it from config.yaml, and delete ~/.hermes/mcp-tokens/ryze.json. To cut Google access as well, disconnect the login on the Google Ads card in Ryze AI or revoke it at myaccount.google.com/permissions.
Sources
- Hermes Agent MCP documentation
- Hermes Agent security and approvals documentation
- NousResearch/hermes-agent on GitHub
- Hermes Agent releases on GitHub
- Google Ads API MCP server guide
- googleads/google-ads-mcp
- Google Ads API quotas
- Google Ads API access levels
- Google Ads API access model
- Google Ads access levels (help)
- Google OAuth 2.0 scopes
- Google Ads API developer token sunset
- Composio Google Ads toolkit
- Zapier MCP for Google Ads
- Coupler.io Google Ads MCP
- Ryze AI help center: Google Ads
Checked November 14, 2026.