Install Google Ads MCP in Codex
What you need first
- Codex, installed.
- uv, which
gives the
uvxcommand the server starts with. - Your own values for
YOUR_GOOGLE_ADS_DEVELOPER_TOKEN,YOUR_GOOGLE_ADS_CLIENT_ID,YOUR_GOOGLE_ADS_CLIENT_SECRET,YOUR_GOOGLE_ADS_REFRESH_TOKEN,YOUR_GOOGLE_ADS_LOGIN_CUSTOMER_ID.
Steps
- Run this in a terminal. It writes the server into
~/.codex/config.toml, which the Codex CLI, its IDE extension and the ChatGPT desktop app share.
codex mcp add google-ads-mcp --env GOOGLE_ADS_DEVELOPER_TOKEN=YOUR_GOOGLE_ADS_DEVELOPER_TOKEN --env GOOGLE_ADS_CLIENT_ID=YOUR_GOOGLE_ADS_CLIENT_ID --env GOOGLE_ADS_CLIENT_SECRET=YOUR_GOOGLE_ADS_CLIENT_SECRET --env GOOGLE_ADS_REFRESH_TOKEN=YOUR_GOOGLE_ADS_REFRESH_TOKEN --env GOOGLE_ADS_LOGIN_CUSTOMER_ID=YOUR_GOOGLE_ADS_LOGIN_CUSTOMER_ID -- uvx scalably-google-ads-mcp==1.0.1 - Replace
YOUR_GOOGLE_ADS_DEVELOPER_TOKEN,YOUR_GOOGLE_ADS_CLIENT_ID,YOUR_GOOGLE_ADS_CLIENT_SECRET,YOUR_GOOGLE_ADS_REFRESH_TOKEN,YOUR_GOOGLE_ADS_LOGIN_CUSTOMER_IDwith your own values. - Start Codex again and type
/mcp: the server is listed.
Check it worked
Ask Codex: List the tools of google-ads-mcp.
If it does not start
- spawn uvx ENOENT
- uv is not on the PATH that Codex sees. Install it, or write the
full path of
uvxin the config. - The server starts, but its tools fail
- A
YOUR_…placeholder is still in the config, or its value is wrong.