ADS Beast for AI assistants
Connect Any MCP client to ADS Beast
Any client that speaks MCP over HTTP and can send a request header connects the same way. The two commands below check the server without any client.
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.
What the client needs
- 1Transport: Streamable HTTP. The URL is
https://adsbeast.pro/api/mcp/workspacefor your account andhttps://adsbeast.pro/api/mcpfor the open tools. - 2Header:
Authorization: Bearer absk_your_key.X-API-Key: absk_your_keyworks as well. - 3Many clients accept the JSON below as is. A client that only starts local programs can go through the
mcp-remotebridge.
{
"mcpServers": {
"adsbeast": {
"type": "http",
"url": "https://adsbeast.pro/api/mcp/workspace",
"headers": {
"Authorization": "Bearer absk_your_key"
}
}
}
}Check the server by hand
- 1The first command prints the tool list and needs no key.
- 2The second calls
whoamiwith your key and returns the organization and the scopes of the key.
macOS, Linux
curl -s https://adsbeast.pro/api/mcp/workspace \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Windows PowerShell
(Invoke-RestMethod -Method Post -Uri https://adsbeast.pro/api/mcp/workspace -ContentType "application/json" -Body '{"jsonrpc":"2.0","id":1,"method":"tools/list"}').result.tools.namemacOS, Linux
curl -s https://adsbeast.pro/api/mcp/workspace \
-H "Content-Type: application/json" \
-H "Authorization: Bearer absk_your_key" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"whoami","arguments":{}}}'Windows PowerShell
(Invoke-RestMethod -Method Post -Uri https://adsbeast.pro/api/mcp/workspace -ContentType "application/json" -Headers @{ Authorization = "Bearer absk_your_key" } -Body '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"whoami","arguments":{}}}').result.structuredContent | ConvertTo-Json -Depth 5First 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