Adsap vs. Google's Official Google Ads MCP Server
Google's open source MCP server reads a Google Ads account through GAQL and creates nothing. Adsap creates and manages campaigns from Claude, ChatGPT, Perplexity or a web app, with a preview before every write. Google's server runs on your machine or your own Cloud Run and needs a Google Cloud project with an approved API access level. Adsap connects with Google sign-in. For reports, Google's server is free and official. For building and changing campaigns, Adsap does the work.
Adsap is our product. Facts about Google's server are from its public repository as of September 13, 2026.
What Google's server does well
Google released the server on October 7, 2025 and put the code on GitHub under the Apache 2.0 license. It exposes three tools: list_accessible_customers, search, which runs any GAQL query the API allows, and get_resource_metadata, which describes the fields of a resource. Four resources ship with it: the API discovery document, the metrics list, the segments list and the release notes. Give an assistant those and it can answer most reporting questions about an account without a fixed report menu. Setup: install with pipx, enable the Google Ads API in a Google Cloud project, add credentials, and point your MCP client at the local process. You can also host it on Cloud Run.
- Official Google code, open source under Apache 2.0
- Free, with no license fee
- GAQL: any read the Google Ads API allows, not a fixed report list
- Resource metadata, so the assistant learns the schema on its own
- Runs on your machine, so the data path is you, Google and your assistant
Where Google's server stops
Google calls this initial release read-only. It reports and diagnoses, and it will not make changes to your account. That is a sound choice for an official tool. It also means the work after the report stays manual:
- No campaign creation: Search, Performance Max, Demand Gen, Shopping, App and Display are all out of scope
- No budget or status changes, no keyword or negative changes, no extensions
- No video upload to YouTube
- Setup needs Python, a Google Cloud project with the Google Ads API enabled and an approved access level, and OAuth credentials
- By default it runs as a local process, for clients such as Claude Code, Cursor and VS Code. To reach it from a web assistant, you host it yourself
- No preview, no automation rules and no audit log, because it never writes
Adsap vs. Google's server, side by side
| Feature | Adsap | Google's MCP server |
|---|---|---|
| Create campaigns (Search, Performance Max, Demand Gen, Shopping, App, Display) | Yes | No |
| Edit budgets and status | Yes | No |
| Keyword ideas and negatives | Yes | No |
| Extensions (sitelinks, callouts, snippets, calls, promotions, prices) | Yes | No |
| YouTube video upload | Yes | No |
| GAQL reads (any query the API allows) | Curated read tools | Yes |
| Setup without a Google Cloud project | Yes | No |
| Preview before every write | Yes | No writes |
| Automation rules with a spend floor and cooldown | Yes | No |
| An audit log on every action | Yes | No |
| Free plan | $0, no card, 1 Google Ads account, 10 tasks a month | Free, open source |
| Price | Free, or $29/month plus tax for every tool | Free |
What Adsap adds
Adsap is a Google Ads MCP server and a web app. Connect a Google Ads account with Google sign-in in the browser, tick the Google Ads permission, and pick the customer accounts to manage. No Google Cloud project, no YAML file. From there you create Search, Performance Max, Demand Gen, Shopping, App and Display campaigns through guided wizards or the copilot. You pull keyword ideas from Keyword Planner, mine search terms for negatives, manage sitelinks and the other extensions, and upload videos to YouTube. Insights go down to the keyword, updated daily.
Everything Adsap creates starts paused. You see a preview before every write, and an audit log records every action. Automation rules need a spend floor you set, and wait 24 hours before acting on the same thing twice. Adsap also runs Meta Ads (see Adsap vs. Meta's official Ads AI connector), with about 100 tools across both platforms. Adsap curates its read tools: a fixed set of reports and lists, not free-form GAQL.
Choose Google's server if
- You want reports and diagnostics, not changes
- You write GAQL, or want an assistant that does
- You already have a Google Cloud project with Google Ads API access
- You work in a local MCP client such as Claude Code, Cursor or VS Code
Choose Adsap if
- You create campaigns, ad groups, keywords and extensions from a chat or a wizard
- You change budgets and status and want a preview first
- You want to connect with Google sign-in and skip the Cloud project
- You want automation rules with a spend floor, and an audit log
Frequently asked questions
Yes. MCP (Model Context Protocol) is an open standard that lets an AI assistant connect to outside tools through one common interface. Google publishes an official Google Ads MCP server on GitHub. It is read-only, and you host it yourself. Adsap runs a hosted MCP server at mcp.adsap.ai that also creates and edits campaigns, with a preview before every write.
Yes. Google published the code on GitHub under the Apache 2.0 license, and it carries no license fee. You run it yourself, so you need Python, a Google Cloud project with the Google Ads API enabled, and Google Ads API credentials. If you host it on Cloud Run instead of your machine, you pay Google Cloud for that hosting.
No. Google describes the initial release as read-only: it reports and diagnoses, and it will not make changes to your account. It exposes three tools: list accessible customers, search with GAQL, and resource metadata. Adsap creates Search, Performance Max, Demand Gen, Shopping, App and Display campaigns, and everything it creates starts paused.
Not any more. Google's guide says developer tokens were sunset on September 9, 2026, and the latest version of its server no longer needs one. API access levels now sit on the Google Cloud project instead. You still need that Cloud project with an approved access level, and OAuth or Application Default Credentials. Adsap asks for none of that. You sign in with Google in the browser, tick the Google Ads permission, and pick the accounts to manage.
Yes. Both are MCP servers, and nothing in either one stops you from adding both to the same assistant. Google's server runs as a local process, or on a server you host, and answers GAQL questions. Adsap connects over the web at mcp.adsap.ai and handles the writes: campaigns, ad groups, keywords, extensions, budgets and status, each with a preview first.
Claude works on any plan, including Free. ChatGPT works on any paid plan (Plus, Pro, Business, Enterprise or Edu), on the web only, with Developer mode turned on. Perplexity needs Pro, Max or Enterprise. The setup guide at adsap.ai/docs/guides/ai-copilot/setup has the steps for each. Google's README lists Antigravity, Claude Code, Cursor and VS Code as clients for its server.
Reports from Google's server, launches from Adsap
Keep Google's server for GAQL if you like it. Add Adsap when you want to create and change campaigns from the same assistant, with a preview before every write. Start on the Free plan, or take Early Access at $29/month plus tax for every tool.