Bubi Ads

AI ad manager for local businesses. Plan, draft and analyze Meta (Facebook/Instagram), Google Ads, TikTok Ads and ChatGPT Ads campaigns from Claude, ChatGPT or any MCP client. Remote server with OAuth; publishing always needs the user's approval in Bubi Ads.

Hosted MCP Server

npx add-mcp 'https://bubiads.com/mcp'

Installs into Claude Code, Codex, Cursor and more

Documentation

If you already use Claude for your daily work, keeping an eye on your ads from the same chat is handy. Bubi Ads uses the Model Context Protocol (MCP) standard for this: Claude calls the tools Bubi Ads provides, with your permission. Your data, ad accounts and approval rules stay in Bubi Ads; Claude only sees and does as much as you allow on your account.

How does the connection work?

The Bubi Ads MCP server is a stateless remote server running over Streamable HTTP. When Claude connects, it is sent to Bubi Ads’ own OAuth 2.1 authorization screen; PKCE is required, and the token issued is only valid for this MCP server. Access tokens are short-lived, and the refresh token changes every time it’s used. You can remove the connection at any time in Bubi Ads under Settings › AI assistants.

There are two permission scopes: ads:read for viewing, and ads:write for creating drafts, suggestions, workflows and automations. If you switch off write access on the permission screen, Claude can only read.

Why aren’t approvals in Claude?

In Bubi Ads, every action that starts or changes spend needs human approval, and that rule is built into the code’s structure. If actions like publishing, pausing, resuming or approving a suggestion come from an AI context, the engine rejects them, which is why they aren’t in the MCP tool list either. When Claude prepares a campaign, it gives you an approval link. You open it, check the card, and the campaign goes live only if you approve. Every action Claude takes is recorded in the campaign history as “Assistant”.

Usage limits

Workflows run by the specialist agents (such as campaign drafts, reports and creative refreshes) count toward your plan’s monthly workflow allowance. To prevent abuse, each user can also make at most 120 tool calls per 10 minutes. Read tools are fast; tools that run an agent can take 20–60 seconds.

Tools other than Claude

Claude Code, Cursor, VS Code and other clients that support MCP can connect to the same server. For clients configured with a header, you can create and revoke a personal access key in Bubi Ads. For ChatGPT, see our separate page on managing ads with ChatGPT.

Frequently asked questions

Can Claude publish ads on my behalf?

No. Publishing, pausing, resuming and approving suggestions aren’t among the MCP tools, and the engine rejects them if they come from AI. Claude gives you an approval link; you start the campaign yourself in Bubi Ads.

Do I need an access key to connect?

Not for Claude (claude.ai, desktop and mobile); you sign in with your Bubi Ads account and grant permission while connecting. In Claude Code you also grant access in the browser. For header-configured tools like Cursor and VS Code, you can create a personal access key.

What data can Claude see?

When it calls the tools, it can see data in your Bubi Ads account such as your business profile, an overview of connected ad accounts, campaigns, metrics, suggestions, automations and competitor analyses. It can’t access accounts that aren’t connected.

How do I remove the connection?

In Bubi Ads, Settings › AI assistants lists your connected assistants and keys, and you can remove any of them with one click. You can also delete the connector on the Claude side.

Which ad platforms does it work with?

With the Meta, Google Ads, TikTok Ads and ChatGPT Ads accounts you’ve connected to Bubi Ads. Claude doesn’t reach those accounts directly; it goes through Bubi Ads.