Skip to content
Grok

ads mcp for Grok

io.github.gudlab/ads-mcp

MCP server for Google Ads and Meta Ads. Wraps both APIs directly to manage campaigns.

client:Grok transport:stdio runtime:npm

Install ads mcp in Grok

.mcp.json (in your project root)

Held in this page only — never stored, logged, or sent anywhere but back to your screen.

{
  "mcpServers": {
    "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_DEVELOPER_TOKEN": "<GOOGLE_ADS_DEVELOPER_TOKEN>",
        "GOOGLE_ADS_REFRESH_TOKEN": "<GOOGLE_ADS_REFRESH_TOKEN>",
        "GOOGLE_ADS_CUSTOMER_ID": "<GOOGLE_ADS_CUSTOMER_ID>",
        "GOOGLE_ADS_LOGIN_CUSTOMER_ID": "<GOOGLE_ADS_LOGIN_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>"
      }
    }
  }
}

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

ads mcp in other clients