Google Ads MCP 服务器

Google Ads MCP Server

This repository contains a Google Ads MCP server that can run locally in Docker for Claude Desktop or remotely on AWS Lambda behind a Function URL.

What it needs

Local Docker setup requires these Google Ads variables:

• GOOGLE_ADS_DEVELOPER_TOKEN
• GOOGLE_ADS_CLIENT_ID
• GOOGLE_ADS_CLIENT_SECRET
• GOOGLE_ADS_REFRESH_TOKEN
• GOOGLE_ADS_LOGIN_CUSTOMER_ID if using a manager account

The full collection steps live in docs/local-variable-checklist.md.

Local Docker setup

1. Copy .env.example to .env.
2. Fill in the Google Ads values.
3. Start the container:

docker compose up --build

4. Point Claude Desktop to http://localhost:8080/mcp.

Windows Claude Desktop config path:

%APPDATA%\Claude\claude_desktop_config.json

Mac Claude Desktop config path:

~/Library/Application Support/Claude/claude_desktop_config.json

Config:

{
  "mcpServers": {
    "google-ads-local": {
      "url": "http://localhost:8080/mcp"
    }
  }
}

AWS deployment

The repo includes:

• deploy/aws/lambda-environment.example.json for Lambda environment variables
• CLIENT_CLAUDE_SETUP.md for client-facing setup instructions
• .github/workflows/deploy-development.yml for GitHub Actions deployment on development

Typical deploy flow:

1. Put Google Ads secrets in SSM Parameter Store.
2. Build and push the image to ECR.
3. Update the Lambda function to the new image.
4. Enable a Lambda Function URL.
5. Point Claude Desktop at https://YOUR-LAMBDA-URL.on.aws/mcp.

Workshop assets

• docs/local-variable-checklist.md
• CLIENT_CLAUDE_SETUP.md
• workshop/google-ads-mcp-setup-workshop.pptx

Notes

• .env is gitignored and should stay local.
• Docker Compose runs the same container image shape used by Lambda, but with local environment variables instead of SSM.
• The local Claude Desktop connector should use /mcp, not /sse.