Atlas MCP is a remote MCP server that connects Claude — and any MCP-compatible assistant — to your Google Ads, Meta, GA4 and e-commerce performance data. Ask "how are my campaigns pacing this month?" and get exact, tenant-scoped numbers from Atlas Core. No dashboard tab required.
works with Claude · Claude Desktop · Cowork · any MCP client (Streamable HTTP)
Plugging four separate platform MCPs into your assistant means raw API responses flooding the context window — slow, token-hungry, and easy to get wrong. Atlas normalizes and joins your ad and commerce data first, then answers with compact, composed results.
Curated on purpose: a few tools with rich, composed output beat dozens of granular ones. Every tool is read-only and answers with exact figures from your connected sources.
Pacing vs. target plus the biggest movers, in one call. Your morning stand-up, answered before the coffee is poured.
Budget and revenue vs. target with daily breakdown and projection. "Are we on target this month?" — answered exactly.
Sessions, conversions, revenue and channel share across your channels, anchored to real commerce revenue.
Stalled campaigns, billing issues, metric deviations — ranked critical-first, then by revenue impact.
Which products and campaigns are rising or falling hardest, week over week, deduplicated per product.
Who changed what, when — a durable ledger of budget, bid, status and targeting changes across Google Ads and Meta.
Any core metric, two periods, exact deltas. This month vs. last, Q2 vs. Q1 — no spreadsheet needed.
Settings, budget, bid strategy and recent performance for a single campaign, in one call.
Atlas MCP is rolling out in a controlled way — every organization is verified personally before activation. Request access and we'll set up your organization and data sources.
Add Atlas as a remote MCP connector in Claude (Settings → Connectors), Cowork, or any MCP-compatible client, and sign in with OAuth. Access is scoped to your organization — nothing else.
"Give me my morning briefing." "Are we pacing to target?" "What changed in the account last week?" Your assistant calls Atlas and answers with exact figures — currency, timezone and freshness stamp included.
Atlas serves teams whose revenue depends on trustworthy numbers. The connector inherits the same trust model as the Atlas platform:
Every tool carries the MCP readOnlyHint annotation. There is no write path from the connector; changes in Atlas always go through human approval.
OAuth-authenticated, scoped to one organization per token. A token structurally cannot reach another organization's data.
Every number is produced by Atlas Core — the same dispatch the web app uses. The model formats and explains; it never calculates.
Hosted on Google Cloud in the Netherlands (europe-west4), encrypted in transit and at rest, with audit logging on access.
Through an MCP connector. Atlas MCP is a remote MCP server: add it as a connector in Claude or any MCP-compatible assistant, sign in with OAuth, and your assistant answers questions like "how are my campaigns pacing" with exact numbers from your own Google Ads, Meta and e-commerce data.
Separate platform MCPs return raw API data your assistant has to reconcile in its context window — slow, token-hungry and error-prone. Atlas is the context layer: it normalizes and joins the data first, then answers with compact, composed results that carry currency, timezone and a freshness stamp.
No. Atlas MCP v1 is strictly read-only. Campaign changes in Atlas always go through the human approval flow — never directly from a chat.
Google Ads, Meta, GA4, Google Search Console, and commerce platforms such as Shopify and WooCommerce. Tools only appear for sources your organization has connected.
MCP access is included with Atlas — pricing is a percentage of managed ad spend, not per call or per token. Get in touch for details.
Access is rolled out per organization, with personal onboarding of your data sources. Tell us which platforms you run and we'll take it from there.
request access →