MCP · Claude
Claude connector for Meta Ads
Query Meta Ads in plain language inside Claude — no cloud project, no token copying, no data storage. Ready in 3 clicks.
What is it?
A hosted MCP (Model Context Protocol) server that links Claude to Meta Ads, read-only. You (or your client) authorize the account via OAuth; Attaché handles the rest: authentication, token refresh, encryption, guardrails. No data is stored — requests pass through in real time.
Ready in 3 steps
- 1
Connect the account
One "Sign in" button, the platform's official OAuth. No password sharing.
- 2
Pick the resources
Tick the properties or accounts to expose. Everything else stays invisible.
- 3
Paste the URL into Claude
Settings → Connectors → custom connector. That's it.
Questions you can ask
"What is the ROAS of my prospecting vs retargeting campaigns?"
"Which audiences have the lowest CPM this month?"
"Break down creative fatigue: frequency and CTR per ad set."
Built for agencies: natively multi-client
A classic MCP connector is tied to one account: switching clients means disconnecting and re-authenticating every time. The Attaché master connector sees all your clients at once — you switch clients in the conversation, not in the settings.
MCP × Agencies →Do I need a cloud account or an API key?
No. Just the official OAuth button — Attaché carries all the infrastructure.
Is the data stored?
Never. Only encrypted OAuth tokens are kept (GDPR). One-click revocation.
Early access
Early access — free
Create your workspace now: no card asked, every feature, as many sites as you want.
Create my free workspaceAlready have access? Log in
Or leave your email to hear when the next platforms land — Meta Ads, TikTok Ads, Pinterest Ads, Strava:
Request received
A confirmation email is on its way. We will write as soon as your access is open — usually within a few days.