A hosted Google Ads MCP server
HeyAdpilot is a remote Model Context Protocol server for Google Ads, Google Analytics 4, Search Console and Merchant Center. Point any MCP client at one URL, sign in with OAuth, and the model gets read and write tools, a specialist playbook and working rules. No developer token, no OAuth app of your own, nothing to host.
Written by the HeyAdpilot team. Facts checked .
The endpoint
https://www.heyadpilot.com/mcp- Transport: Streamable HTTP, JSON-RPC over POST. GET is not used.
- Auth: OAuth 2.1, authorization code flow with PKCE only. Access tokens last 1 hour; refresh tokens last 60 days and rotate on every use.
- Discovery: a 401 carries a WWW-Authenticate header with resource_metadata, and both /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server are published.
- Client registration: dynamic client registration (RFC 7591) at /oauth/register, so Claude, ChatGPT and other clients register themselves.
- Fallback: a private connection link with an embedded token for clients without OAuth, revocable from the dashboard.
Tokens are stored as hashes, and the Google refresh token is encrypted at the application level. The full list is on the security page.
The tool surface
Behind the server are more than 70 tools. Handing all of them with full descriptions to a client would use a large share of its context in every conversation, so the surface is deliberately small:
- Orientation: a get-started tool that returns the connected accounts, sources and a 30-day snapshot, an account list, and the playbook with its working rules.
- Common reads with their own entry: campaign results, campaign settings, search terms, keywords with Quality Score, ads, conversion actions, Search Console performance, GA4 website behaviour and the change history.
- A generic read and a generic write: the rest, such as GAQL queries, GA4 reports, Merchant Center reports, campaign creation and extensions, is reached through one read tool and one write tool. The model looks a tool up with a describe tool before first use.
Every tool carries MCP annotations (readOnlyHint, destructiveHint), so clients can let reads run freely and ask before writes. Each write takes a plain-language change summary, which is what the user sees in the confirmation and in the HeyAdpilot history. Writes are logged with the old and new value and can be undone. HeyAdpilot pauses rather than deletes. Tool names are kept stable, because a rename breaks connected clients.
The playbook is the part a raw API wrapper lacks: how a senior specialist audits an account, builds campaigns, sets up conversion tracking and screens keywords, plus rules such as reading a setting before talking about it, giving every number with its time window, and checking a second source before moving money.
Client setup
Claude (web, desktop, mobile): use the one-click link on the Claude guide, or add a custom connector with the URL above. ChatGPT: Business, Enterprise and Edu workspaces, see the ChatGPT guide.
claude mcp add --transport http heyadpilot https://www.heyadpilot.com/mcpThen run /mcp inside Claude Code and choose HeyAdpilot to sign in.
{
"mcpServers": {
"heyadpilot": {
"url": "https://www.heyadpilot.com/mcp"
}
}
}{
"servers": {
"heyadpilot": {
"type": "http",
"url": "https://www.heyadpilot.com/mcp"
}
}
}{
"mcpServers": {
"heyadpilot": {
"httpUrl": "https://www.heyadpilot.com/mcp"
}
}
}Perplexity, Le Chat and other clients that accept a remote MCP server with OAuth use the same URL. Each client starts the sign-in the first time a tool is called.
Hosted HeyAdpilot or self-hosting the open-source server
Google publishes an open-source Google Ads MCP server (googleads/google-ads-mcp on GitHub). It is a good choice if you want full control, run it inside your own infrastructure and mainly need to query data. As of November 2026 Google describes it as read-focused: recent versions add a few asset and label writes with a propose and confirm step, but no bid, budget or campaign edits.
| HeyAdpilot (hosted) | Self-hosted open-source server | |
|---|---|---|
| Setup | Paste one URL, sign in with Google and OAuth | Google Cloud project, Google Ads API access, an OAuth client or application default credentials, Python runtime |
| Where it runs | On HeyAdpilot | Your machine, or your own Cloud Run or server for remote use |
| Data sources | Google Ads, GA4, Search Console, Merchant Center | Google Ads |
| Writes | Budgets, bids, keywords, negatives, ads, campaigns, with confirmation, audit log and undo | Read-focused; limited asset and label writes in recent versions |
| Guidance for the model | Specialist playbook and working rules | API access and query tools |
| Maintenance | API version upgrades and fixes handled for you | You track releases and Google Ads API changes |
| Cost | $79 per month, unlimited accounts | Free software, plus your hosting and time |
If you only need GAQL access for yourself and like running your own services, self-hosting is reasonable. If you want writes with an approval trail, the other Google sources, and something a non-developer on your team can connect in a few minutes, the hosted server is the shorter path. Pricing is on the pricing page, and other options are compared in the best AI tools for Google Ads.
Questions people ask
What is a Google Ads MCP server?
An MCP server exposes Google Ads data and actions as tools that an AI client such as Claude, ChatGPT, Cursor or Gemini can call through the Model Context Protocol. A remote one runs on the web, so the client connects to a URL instead of starting a local process.
Do I need a Google Ads developer token or my own OAuth app?
Not with HeyAdpilot. You sign in to HeyAdpilot with Google, and HeyAdpilot holds the API access. Your MCP client signs in to HeyAdpilot with OAuth 2.1 and registers itself through dynamic client registration. Self-hosting Google's open-source server is different: you set up your own Google Cloud project, Google Ads API access and OAuth client.
Is the HeyAdpilot MCP server read-only?
No. It reads and writes. Read tools are marked read-only, write tools are marked as changing data, and MCP clients ask the user before a write runs. Every write is logged with the old and new value and can be undone from the HeyAdpilot history.
Which MCP transport does it use?
Streamable HTTP over POST at https://www.heyadpilot.com/mcp. Without a valid bearer token it answers 401 with a WWW-Authenticate header pointing at the protected resource metadata, which is how clients discover the sign-in.
My client does not support OAuth. Can I still connect?
Yes. Create a private connection link under Connections in the HeyAdpilot dashboard and use it as the server address. It carries a secret token, so treat it like a password and revoke it there if it leaks.
What does it cost?
$79 per month after a 7-day free trial without a credit card, with unlimited Google Ads accounts. HeyAdpilot sells no AI credits; the model runs in your own client.
Try it on your own account.
Connect your Google accounts, add HeyAdpilot to Claude or ChatGPT and ask your first question. 7 days free without a credit card, then $79 per month with unlimited Google Ads accounts.