Ads MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 42 installs a week from npm. Last commit 24 Oct 2026.
MCP server for Google Ads and Meta Ads. Wraps both APIs directly to manage campaigns.
Today is the operative word: we check 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.
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 ads-mcp -e 'GOOGLE_ADS_CLIENT_ID=<GOOGLE_ADS_CLIENT_ID>' -e 'GOOGLE_ADS_CLIENT_SECRET=<GOOGLE_ADS_CLIENT_SECRET>' -e 'GOOGLE_ADS_DEVELOPER_TOKEN=<GOOGLE_ADS_DEVELOPER_TOKEN>' -e 'GOOGLE_ADS_REFRESH_TOKEN=<GOOGLE_ADS_REFRESH_TOKEN>' -e 'GOOGLE_ADS_CUSTOMER_ID=<GOOGLE_ADS_CUSTOMER_ID>' -e 'META_APP_ID=<META_APP_ID>' -e 'META_APP_SECRET=<META_APP_SECRET>' -e 'META_ACCESS_TOKEN=<META_ACCESS_TOKEN>' -e 'META_AD_ACCOUNT_ID=<META_AD_ACCOUNT_ID>' -- npx -y @gudlab/ads-mcp
{
"mcpServers": {
"ads-mcp": {
"command": "npx",
"args": [
"-y",
"@gudlab/ads-mcp"
],
"env": {
"GOOGLE_ADS_CLIENT_ID": "<GOOGLE_ADS_CLIENT_ID>",
"GOOGLE_ADS_CLIENT_SECRET": "<GOOGLE_ADS_CLIENT_SECRET>",
"GOOGLE_ADS_CUSTOMER_ID": "<GOOGLE_ADS_CUSTOMER_ID>",
"GOOGLE_ADS_DEVELOPER_TOKEN": "<GOOGLE_ADS_DEVELOPER_TOKEN>",
"GOOGLE_ADS_REFRESH_TOKEN": "<GOOGLE_ADS_REFRESH_TOKEN>",
"META_ACCESS_TOKEN": "<META_ACCESS_TOKEN>",
"META_AD_ACCOUNT_ID": "<META_AD_ACCOUNT_ID>",
"META_APP_ID": "<META_APP_ID>",
"META_APP_SECRET": "<META_APP_SECRET>"
}
}
}
}
[mcp_servers.ads-mcp]
command = "npx"
args = ["-y", "@gudlab/ads-mcp"]
env = { GOOGLE_ADS_CLIENT_ID = "<GOOGLE_ADS_CLIENT_ID>", GOOGLE_ADS_CLIENT_SECRET = "<GOOGLE_ADS_CLIENT_SECRET>", GOOGLE_ADS_DEVELOPER_TOKEN = "<GOOGLE_ADS_DEVELOPER_TOKEN>", GOOGLE_ADS_REFRESH_TOKEN = "<GOOGLE_ADS_REFRESH_TOKEN>", GOOGLE_ADS_CUSTOMER_ID = "<GOOGLE_ADS_CUSTOMER_ID>", META_APP_ID = "<META_APP_ID>", META_APP_SECRET = "<META_APP_SECRET>", META_ACCESS_TOKEN = "<META_ACCESS_TOKEN>", META_AD_ACCOUNT_ID = "<META_AD_ACCOUNT_ID>" }
{
"mcpServers": {
"ads-mcp": {
"command": "npx",
"args": [
"-y",
"@gudlab/ads-mcp"
],
"env": {
"GOOGLE_ADS_CLIENT_ID": "<GOOGLE_ADS_CLIENT_ID>",
"GOOGLE_ADS_CLIENT_SECRET": "<GOOGLE_ADS_CLIENT_SECRET>",
"GOOGLE_ADS_CUSTOMER_ID": "<GOOGLE_ADS_CUSTOMER_ID>",
"GOOGLE_ADS_DEVELOPER_TOKEN": "<GOOGLE_ADS_DEVELOPER_TOKEN>",
"GOOGLE_ADS_REFRESH_TOKEN": "<GOOGLE_ADS_REFRESH_TOKEN>",
"META_ACCESS_TOKEN": "<META_ACCESS_TOKEN>",
"META_AD_ACCOUNT_ID": "<META_AD_ACCOUNT_ID>",
"META_APP_ID": "<META_APP_ID>",
"META_APP_SECRET": "<META_APP_SECRET>"
}
}
}
}
{
"servers": {
"ads-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@gudlab/ads-mcp"
],
"env": {
"GOOGLE_ADS_CLIENT_ID": "<GOOGLE_ADS_CLIENT_ID>",
"GOOGLE_ADS_CLIENT_SECRET": "<GOOGLE_ADS_CLIENT_SECRET>",
"GOOGLE_ADS_CUSTOMER_ID": "<GOOGLE_ADS_CUSTOMER_ID>",
"GOOGLE_ADS_DEVELOPER_TOKEN": "<GOOGLE_ADS_DEVELOPER_TOKEN>",
"GOOGLE_ADS_REFRESH_TOKEN": "<GOOGLE_ADS_REFRESH_TOKEN>",
"META_ACCESS_TOKEN": "<META_ACCESS_TOKEN>",
"META_AD_ACCOUNT_ID": "<META_AD_ACCOUNT_ID>",
"META_APP_ID": "<META_APP_ID>",
"META_APP_SECRET": "<META_APP_SECRET>"
}
}
}
}
Put your own values in place of
<GOOGLE_ADS_CLIENT_ID> (OAuth client ID from Google Cloud Console), <GOOGLE_ADS_CLIENT_SECRET> (OAuth client secret from Google Cloud Console), <GOOGLE_ADS_DEVELOPER_TOKEN> (Developer token from Google Ads API Center), <GOOGLE_ADS_REFRESH_TOKEN> (Refresh token minted via `pnpm google:auth`), <GOOGLE_ADS_CUSTOMER_ID> (Default Google Ads account ID, 10 digits, no dashes), <META_APP_ID> (Meta App ID from developers.facebook.com), <META_APP_SECRET> (Meta App secret), <META_ACCESS_TOKEN> (Long-lived System User access token with ads_management scope), <META_AD_ACCOUNT_ID> (Default Meta ad account ID, numeric, no act_ prefix).
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 (MCC account ID, only if the customer account is managed under one).
MCP server for Google Ads campaign and budget management
Google Ads MCP server — manage campaigns, keywords, and metrics.
Open-source MCP server for Google Ads & Meta Ads — manage campaigns from any AI assistant.
Google & Meta Ads management with 100+ tools. Audit, create, and optimize campaigns.
Ads MCP for Meta, Google Ads, TikTok, Snapchat and LinkedIn: stage launches and manage campaigns.
Google Ads management for AI agents — diagnose, optimize, and manage campaigns.
18 Google Maps tools for AI agents — geocode, search, directions, weather, and more.
MCP server for the Google Forms API: create forms, manage questions, read responses and watches.
Answers built from our own checks of this server.