# Hosted vs open-source MCP servers for Google Ads: how to choose in 2026

> A practical comparison of the ways to connect an AI assistant to Google Ads: open-source MCP servers you self-host with your own developer token, Google Ads Scripts, direct API use, and hosted servers like PaidHelm. Criteria, costs and who each fits.

URL: https://paidhelm.com/blog/best-mcp-servers-for-google-ads/  
Last updated: 2026-11-01

There are now several ways to let Claude, ChatGPT or Cursor touch a Google Ads account. They differ less in what they can do and more in who carries the operational weight. This guide lays out the options honestly, including where PaidHelm is not the best fit.

The options

OptionHow it worksBest for

Open-source MCP server (self-hosted)Run a community server locally or on your cloud; configure your own Google Cloud OAuth client and Google Ads developer token.Developers who want full control and already have API access.

Hosted MCP server (PaidHelm)Paste a URL, sign in with Google. Developer token, hosting, OAuth, quotas and safety rules are handled for you.Advertisers, freelancers, agencies without an engineering team.

Google Ads ScriptsJavaScript inside Google Ads running on a schedule.Fixed automated rules, no conversation needed.

Direct API with an agent frameworkBuild your own agent with the Google Ads client libraries.Product teams embedding ads management in their own software.

Criteria that actually matter

1. Developer token and API access

Every call to the Google Ads API needs a developer token tied to a manager account, and Google grants Basic access only after reviewing your application. Self-hosting means going through that process yourself and staying compliant with the API terms. A hosted server has already done it.

2. Authentication

Both approaches should use Google OAuth. The difference is who runs the OAuth app: you (self-hosted, with a consent screen you must verify for external users) or the provider.

3. Safety defaults

Check whether new campaigns are created paused, whether removal requires explicit IDs, and whether there are quotas that cap runaway loops. Community servers vary widely; read the code or test on a sandbox account.

4. Tool coverage

Many community servers focus on reporting (GAQL) and a handful of mutations. If you need Performance Max asset groups, Demand Gen, Shopping or image upload from the chat, check the tool list. PaidHelm's catalog lists all 32 tools.

5. Total cost

Self-hosted: $0 software + hosting + the hours to set up OAuth, token application, upgrades when the API version changes (Google deprecates versions roughly every 4 months).

Hosted: a subscription, from $0 (30 tasks) to $199/month (6,000 tasks) at PaidHelm, zero maintenance.

6. Data handling

Self-hosting keeps everything on your machine. A hosted server should document that it relays rather than stores your reports; see how PaidHelm handles data.

When to self-host

You are a developer, already hold a developer token with Basic access, and want to customize tools.

Compliance requires that no third party processes your advertising data.

You are building a product and need the server embedded in your stack.

When a hosted server is the better call

You run ads, not servers. You want to be working in the chat today.

You manage several client accounts and need one login to cover them all.

You want paused-by-default, quotas and support as part of the deal.

Our view

We built PaidHelm because we are an agency, not a software vendor, and we wanted the second column without maintaining the first. If you have an engineering team and the token already, self-hosting is legitimate. If you don't, start on the free plan and judge by the first week.

## FAQ

**Is self-hosting an MCP server for Google Ads free?**

The software is usually free, but you need a Google Ads API developer token (which requires an application and a manager account), a server to run it, and time to keep it working. For many teams the engineering hours cost more than a subscription.

**Can I switch later?**

Yes. Because MCP is a standard, the prompts and workflows you build with one server mostly carry over to another. Your campaigns always stay in Google Ads.