ADS Beast for AI assistants
Connect Cursor to ADS Beast
Cursor reads MCP servers from a JSON file and can send the key as a request 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
- 1Open
~/.cursor/mcp.jsonto have the server in every project, or.cursor/mcp.jsoninside one project. Create the file if it is missing. - 2Paste the snippet. It takes the key from the
ADSBEAST_API_KEYenvironment variable, which has to be set before the app starts. You can also write the key itself in place of${env:ADSBEAST_API_KEY}. - 3Open Customize in the Cursor sidebar and check that
adsbeastis on and shows its tools.
File:
~/.cursor/mcp.json{
"mcpServers": {
"adsbeast": {
"url": "https://adsbeast.pro/api/mcp/workspace",
"headers": {
"Authorization": "Bearer ${env:ADSBEAST_API_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.
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 Cursor 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