ADS Beast for AI assistants
Connect Gemini CLI to ADS Beast
Gemini CLI connects to a remote server over HTTP and sends the key as a header.
First, create an API key
- 1Sign in to ADS Beast and open API keys in the menu. Creating a key needs the administrator role.
- 2Create a key with only the scopes the assistant needs.
read:*is enough to look at data. Addwrite:proposalsto let it propose changes and build campaign drafts, andwrite:leadsto let it update leads. - 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
- 1Run the command with your key in place of
absk_your_key, or add the block to~/.gemini/settings.jsonby hand. The block is what the command writes. - 2The key is stored in that settings file as plain text. Keep the file private and do not commit it.
- 3Start Gemini CLI in a folder you trust and run
/mcp. The server and its tools are listed. In a folder that is not trusted, Gemini CLI shows the server as disabled.
gemini mcp add --transport http --scope user --header "Authorization: Bearer absk_your_key" adsbeast https://adsbeast.pro/api/mcp/workspaceFile:
~/.gemini/settings.json{
"mcpServers": {
"adsbeast": {
"url": "https://adsbeast.pro/api/mcp/workspace",
"type": "http",
"headers": {
"Authorization": "Bearer absk_your_key"
}
}
}
}Or install the extension
- 1The extension adds the server, the open ad spec tools and the workflow commands. It asks for the key during install and keeps it in the
ADSBEAST_API_KEYsetting.
gemini extensions install https://github.com/notformal/adsbeast-pluginsWe have not tested other Google command-line clients.
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
whoamitool 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