Other · Local MCP server
Google Ads Manager MCP
Unofficial MCP server for Google Ads: reporting plus safe draft/confirm campaign management.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.AleemHaider/google-ads-manager-mcp- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-08-13
- Updated
- 2026-08-13
- Publisher
- AleemHaider (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/AleemHaider) · how
- Repository
- github.com/AleemHaider/google-ads-manager-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | google-ads-manager-mcp | 1.0.0 | stdio |
How to connect Google Ads Manager MCP
Google Ads Manager MCP runs locally from a Node.js package published to the npm registry: google-ads-manager-mcp version 1.0.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y google-ads-manager-mcp@1.0.0. It reads these environment variables: GOOGLE_ADS_CLIENT_ID (required), GOOGLE_ADS_CLIENT_SECRET (required, secret), GOOGLE_ADS_DEVELOPER_TOKEN (required, secret), GOOGLE_ADS_REFRESH_TOKEN (required, secret), GOOGLE_ADS_CUSTOMER_ID (required) and GOOGLE_ADS_LOGIN_CUSTOMER_ID; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"google-ads-manager-mcp": {
"command": "npx",
"args": [
"-y",
"google-ads-manager-mcp@1.0.0"
],
"env": {
"GOOGLE_ADS_CLIENT_ID": "<value>",
"GOOGLE_ADS_CLIENT_SECRET": "<secret>",
"GOOGLE_ADS_DEVELOPER_TOKEN": "<secret>",
"GOOGLE_ADS_REFRESH_TOKEN": "<secret>",
"GOOGLE_ADS_CUSTOMER_ID": "<value>",
"GOOGLE_ADS_LOGIN_CUSTOMER_ID": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Google AdsGoogle Ads reporting and campaign management. Everything it creates starts paused. | Remote · HTTPLive check: sign-in required |
| Google AdsGoogle Ads MCP server: 35 read tools, 10 opt-in preview-first writes. | Local · stdio |
| Google AdsGoogle Ads MCP with MCC support: 35 tools for campaigns, keywords, reporting, GAQL. | Local · stdio |
| Google AdsMCP server for Google Ads - 22 tools for spend diagnosis, impression share, and asset performance. | Local · stdio |
| Google Ads MCPGoogle Ads MCP: GAQL queries, resources, recommendations, keyword ideas, change history. 11 tools. | Local · stdio |
| Google Ads MCP by AdPlugGoogle Ads MCP server: 16 tools for reporting, campaigns, keywords, assets. Writes preview first. | Remote · HTTPLive check: sign-in required |
| Google Ads MCP ServerGoogle Ads management - campaign writes, GAQL reporting, bulk mutate, validation, and previews. | Remote & Local · HTTP, stdio |
| Google Business Profile MCPMCP server for Google Business Profile: locations, reviews, local posts and performance metrics. | Local · stdio |