The Model Context Protocol made it possible to plug real data straight into Claude, ChatGPT and every other assistant that speaks it. Cinble runs the servers for the ad platforms, so connecting your accounts is a URL rather than a project.
The servers
Meta Ads MCP
meta-ads.mcp.cinble.comCampaigns, ad sets, ads, creative performance and insights, with period comparisons already computed.
Set it up → Live in early accessGoogle Ads MCP
google-ads.mcp.cinble.comCampaigns, ad groups, keywords, the search terms report and read-only GAQL, without the developer token wait.
Set it up →
Planned: TikTok Ads, LinkedIn Ads, X Ads and Snapchat, on the same
platform.mcp.cinble.com pattern.
What MCP is, in one minute
MCP is an open standard, introduced by Anthropic in late 2024 and adopted across the industry since, that defines how an AI assistant talks to external tools. An MCP server publishes tools such as "list campaigns" or "get insights for a date range", and the assistant decides when to call them while answering you.
For advertising that means no more exporting a report, pasting it into a chat and hoping the assistant reads the columns right. You ask, it fetches, it answers with the live numbers.
Why use ours instead of running your own
Open-source ad MCP servers exist and they are a reasonable choice if you want to own the process end to end. What you take on is everything around the protocol:
| Self-hosted | Cinble hosted | |
|---|---|---|
| Platform API access | Your own developer app, plus Google's developer token approval | Ours, already approved |
| Credentials | You generate, store and renew them | OAuth on your side, nothing to store |
| Rate limits | Yours to stay inside | Pooled and managed |
| Hosting | A process you keep alive | None |
| Multiple platforms | One server each, configured separately | Same pattern, same account, same panel |
And then there is the copilot
An MCP connection answers whatever you think to ask. It is excellent for exploration, and it runs only while you are in the chat. The part it cannot do is watch the account when you are not looking.
That is the rest of Cinble: a copilot that consolidates every connected Google Ads and Meta Ads account into one panel, reads their history and puts budget moves in front of you ranked by impact, with the numbers and the reasoning attached. It never touches your account on its own. Both halves read the same connected accounts, so you explore in your assistant and let the panel keep watch between sessions.
Get your servers enabled
Early access is opening in batches, free while it lasts. Join the waitlist and we will turn on the MCP servers and the copilot together.
Join the waitlist ↗Frequently asked questions
What is MCP?
The Model Context Protocol is an open standard that defines how AI assistants call external tools and data sources. A server publishes tools; the assistant calls them while answering you. Cinble runs the servers for ad platforms.
Which platforms are covered?
Meta Ads and Google Ads in early access. TikTok Ads, LinkedIn Ads, X Ads and Snapchat are planned, on the same subdomain pattern.
Do I need API tokens?
No. Cinble runs the developer apps and holds the approved credentials, the Google Ads developer token included. You authorize your accounts through each platform's own login screen and connect your assistant with a URL.
Can an assistant change my campaigns?
Not during early access. Both servers ship read-only. Write tools are planned later as an explicit per-account opt-in with a confirmation step.
Which clients work?
Anything that speaks MCP over HTTP: Claude on web and desktop, Claude Code, ChatGPT, Cursor, VS Code, and custom agents built with an MCP-compatible SDK.