Skip to main content
Glama
0-shiv

Google Ads Gateway MCP

by 0-shiv

Codex front door — MCP server

Wraps the Google Ads Gateway Worker as two Codex tools: list_accounts and run_gaql. Holds no Google credentials — just the Worker URL and the shared team token.

Per-laptop setup (each teammate, once)

Logging into the shared ChatGPT/Codex account does not carry this — MCP config is a local file. Each laptop does this once (~30 seconds):

cd <path-to>/google-ads-gateway/mcp
npm install

Then add the server to Codex's config. For Codex CLI, edit ~/.codex/config.toml:

[mcp_servers.google_ads]
command = "node"
args = ["/ABSOLUTE/PATH/TO/google-ads-gateway/mcp/index.js"]
env = { GADS_GATEWAY_URL = "https://google-ads-gateway.<subdomain>.workers.dev", GADS_GATEWAY_TOKEN = "<team token>" }

(For the IDE/desktop Codex, add the same command / args / env in its MCP settings UI.)

Restart Codex. Then in a session:

list my google ads accounts for ACI, pull cost, clicks and conversions by campaign for the last 30 days

Related MCP server: google-ads-mcp-server

Quick local test (without Codex)

GADS_GATEWAY_URL=https://google-ads-gateway.<subdomain>.workers.dev \
GADS_GATEWAY_TOKEN=<team token> \
npx @modelcontextprotocol/inspector node index.js
F
license - not found
-
quality - not tested
C
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/0-shiv/google-ads-gateway-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server