ADS Beast for AI assistants
Connect Claude Code to ADS Beast
One command adds the server. The plugin from our public repository adds the same server and a short connection skill.
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 in a terminal with your key in place of
absk_your_key. - 2By default the server is saved for you in the current project. Add
--scope userto have it in every project. - 3Start Claude Code and run
/mcp. The serveradsbeastis listed as connected.
claude mcp add --transport http adsbeast https://adsbeast.pro/api/mcp/workspace --header "Authorization: Bearer absk_your_key"Or share it with the team
- 1Put the snippet into
.mcp.jsonat the root of the repository. The key stays in theADSBEAST_API_KEYenvironment variable of each person, not in the file. Claude Code asks each person to approve the server the first time they start it in that repository.
File:
.mcp.json{
"mcpServers": {
"adsbeast": {
"type": "http",
"url": "https://adsbeast.pro/api/mcp/workspace",
"headers": {
"Authorization": "Bearer ${ADSBEAST_API_KEY}"
}
}
}
}Or install the plugin
- 1Run the two commands inside Claude Code. It then asks for the key. If it does not, run
/plugin configure adsbeast@adsbeast-plugins.
/plugin marketplace add notformal/adsbeast-plugins
/plugin install adsbeast@adsbeast-pluginsSign-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.
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