
MCP Google Ads
io.github.Ayo-FamPublished by GitHub account Ayo-Famv0.1.0Updated Oct 24, 2026
Multi-account Google Ads MCP: campaigns, keywords, search terms, and ad performance.
Overview
Local MCP server that lets an assistant query multiple Google Ads accounts for campaigns, keywords, search terms and ad performance.
- What you can do
- List and route accounts: list accounts, set a default account, discover accessible customers
- Report spend: account summaries and period-over-period comparisons
- Analyze campaigns: list campaigns and get range-based campaign performance
- Inspect query-level detail: keyword performance, search-term reports and ad performance
- All queries run as GAQL calls against the Google Ads API with retries and normalized rows
- When to use it
- Useful when you manage several client or in-house Google Ads accounts and want one assistant session to switch between them without restarting the server, for reporting and performance analysis rather than editing campaigns.
- Requirements
- Runs locally as a Python package (mcp-google-ads-multi) installed via pip or run with uvx. Needs a Google Ads API developer token in GOOGLE_ADS_DEVELOPER_TOKEN and an accounts.json file, pointed to by GOOGLE_ADS_ACCOUNTS_CONFIG, holding OAuth or service-account credentials per account. Network access to the Google Ads API.
Installation
In SourceWeft
- Open MCP Google Ads in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mcp-google-ads
Multi-account Google Ads MCP server for operators who need one MCP surface across multiple client or in-house ad accounts without restarting the server.
Release posture: beta package, version 0.1.0 from pyproject.toml.
Choose your path
Architecture
Request flow
Quick start
- Install the package.
- Copy the accounts config template and add your accounts.
- Register it in your MCP client.
Available tools
Runtime proof
Repo map
Validation
License
MIT
Project context for new tasks
Use INDEX.md to find task-specific contracts; consult prompt.md when product direction is relevant. Historical examples do not select the current task.
Source: README.md at commit 93fe255
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts