Cookies

We use cookies to sign you in (required) and for analytics (optional). More - Privacy Policy.

ADS Beast for AI assistants

Connect Codex to ADS Beast

Codex keeps MCP servers in `~/.codex/config.toml` and reads the key from an environment variable you name.

First, create an API key

  1. 1Sign in to ADS Beast and open API keys in the menu. Creating a key needs the administrator role.
  2. 2Create a key with only the scopes the assistant needs. read:* is enough to look at data. Add write:proposals to let it propose changes and build campaign drafts, and write:leads to let it update leads.
  3. 3Copy the key that starts with absk_. It is shown once. You revoke it on the same screen, and a revoked key stops working at once.

Add the server with a key

  1. 1Put the key into an environment variable that stays after a restart, then open a new terminal.
  2. 2Run the codex mcp add command, or write the same block into ~/.codex/config.toml by hand.
  3. 3Run codex mcp list to check that adsbeast is there, then start Codex.
macOS, Linux
echo 'export ADSBEAST_API_KEY=absk_your_key' >> ~/.zshrc   # or ~/.bashrc
Windows PowerShell
[Environment]::SetEnvironmentVariable("ADSBEAST_API_KEY", "absk_your_key", "User")
codex mcp add adsbeast --url https://adsbeast.pro/api/mcp/workspace --bearer-token-env-var ADSBEAST_API_KEY
File: ~/.codex/config.toml
[mcp_servers.adsbeast]
url = "https://adsbeast.pro/api/mcp/workspace"
bearer_token_env_var = "ADSBEAST_API_KEY"

Or install the plugin

  1. 1The plugin adds the workflow skills (account audit, wasted spend, weekly report and more) on top of the server.
  2. 2A Codex plugin cannot carry the key, so run the codex mcp add command above as well, with the same name adsbeast. Without it the tools answer 401 and say what is missing.
codex plugin marketplace add notformal/adsbeast-plugins
codex plugin add adsbeast@adsbeast-plugins

Sign-in without a key (OAuth) is built, but it is not switched on in production yet. The steps that need it will appear here when it is switched on.

We ran these commands in Codex CLI and read the config it saved. We did not sign in to Codex, so we did not call a tool from inside it.

First prompts to try

  • Call whoami in ADS Beast and tell me which organization and scopes this connection has.
  • Show the campaign dashboard summary and the unread alerts.
  • Check this Google Ads headline against the platform limits: "Plumber in Bratislava, same day".

If it does not work

  • A 401 answer means the key is missing, mistyped or revoked. The handshake and the tool list answer without a key, so a client can show the tools and still fail on the first call.
  • A 403 in the answer means the key lacks the scope that tool needs. The whoami tool lists the scopes the key carries.
  • No tools after you edit a config file: restart the client or reload its MCP servers.

We ran the commands on this page ourselves on November 18, 2026, on a clean configuration, with a scoped key, against production. Vendor documentation