Google Ads MCP runs on your own machine — the client starts it, so there is no endpoint to ping.
Google Ads MCP server: GAQL queries, performance reports and campaign management.
Nothing serious here today
Today is the operative word: we check Google Ads MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add google-ads-mcp -e 'GOOGLE_ADS_DEVELOPER_TOKEN=<GOOGLE_ADS_DEVELOPER_TOKEN>' -e 'GOOGLE_OAUTH_CLIENT_ID=<GOOGLE_OAUTH_CLIENT_ID>' -e 'GOOGLE_OAUTH_CLIENT_SECRET=<GOOGLE_OAUTH_CLIENT_SECRET>' -e 'GOOGLE_OAUTH_REFRESH_TOKEN=<GOOGLE_OAUTH_REFRESH_TOKEN>' -- npx -y @renzo.johnson/google-ads-mcp{
"mcpServers": {
"google-ads-mcp": {
"command": "npx",
"args": [
"-y",
"@renzo.johnson/google-ads-mcp"
],
"env": {
"GOOGLE_ADS_DEVELOPER_TOKEN": "<GOOGLE_ADS_DEVELOPER_TOKEN>",
"GOOGLE_OAUTH_CLIENT_ID": "<GOOGLE_OAUTH_CLIENT_ID>",
"GOOGLE_OAUTH_CLIENT_SECRET": "<GOOGLE_OAUTH_CLIENT_SECRET>",
"GOOGLE_OAUTH_REFRESH_TOKEN": "<GOOGLE_OAUTH_REFRESH_TOKEN>"
}
}
}
}[mcp_servers.google-ads-mcp]
command = "npx"
args = ["-y", "@renzo.johnson/google-ads-mcp"]
env = { GOOGLE_ADS_DEVELOPER_TOKEN = "<GOOGLE_ADS_DEVELOPER_TOKEN>", GOOGLE_OAUTH_CLIENT_ID = "<GOOGLE_OAUTH_CLIENT_ID>", GOOGLE_OAUTH_CLIENT_SECRET = "<GOOGLE_OAUTH_CLIENT_SECRET>", GOOGLE_OAUTH_REFRESH_TOKEN = "<GOOGLE_OAUTH_REFRESH_TOKEN>" }{
"mcpServers": {
"google-ads-mcp": {
"command": "npx",
"args": [
"-y",
"@renzo.johnson/google-ads-mcp"
],
"env": {
"GOOGLE_ADS_DEVELOPER_TOKEN": "<GOOGLE_ADS_DEVELOPER_TOKEN>",
"GOOGLE_OAUTH_CLIENT_ID": "<GOOGLE_OAUTH_CLIENT_ID>",
"GOOGLE_OAUTH_CLIENT_SECRET": "<GOOGLE_OAUTH_CLIENT_SECRET>",
"GOOGLE_OAUTH_REFRESH_TOKEN": "<GOOGLE_OAUTH_REFRESH_TOKEN>"
}
}
}
}{
"servers": {
"google-ads-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@renzo.johnson/google-ads-mcp"
],
"env": {
"GOOGLE_ADS_DEVELOPER_TOKEN": "<GOOGLE_ADS_DEVELOPER_TOKEN>",
"GOOGLE_OAUTH_CLIENT_ID": "<GOOGLE_OAUTH_CLIENT_ID>",
"GOOGLE_OAUTH_CLIENT_SECRET": "<GOOGLE_OAUTH_CLIENT_SECRET>",
"GOOGLE_OAUTH_REFRESH_TOKEN": "<GOOGLE_OAUTH_REFRESH_TOKEN>"
}
}
}
}Put your own values in place of
<GOOGLE_ADS_DEVELOPER_TOKEN> (Google Ads API developer token), <GOOGLE_OAUTH_CLIENT_ID> (OAuth client ID. Set together with the client secret and refresh token), <GOOGLE_OAUTH_CLIENT_SECRET> (OAuth client secret), <GOOGLE_OAUTH_REFRESH_TOKEN> (OAuth refresh token with the Google Ads scope).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
GOOGLE_ADS_LOGIN_CUSTOMER_ID (Manager (MCC) account ID, digits only, when you access accounts through a manager), GOOGLE_ADS_DEFAULT_CUSTOMER_ID (Account used when a tool call names none).
Alternatives to Google Ads MCP
same job, measured the same wayMCP server for Google Ads campaign and budget management
Unofficial MCP server for Google Ads: reporting plus safe draft/confirm campaign management.
Full Google Ads management: read (campaigns, performance, ROAS, keywords, search terms) and write (p
Google Ads MCP server — manage campaigns, keywords, and metrics.
Multi-account Google Ads MCP: campaigns, keywords, search terms, and ad performance.
Google & Meta Ads management with 100+ tools. Audit, create, and optimize campaigns.
MCP server for Google Ads and Meta Ads. Wraps both APIs directly to manage campaigns.
Open-source MCP server for Google Ads & Meta Ads — manage campaigns from any AI assistant.
Google Ads MCP — questions
Answers built from our own checks of this server.