Marxx MCP
Your Meta and Google ad accounts, inside Claude.
Connect once. Ask about spend, creative and competitors in plain English, and get the answer in the chat.
Server URL
https://api.marxx.ai/mcp
The URL is the whole setup. Your assistant hands you off to Marxx, you approve the connection there, and the tools appear in the chat.
- OAuth, no keys to paste
- Read-only
Setup
Connected in about two minutes.
One server covers both ad platforms and every workspace you belong to. You do this once, not once per account.
Connect Meta and Google Ads to Marxx
The server reads the accounts Marxx already indexes, so the workspace comes first. Both Meta and Google Ads authorise over OAuth on read scopes, so nothing in either account can be changed from the connection.
Paste the URL as a custom connector
In Claude, add a custom connector under Settings. In ChatGPT, add it as a connector. The URL is the only thing you enter: there is no config file to edit and no key to paste anywhere.
Approve the connection on Marxx
The assistant hands you off to Marxx over OAuth. You sign in with your own Marxx account and approve the connection there, so no credential is ever typed into the assistant or stored in its settings.
Pick the workspace
Agencies running client-isolated workspaces scope the session to one client before asking anything. The assistant does this itself with marxx_select_workspace, so a question about one client cannot read another's spend.
Ask in plain English
Ask what changed last week, which hook is fatiguing, or what a competitor shipped. The assistant picks the tools, and the answer arrives in the thread with the numbers behind it.
Step one needs a workspace. That is the call.
In thirty minutes we connect one Meta or Google account with you, turn the connector on, and you ask it your first question live. Read-only throughout, nothing is published to your account, and you keep whatever the call produces.
Both platforms, read through the same tools.
Marxx already indexes the accounts for the app. The MCP server hands an assistant that same index, so nothing has to be re-ingested per question.
Meta Ads
Full creative history, not the last thirty days. Video, static and carousel parsed into hooks, formats, angles and offers, with spend, CPA and frequency attached to each one.
Google Ads
Campaign structure, budgets and spend alongside the creative, so a question about rising CPA can be answered across both platforms instead of one at a time.
Tools
Twenty tools the assistant picks from.
You never call these by name. They are listed because knowing what a connector can reach is the difference between trusting it and guessing.
Your accounts
Meta and Google Ads spend, creative and structure, read straight from the connected accounts.
- marxx_my_ad_accounts
- marxx_my_ads_overview
- marxx_my_ads
- marxx_ad_detail_by_id
- marxx_account_audit
- marxx_performance_brief
- marxx_select_workspace
Competitors
Live creative from any brand you track, plus the teardown Marxx runs on it. No connection needed on their side.
- marxx_tracked_competitors
- marxx_competitor_ad_fetcher
- marxx_competitor_creative_intelligence
- marxx_brand_teardown
- marxx_saved_ads
Trends and gaps
What your category is running now, and the list of angles your account has never tested.
- marxx_trending_tactics
- marxx_trend_tactic_detail
- marxx_creative_gap_recommendations
Brand and audience
The positioning, claims and constraints a generated script has to stay inside, and who it is speaking to.
- marxx_brand_knowledge
- marxx_brand_assets
- marxx_products
- marxx_audience_personas
- marxx_persona_voice_of_customer
Read-only, by scope
Nothing in the tool surface writes back to Meta or Google. An assistant cannot pause a campaign or move a budget through it.
Scoped to one workspace
Agency sessions answer inside a single client at a time, so one client's question cannot reach another client's account.
What people actually ask it.
Why not just point Claude at the ad platforms?
Platform MCPs answer about ad IDs
Meta's and Google's own endpoints hand back rows keyed to campaign and ad IDs. Marxx rolls the same spend up by hook, angle, format and offer, so the answer is a creative decision you can repeat rather than an identifier you cannot.
One thread, both platforms
Meta and Google sit behind the same tools, so a question that spans them is one question. No swapping servers mid-conversation and no reconciling two answers by hand afterwards.
It can see outside your account
No ad API can tell you what a competitor is running. The tracked-competitor tools carry live creative from brands you do not own, scored on the same axis as your own, which is the half of the picture an account-only connection never has.
Marxx MCP, answered.
How do I connect Claude to my Google Ads and Meta Ads accounts?
Connect the ad accounts inside Marxx first, then add https://api.marxx.ai/mcp to Claude as a custom connector. That URL is the only thing you enter. Claude hands you off to Marxx over OAuth, you approve the connection there, and it then covers every account in the workspaces you belong to, on both Meta and Google Ads.
Does it work in ChatGPT and other assistants?
Yes. Marxx runs a standard hosted MCP server with OAuth, so any client that supports remote MCP servers can use it. Claude and ChatGPT are the two we test against every release; Cursor, VS Code and the rest take the same URL and the same approval flow.
Can it change or pause my campaigns?
No. The MCP tools are read-only. Both ad platforms authorise on read scopes and nothing in the tool surface writes back, so an assistant cannot pause a campaign, move a budget or edit an ad through this connection. Publishing to Meta happens in the Marxx app, behind an approval.
What does it send to the model?
Only the results of the tool the assistant called. Chart data is compacted before it is sent, into the totals, shares, trends and outliers each chart exists to show, because a model reading tens of thousands of raw points can only guess at the shape.
How do agencies keep clients separate?
Each client is its own workspace in Marxx, and the session is scoped to one workspace at a time. An assistant working on one client's question cannot read another client's spend, creative or competitors.
How do I disconnect it?
Revoke the connector in Marxx and the server stops answering, whether or not the assistant still has it configured. Removing it on the assistant's side alone is the weaker of the two, so do it in Marxx.
Which plan includes the MCP server?
The Marxx MCP server and the Slack bot ship on the same plans. See pricing for what each tier includes.
One size fits none. Let’s build your exact setup.
Hop on a call with our founder to see real-world use cases, cut out the noise, and isolate the exact tools that drive results for your business — complete with a personalized pricing plan.