#1010th of 12 in MCP serversFor finance and business, e-commerce, marketing and sales

google-ads-mcp

MCP server for querying and managing Google Ads accounts from LLM agents

Stars
1.2k
License
Apache-2.0
Last commit
Nov 2026
Last release
Nov 2026
Language
Python
Stars, last 29 weeks+764
21 Apr 2026: 388 stars28 Apr 2026: 404 stars5 May 2026: 442 stars12 May 2026: 487 stars19 May 2026: 516 stars26 May 2026: 544 stars2 Jun 2026: 572 stars9 Jun 2026: 606 stars16 Jun 2026: 636 stars23 Jun 2026: 661 stars30 Jun 2026: 677 stars7 Jul 2026: 712 stars14 Jul 2026: 735 stars21 Jul 2026: 760 stars28 Jul 2026: 783 stars4 Aug 2026: 808 stars11 Aug 2026: 841 stars18 Aug 2026: 864 stars25 Aug 2026: 883 stars1 Sept 2026: 904 stars8 Sept 2026: 920 stars15 Sept 2026: 954 stars22 Sept 2026: 972 stars29 Sept 2026: 995 stars6 Oct 2026: 1,017 stars13 Oct 2026: 1,041 stars20 Oct 2026: 1,061 stars27 Oct 2026: 1,089 stars3 Nov 2026: 1,118 stars10 Nov 2026: 1,152 stars

388 on 21 Apr 20261,152 on 10 Nov 2026

From GitHub's daily star counts.

Checked on GitHub.

Overview

Python MCP server built on FastMCP that lets an agent run GAQL queries, read resource metadata, list accessible customers, and create assets and labels in Google Ads. Write tools use a propose-and-confirm flow: a validate_only dry run returns a checksum that must be passed back to commit. It runs over stdio with Application Default Credentials, or as a Streamable HTTP service with an OAuth proxy, including on Cloud Run.

Who it is for: Advertisers and engineers connecting AI agents to Google Ads accounts

Strengths

  • Mutating tools require a validate_only proposal and a matching checksum before committing
  • tools_config.yaml toggles tools by namespace; read-only mode is two settings
  • Runs over stdio with ADC or Streamable HTTP with OAuth proxy; Cloud Run steps documented
  • OAuth state storage can use filetree, Redis, Firestore or memory

Weaknesses

  • Only seven tools; no campaign, ad group or budget mutation tools are listed
  • Image path and video upload tools work only in local stdio mode
  • Connected LLM can see account data; the README warns of this
  • Firestore OAuth storage never deletes expired entries and needs a cleanup job

What it needs

  • no GPU
  • Docker
  • Needs Google Ads API, Google Cloud project, OAuth client or Application Default Credentials, pipx, Redis or Firestore (optional)
  • port 8080

Quick answers

Is google-ads-mcp open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Can you run google-ads-mcp with Docker?

Yes. Its repository has a Docker setup: a Dockerfile, a Compose file or a published image.

Does google-ads-mcp need a GPU?

No, it runs without one.

Also in MCP servers

See all 12
Also in MCP servers
RankProjectScore
1serversReference MCP servers for files, git, fetch, memory and time91.9k starscustom license94 out of 100
2apify-mcp-serverOfficial MCP server exposing Apify Store Actors as tools for web scraping15.7k stars+5,088 (+48%) in 30 daysMIT86 out of 100
3xiaohongshu-mcpMCP server that lets AI clients post, search and comment on Xiaohongshu17.1k stars+912 (+5.6%) in 30 daysApache-2.085 out of 100
#4ha-mcpMCP server that lets AI assistants configure and control Home Assistant7.1k starsMIT80 out of 100
#5mcp-atlassianMCP server exposing Jira and Confluence tools to AI assistants6.1k stars+140 (+2.3%) in 30 daysMIT69 out of 100