Google and Meta both now ship an official MCP server so Claude can read ad account data directly: Google's is read-only and open source, Meta's is a hosted, read-write server with 7 tool categories. Either one gets you started on a single platform in minutes. The moment you run more than one platform, the question changes from "which server" to whether you want one server per platform at all.
Key Takeaways
- Google's official Google Ads MCP server is open source, read-only, and exposes three tools: listing accessible accounts, running GAQL reports, and reading resource metadata. It cannot pause a campaign or change a bid.
- Meta's official Ads MCP server is hosted at mcp.facebook.com/ads and covers reporting, campaign creation and edits, catalog management, signal health, A/B and lift tests, and activity logs, so it can write to your account, not just read from it.
- Both are single-platform servers: each one only ever knows about the account you connected it to, so a cross-channel question still means asking two agents and combining the answers yourself.
- A platform-specific MCP server is the right call when the question genuinely stays inside that platform, like a GAQL query against one Google Ads account.
- The moment the question spans Google Ads, Meta Ads, and whatever else is in the stack, one governed gateway with a single audit trail replaces a server per platform, per person.
What Is Google Ads MCP?
Google Ads MCP is Google's own open-source Model Context Protocol server for the Google Ads API, announced on the Google Ads Developer Blog. It runs as a local Python process over standard input/output (stdio) and authenticates with OAuth 2.0 or a service account against a Google Cloud project with Google Ads API access.
It exposes three tools, and only three: list_accessible_customers (the Google Ads customer IDs and account names the authenticated user can see), search (runs a GAQL query against campaigns, budgets, and status), and get_resource_metadata (reads the schema of a Google Ads API resource type). Google's own documentation is explicit that the server is "strictly read-only: it cannot modify bids, pause campaigns, or create new assets." For a Claude session that only needs to answer questions about one Google Ads account, that is a complete, honest tool, not a stripped-down one.
What Is Meta Ads MCP?
Meta's official ads MCP server, documented under Meta for Developers as an "AI connector," is remote-hosted at mcp.facebook.com/ads and, per Meta's own page, "works with any MCP-compatible AI agent." Unlike Google's server, it is not read-only. Meta's documentation groups its tools into seven areas: comprehensive reporting (spend, CPA, ROAS and reach across campaigns, ad sets and ads); ad creation and management, which can create and edit ads, ad sets and campaigns; catalog creation and management, including troubleshooting feed and item-visibility issues; signals and datasets, covering signal health and quality; a Meta Business Help Center search tool; A/B tests and conversion lift studies; and activity logs that mirror the Ads Manager campaign-history page.
That write capability is the trade-off, not a bonus. A read-only server can sit in a shared Claude workspace with no blast radius. A server that can create and edit campaigns needs the same access discipline you would give a person: who can connect it, what they can approve, and where the record of what it changed lives.
Google Ads MCP vs. Meta Ads MCP
| Property | Google Ads MCP | Meta Ads MCP |
|---|---|---|
| Publisher | Google (official, open source) | Meta (official, hosted) |
| Hosting | Self-run, stdio transport | Meta-hosted at mcp.facebook.com/ads |
| Auth | OAuth 2.0 or service account | OAuth through a Meta developer app |
| Read or write | Read-only by design | Read and write (can create/edit campaigns) |
| Tool surface | 3 tools: accounts, GAQL search, resource metadata | 7 tool categories: reporting, campaign management, catalog, signals, help search, tests, activity log |
| Scope | One Google Ads account per connection | One Meta ad account per connection |
Talk to an Improvado expert about connecting Claude to your full ad stack.
When a Single-Platform MCP Server Is the Right Call
Use Google's or Meta's own server when the question never leaves that platform: "what did this Google Ads account spend on Campaign X last week" is a GAQL query away with Google's server, and "what is the ROAS on this Meta ad set" is a reporting call away with Meta's. Both are official, both are free, and both save you from writing a wrapper around an ad-platform API yourself. If you run one platform, or you are prototyping against one account, connect the vendor's own server and stop there.
When One Gateway Beats Five Servers
The moment you add a second platform, the arithmetic changes. Every additional single-platform MCP server means another OAuth grant to manage, another credential living in someone's local config, and another tool list Claude has to hold in context on every call, with no shared governance across any of them. We wrote the longer version of this argument in why we built one MCP gateway instead of fifty MCP servers: past two or three platforms, a server-per-platform setup breaks on credential sprawl, context bloat, and the fact that most platforms in a real marketing stack, the smaller ad networks, the CRM, the warehouse, never get an MCP server built for them at all.
A single governed gateway answers a cross-channel question the way a marketer actually asks it, in one Claude session, without you writing the join between Google Ads and Meta Ads yourself. See seven real workflows people run through one MCP connection for what that looks like once your ad platforms, CRM, and warehouse tables are behind a single endpoint, and how to see the AI agent traffic your analytics currently misses for the measurement side of the same shift toward agents acting on your data directly.
How Improvado MCP Connects Claude to Your Ad Data
Improvado MCP is one governed endpoint in front of a 187-source public connector catalog, ad platforms, CRMs, and warehouses included, so Claude reaches every source you have connected through a single OAuth grant instead of one per platform. Credentials stay on Improvado's side; Claude gets tool calls, and every call runs under your existing Improvado role permissions, so a read-only role gets read-only tools regardless of which platform the question touches. Setup is the same couple of minutes as connecting a single-platform server: add Improvado MCP as a custom connector in Claude, authorize with your Improvado account, and every source in your workspace, Google Ads and Meta Ads included, becomes something Claude can query and chart in the same session. The full setup guide is in the Improvado MCP documentation.
Give your agent every ad source through one connection.
Frequently Asked Questions
Is Google's Google Ads MCP server free?
Yes. It is open source, published by Google on the Google Ads Developer Blog, and you run it yourself; the only cost is your own Google Ads API access and hosting for the process.
Can Meta's Ads MCP server change my campaigns?
Yes. Meta's own documentation lists ad, ad set, and campaign creation and editing among its tool categories, alongside reporting, catalog management, signal health, A/B and lift tests, and activity logs, so it is a read-write connection, not a reporting-only one.
Do I need a separate MCP server for every ad platform?
Only if every question you ask stays inside one platform. Google's and Meta's servers each know about one account on one platform; the moment a question spans platforms, a single gateway that already holds every connection answers it in one session instead of two.
What is the difference between an MCP server and an MCP gateway?
A server is built for one platform's API, so Claude gets one tool set per server you connect. A gateway sits in front of many platforms behind one endpoint and one OAuth grant, so Claude gets one tool set that already spans everything you have connected.
Does Improvado MCP replace Google Ads MCP or Meta Ads MCP?
It replaces the need to run them side by side for cross-channel work. If you only ever query one platform, the vendor's own server is a fine, free choice; Improvado MCP is for the workspace that also has Meta Ads, a CRM, and a warehouse in the picture and wants Claude to reach all of it through one connection.
