# How to Connect Meta Ads to Claude (Custom Connector Walkthrough) > Connect Meta Ads to Claude in five minutes with a custom connector, then make the decisions that matter: which server, which permissions, what to "Always allow", and how to check the answers. - **Author**: Marxx - **Published**: 2026-10-24 - **Category**: Product - **URL**: https://marxx.ai/posts/connect-meta-ads-to-claude --- **How do you connect Meta Ads to Claude?** Add an MCP server as a custom connector. In Claude, open **Customize -> Connectors -> Add custom connector**, paste the server's URL, sign in, and choose your ad accounts. You can use Meta's official connector for your own accounts, or the Marxx MCP server for your accounts plus competitors' ads, with changes drafted for your approval. ## The five minutes are easy. The decisions inside them aren't. Put the kettle on. By the time your chai is ready, Claude can be answering questions about your Meta ads from live data. The setup really is that quick, and you don't need to write any code. But inside those five minutes you make four decisions that matter much more than the clicks: 1. **Which server** you connect, and what it can see and change. 2. **Which accounts and permissions** you grant when you sign in. 3. **Which tools** Claude may use without asking you first. 4. **Which questions** you start with, and how you check the answers. Most setup guides skip those decisions. This one walks through the clicks *and* the choices, so the connection is useful from day one and doesn't do anything you didn't intend. Set up in the time it takes to make chai: five steps from opening Settings to asking your first question --- ## Part 1: What actually happens when you connect Claude connects to outside tools through the **Model Context Protocol (MCP)**: a standard that lets an AI assistant use another service's *tools*, such as "get campaign results" or "draft a pause". Each tool has a written description. Here's what happens, step by step. What happens when you connect: you add a server URL, you grant scopes through sign-in, Claude chooses tools from their descriptions, and you approve actions unless you choose Always allow 1. **You add a server URL.** Claude reads the list of tools that server offers. 2. **You sign in (OAuth).** Claude gets a *token*, a revocable key limited to what you approve, not your password. You choose which accounts it covers. 3. **Claude chooses tools.** In each chat, Claude decides which tool to call based on its description and your question. 4. **You approve actions.** Claude asks before using a tool, unless you've told it to "Always allow" that tool. **Why this matters:** Steps 2 and 4 are where you control risk. Anthropic's own documentation warns that custom connectors can connect to unverified services, that Claude can perform actions within them, and that you should review permission scopes and only click "Always allow" for trusted servers ([Anthropic](https://www.claude.com/docs/connectors/custom/remote-mcp)). --- ## Part 2: Choose your server: Meta's official connector or Marxx As of 2026, there are two main routes for Meta Ads. **Meta's official connector.** Meta released its Ads AI connectors in open beta on 29 April 2026, with an endpoint you add to Claude as a custom connector ([guide](https://pasqualepillitteri.it/en/news/1707/official-meta-ads-mcp-claude-29-tools-2026)). It works on your own ad accounts. Its tools include reporting and insights, plus creating, updating and activating campaigns, ad sets and ads. In July 2026 Meta opened the server to any developer with a Meta app, with tools to create, edit and delete ([PPC Land](https://ppc.land/meta-opens-ads-mcp-to-any-app-cutting-integration-code-to-zero/)). **The Marxx MCP server.** It connects your Meta and Google ad accounts *and* your competitors' ads. Every ad is tagged by hook, offer, emotion and format, with days live and copy counts. Changes to Meta are drafted, shown as a before and after, and applied only when you say yes. Two ways to connect Meta Ads to Claude: Meta's official connector covers your own accounts and can create, edit and activate directly; Marxx adds competitors' ads, days live and copy counts, drafts changes for approval, needs a second confirmation for risky changes, and can't delete | | Meta's official connector | Marxx MCP server | |---|---|---| | **Your own ad accounts** | Yes | Yes, Meta and Google | | **Competitors' ads** | No | Yes, tagged by hook and offer | | **Days live and copy counts** | No | Yes | | **Making changes** | Create, edit and activate directly | Drafts; you approve each one | | **Risky changes** (big budget moves, going live) | Governed by your Meta permissions | Need a second confirmation | | **Deleting** | Possible in the July 2026 release | Not possible | **How to choose:** - **You mainly want to manage campaigns from Claude, and you're comfortable with direct changes:** Meta's connector, with read-only permissions to start. - **You want to understand *why* ads work and what competitors are backing, with a human yes before anything changes:** Marxx. - **Both?** You can connect both, but more connectors means more tools for Claude to choose between. Start with one, and add the second only if you're missing answers (see [best MCP servers for marketing](/blog/best-mcp-servers-marketing)). --- ## Part 3: The five-minute setup *Menu names as of October 2026. Claude's interface changes, so check [Anthropic's documentation](https://www.claude.com/docs/connectors/custom/remote-mcp) if a step looks different.* ### 0:00: Check your plan Custom connectors are available on Claude's Free, Pro, Max, Team and Enterprise plans. **Free plans are limited to one custom connector.** On Team and Enterprise, an Owner adds the connector first (see below). ### 1:00: Open Connectors In Claude, go to **Customize -> Connectors** and choose **Add custom connector**. ### 2:00: Paste the server URL For Marxx, copy the MCP server URL from your Marxx workspace settings. For Meta's connector, use the endpoint Meta publishes, and only that one. Third-party look-alike URLs are a known risk. ### 3:00: Sign in and choose accounts A sign-in window opens. Log in and approve access. **This is the most important click.** Grant only the ad accounts you need. If the server offers read-only access, start there. **With Marxx:** If your account holds more than one client, Marxx asks which one you mean before answering anything. There's no default, so it can't guess wrong. ### 4:00: Ask your first question Start a new chat, make sure the connector is switched on in the tools menu, and ask something you'd normally open Ads Manager for. Marxx answering a question about ads inside Claude ### For teams: Owners add it once, members sign in Setting it up for a team: an Owner adds the connector under Organization settings, Connectors, Add, Custom; each member finds it under Customize, Connectors and signs in with their own account On **Team and Enterprise** plans, an Owner goes to **Organization settings -> Connectors -> Add -> Custom** and pastes the URL. Each member then finds the connector under **Customize -> Connectors**, clicks **Connect**, and signs in with their own account. That way, each person's access matches their own permissions. --- ## Part 4: Decide what Claude can do without asking Claude asks before using a connector's tools unless you choose **Always allow**. That button is convenient, and it's the single biggest safety decision in the setup. Tool approvals: always allow reading and competitor lookups; ask each time for drafting changes; never always-allow anything that activates, spends or changes budget; turn off unused tools | Tool type | Setting | Why | |---|---|---| | Reading results, listing accounts, competitor lookups | **Always allow** | The worst case is a wrong answer | | Drafting a change, creating a preview | **Ask each time** | Cheap to check, and you see what's proposed | | Anything that activates ads, spends money or changes budgets | **Never always-allow** | A mistake costs money before anyone notices | | Tools you never use | **Turn off** | Fewer tools, better tool choices | **An extra safety net on Meta's side:** Set an account-level spending limit in Meta's billing settings. If anything goes wrong, the damage has a ceiling. **How Marxx handles this:** Every change is a draft with a before and after. Risky moves, like publishing a campaign, turning anything on, or moving a budget by more than 50%, need a second confirmation. Nothing can be deleted, and every change is logged. Our [guardrails guide](/blog/ai-ad-account-guardrails) covers this in detail. --- ## Part 5: Your first five questions, and how to check the answers Five first questions: results, fatigue, rivals, gaps, and a drafted action you approve | # | Question | What a good answer includes | Why start here | |---|---|---|---| | 1 | **Results:** "Which ads spent the most last week, and what did each cost per result?" | A short ranked list with spend and cost per result | Checks the connection works and the numbers match Ads Manager | | 2 | **Fatigue:** "Which of my ads are fading?" | Ads whose results fell while spend held, with dates | Your refresh list | | 3 | **Rivals:** "What has my top competitor been running longest?" | Ads with days live and copy counts (Marxx) | What they're backing | | 4 | **Gaps:** "Which hooks do my competitors use that I don't?" | A list of hook types, with example ads | Next week's test ideas | | 5 | **Action:** "Draft a pause for my three weakest ads." | A before-and-after preview, not an applied change | Tests the approval flow safely | ### Check before you act AI answers about ad data are fluent, which makes them easy to trust too quickly. Five checks before acting on an answer: which account, which dates, which metric, show me the ads, and treat the why as a hypothesis 1. **Which account?** Is the right client and ad account named? 2. **Which dates?** Did it use the window you meant? Say "last 7 days", never "recently". 3. **Which metric?** Cost per result, not just clicks or click-through rate. 4. **Show me.** Ask for the ads behind any claim. 5. **Why?** When Claude explains a change ("creative fatigue", "auction pressure"), treat it as a hypothesis. It can see your numbers, not your landing page, your tracking, or a competitor's sale. ### Worked example: A confident answer that needed checking *Hypothetical example.* **Question:** "Why did cost per lead rise last week?" **Answer:** "Creative fatigue. Your top ad's frequency rose from 2.1 to 3.4." **The check:** Asked to "show cost per lead by ad and by day", Claude's data showed costs rose on *every* ad on the same day, including brand-new ones. Fatigue doesn't hit new ads overnight. The real cause was a broken tracking tag on the form page, found in two minutes once the pattern was visible. **The lesson:** Use Claude to find *what* changed, fast. Decide *why* yourself. --- ## If it doesn't work If it doesn't work: no tools used means the connector is off for this chat; which client is expected with several clients; no data means the ad account isn't linked; can't add it on a team plan means ask an Owner; to turn it off go to Customize, Connectors | Symptom | Likely cause | Fix | |---|---|---| | Claude doesn't use the connector | It's off for this chat | Turn it on in the tools menu | | "Which client do you mean?" | Several clients, no default (Marxx) | Expected; name one | | No data comes back | The ad account isn't linked | Connect it inside Marxx, or re-grant it in Meta's sign-in | | You can't add a custom connector | Team or Enterprise member | Ask an Owner to add it | | You want to turn it off | -- | **Customize -> Connectors**, then remove or disable it. For Meta, also revoke access in Business Suite's integration settings | Marxx creative board grouping ads by hook, angle and format --- ## Six mistakes, and how to spot them | Mistake | Symptom | Fix | |---|---|---| | Granting every ad account | Answers mix up clients | Grant only what you need | | "Always allow" on write tools | Changes nobody remembers approving | Always-allow reads only | | Copying a look-alike URL | Odd behaviour, unexpected permission requests | Use only the URL from the vendor's own settings or docs | | Vague questions | Answers about the wrong period or metric | Name the dates, the client and the metric | | Trusting the "why" | New creative that doesn't fix the drop | Ask for the data by ad and by day | | Connecting everything at once | Slower, vaguer answers | One connector first; add a second only if needed | ## What to take into your next team meeting - **The setup takes five minutes; the permissions last much longer.** Spend your attention on the sign-in screen. - **"Always allow" is for reading, never for spending.** - **Meta's connector manages your accounts; Marxx adds competitors and an approval step.** Choose by the questions you need answered. - **Claude finds what changed. You decide why.** - **Free plans get one custom connector.** Choose it deliberately. ## FAQ **Can I connect Facebook Ads to Claude?** Yes, by adding an MCP server as a custom connector: Meta's official connector, or a server like Marxx that also covers competitors. **Which Claude plans support custom connectors?** Free, Pro, Max, Team and Enterprise, according to Anthropic's documentation. Free plans are limited to one custom connector. **Is it safe to connect my ad account to Claude?** It can be. Grant only the accounts you need, start read-only, use "Always allow" only for read tools, and set a spending limit in Meta. With Marxx, changes are drafted and need your approval. **Can Claude change my Meta ads?** Through Meta's connector, yes, if you grant write permissions. Through Marxx, Claude drafts changes that apply only after you approve them. **Does it work in ChatGPT too?** Yes. See [how to analyse your Meta ads in ChatGPT](/blog/analyze-facebook-ads-chatgpt). --- ## Add the Marxx MCP server to Claude Five minutes, one connector, and your Meta ads and your competitors' ads are in the chat, with every change waiting for your yes. A Marxx competitor brief delivered in Slack **[Add the Marxx MCP Server ->](https://www.marxx.ai)** *Related: [Claude vs ChatGPT for Marketing](/blog/claude-vs-chatgpt-for-marketing) - [Best MCP Servers for Marketing](/blog/best-mcp-servers-marketing) - [Guardrails for Letting AI Touch Your Ad Account](/blog/ai-ad-account-guardrails)* ### Sources - Anthropic. [Custom connectors using remote MCP](https://www.claude.com/docs/connectors/custom/remote-mcp) (plans, setup steps, security guidance). - Pasquale Pillitteri (2026). [Official Meta Ads MCP for Claude: Guide to all 29 tools](https://pasqualepillitteri.it/en/news/1707/official-meta-ads-mcp-claude-29-tools-2026). - PPC Land (2026). [Meta opens ads MCP to any app](https://ppc.land/meta-opens-ads-mcp-to-any-app-cutting-integration-code-to-zero/). - Marxx MCP server behaviour, October 2026. --- - [More Product articles](https://marxx.ai/posts/category/product) - [All articles](https://marxx.ai/posts)