ADS Beast for AI assistants
Connect Claude to ADS Beast
Claude adds remote servers as custom connectors. Sending an API key from a connector is a beta that only some organizations have, so there are three ways and you pick the one your account offers.
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.
Open tools as a connector
- 1Open Customize, then Connectors, press Add and choose Add custom connector.
- 2Name it ADS Beast, paste
https://adsbeast.pro/api/mcp, continue and choose No sign-in. - 3Add it. In a chat press +, open Connectors and switch ADS Beast on.
Your account with a key in a request header
- 1Open Add custom connector again, paste
https://adsbeast.pro/api/mcp/workspace, continue and choose No sign-in. - 2Open Request headers (it can sit under Advanced), pick
authorizationand enterBearer absk_your_keywith your key. Claude adds no prefix, so the word Bearer goes in the value. - 3If the dialog has no Request headers section, your account does not have this beta. Use the desktop bridge below.
- 4Add the connector and switch it on in a chat, as in the steps above.
Claude Desktop through a local bridge
- 1Install Node.js 18 or newer. The bridge is the open-source
mcp-remotepackage, started bynpx. - 2In Claude Desktop open Settings from the Claude menu, then Developer, then Edit Config. Paste the snippet into
claude_desktop_config.jsonwith your key in place ofabsk_your_key. - 3Quit Claude Desktop completely and start it again. ADS Beast appears among the tools of a new chat.
claude_desktop_config.json{
"mcpServers": {
"adsbeast": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://adsbeast.pro/api/mcp/workspace",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer absk_your_key"
}
}
}
}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.
ADS Beast is not in the Claude connectors directory. You add it yourself by URL. On the Free plan Claude allows one custom connector, so pick the open tools or your account. On Team and Enterprise plans an owner adds it for the organization.
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 could not run Claude ourselves. The steps follow its documentation as read on November 18, 2026, and menus can change between versions. The server side was checked against production. Vendor documentation