Marketing
Claude as an operations hub: how we connect ads, CRM and reporting

Mariángeles Leiva Luque
Published · 10 min

The short answer
At We make it Lab we use Claude as the place where the agency's data and tasks come together. With connectors built on MCP (Model Context Protocol, the open standard Anthropic introduced on November 25, 2024), Claude queries Meta Ads, Google Ads, GA4, our CRM, ClickUp, Slack and Google Drive from a single conversation. That is how we build weekly reports, account audits and tasks without copying numbers by hand from one tab to another.
The part we watch most closely is permissions. Claude only sees what the person who connects it can see, we always start ad accounts on read access, and every deliverable goes through a quality check before someone on the team looks at it. If you run an online store, you can get started in an afternoon with a single process: your weekly ad report.
What "operations hub" means
A paid media agency for ecommerce spends its day jumping between tools: spend in Meta and Google, sales in the store and in GA4, leads in the CRM, tasks in ClickUp and conversations in Slack. Building a report used to mean opening five tabs and matching numbers by hand.
MCP removes that jump. Anthropic described it as an open standard for building secure, two-way connections between data sources and AI-powered tools. Instead of coding a separate integration for each system, each tool gets a connector and Claude can query all of them in the same conversation.
Here is how we have it organized today:
| Area | Tool | What Claude uses it for |
|---|---|---|
| Ads | Meta Ads and Google Ads | Read spend, results and creatives by campaign |
| Analytics | GA4 | Match sessions, conversions and products with ad data |
| Sales | CRM (GoHighLevel) | See leads, stages and closed deals the ad dashboard does not show |
| Tasks | ClickUp | Create tasks with context, owner and due date |
| Team | Slack | Flag what is ready and what needs review |
| Files | Google Drive and Sheets | Read briefs, save drafts and update spreadsheets |
Build the same table with your own tools and mark where each number you check every week lives today. That is your map for deciding what to connect first.
The idea I saw confirmed at Growth Lab
At Growth Lab in Florianópolis, Rodrigo Chernhak, partner at Agência Tab, showed how they use Claude as the base that connects Asana, Drive, Gmail, Figma, WordPress, their CRM and in-house prospecting and proposal tools. The slide summed it up in one line: "Everything goes through here".
We got to the same place from a different direction. Tab came from content and proposal production; we came from paid media and reporting for online stores. What both setups share is that the team stops hunting for data and spends more time deciding what to do with it.
If you are considering something similar, start with the process that eats the most copy and paste hours today.
What we connect and with which connectors
When an official connector exists, we prefer it. When it does not exist or falls short, we build our own, almost always read only.
Meta Ads. Meta released its own MCP server for ads, hosted by Meta, with tools scoped to each account's permissions.
Google Ads and GA4. Google maintains a Google Analytics connector and a Google Ads connector on GitHub. If you want to see what you can ask for, we cover it in our guide to auditing Google Ads with Claude.
CRM. HighLevel has an official MCP server that is authorized through OAuth and only performs the operations allowed by the scopes you grant. If your CRM is not organized yet, start there: this is how we handle CRM implementation on GoHighLevel.
ClickUp. ClickUp explains on its blog how its official MCP server can create and update tasks, read comments and search the workspace.
Slack. The Slack MCP server can search messages, read channels and send updates, with permissions approved by the workspace admin.
The technical steps to connect an in-house system are in how to connect Claude to your CRM or ERP with MCP. Before connecting any of them, read what permissions it asks for and write down who on your team authorizes it.
How we use it at the agency
Ad audits with the same criteria every time
We have Claude skills to audit Meta Ads, Google Ads, TikTok and Pinterest accounts. The Claude help center defines skills as folders of instructions, scripts and resources that Claude loads when it needs them: MCP gives access to the data and the skill tells Claude how to work with it.
Each skill holds the checkpoints and the thresholds we use to flag something red, yellow or green. That way, anyone auditing an account follows the same checklist. Then a person reads the result and decides what to change. We explain how to build them in what Claude skills are and how to create them for your company.
CRM: what the ad dashboard cannot see
When a sale closes over WhatsApp or on a call, Meta records the lead but does not know whether that person bought. When Claude reads the CRM alongside the ad account, we can see which campaigns bring leads that move forward and which bring contacts that never reply.
A campaign with a low cost per lead can be the one that sells the least. Before you move budget, check whether your campaigns are measured by lead or by closed sale.
Weekly reports: the data arrives together
Each client's weekly report is built from data that is already connected: platform spend and results, GA4 sessions and sales, lead status in the CRM and completed tasks in ClickUp. Claude pulls the numbers together, compares them with the previous week and writes a first draft. The account owner reviews it, adds context and sends it.
When a GA4 number does not add up, we go back to the metric definition in our GA4 dimensions and metrics reference before fixing the prompt. The time that used to go into building the spreadsheet now goes into explaining what to do the following week.
Agents with quality control
For long tasks we use agents: one researches and writes, another reviews. The Claude Code documentation describes subagents as assistants with their own context, their own instructions and access only to the tools they need. That separation lets us apply a simple rule: whoever writes does not approve.
This blog works that way: one agent reads the article index, researches and writes all three languages; another checks data, sources, links and spelling, and only then is the publishing task created in ClickUp for the web team. Before any deliverable reaches a client, a person always looks at it.
For your store, pick a single automatic output at first: a task or a notification, not both at once.
Permissions: start with read access
Connecting Claude to an ad account means giving it access to your money. That is why permissions are the first decision, before any automation.
According to the article on Claude's web connectors, Claude inherits each person's permissions from the connected service: if you cannot access a file, channel or record, Claude cannot either. On Team and Enterprise plans, Owners can limit each connector action for the whole organization with three options: "Always allow", "Needs approval" or "Blocked".
Google's connectors also come with their own safeguards:
| Connector | What it can do | How it ships |
|---|---|---|
| Google Analytics (GitHub googleanalytics) | Reports, funnels and realtime; also create annotations, custom dimensions and key events | Starts read only; writing requires the --allow-write option and an extra scope |
| Google Ads (GitHub googleads) | GAQL queries; also create assets and manage labels | Every change is proposed first and only applied after a confirmation; can be kept read only |
| Custom connectors in Claude | Whatever each server allows | Anthropic notes it does not verify them and asks you to connect only trusted servers |
Our internal rule: in ad accounts, Claude reads, analyzes and proposes. It can leave a draft ready, but turning a campaign on or moving budget is a decision and an action for a person. Before connecting a tool, check what permissions it asks for and deny the ones you do not need.
How to set it up for your online store
Pick one process. The weekly ad report is the best candidate: it repeats, always uses the same data and takes up your time today.
List the sources. For that report, they are probably Meta Ads, Google Ads, GA4 and your store platform (Shopify, Tiendanube or another).
Connect with read access. Use official connectors when they exist. If you use a third party one, check who maintains it and what permissions it asks for.
Write the request once. Which metrics, compared with which period and with which thresholds. Save it as a skill or a fixed instruction so you do not repeat it every week.
Check the numbers against the source. For the first four weeks, compare Claude's report with the original dashboards. If a number does not match, fix the request.
Add one output. Once the report is reliable, add the task in your project tool or the Slack notification.
If a step fails, do not move on: a report that does not match the source helps you make bad decisions faster. If you would rather have your team learn to build it with guidance, we offer Claude Code training for teams.
What to avoid
Granting write access to ad accounts on day one. A budget change applied wrong during Black Friday is expensive. Start with read access.
Connecting servers when you do not know who maintains them. The custom connectors guide warns that a malicious server can include hidden instructions that try to make Claude take unintended actions.
Using a shared credential with no limits. The same guide explains that on Team and Enterprise, if the connector uses a single credential, everyone who uses it reaches the service with that access. Use one limited to what each person should see.
Sending the report without a person reading it. The explanation and the decision on what to change still belong to the team.
Connecting everything at once. Add connectors one at a time, once the previous one works.
To organize connectors, skills and security across the whole company, we have a guide on how to implement Claude in a company.
Conclusion
To use Claude as an operations hub, you need to pick one process, connect the sources with the right permissions and check the results against the source until they are reliable. At the agency we started with ad reports and audits, then added the rest.
If you run an online store, the weekly report is the best first step: you will use it every week and you will notice right away whether the numbers add up. If you also want to automate what happens after the report, see how we approach marketing automation.
If you want to know which store data to connect first and how to read it, book a 30-minute account diagnosis with us.
Sources
Introducing the Model Context Protocol, Anthropic, published Nov 25, 2024.
Pre-built web connectors using remote MCP, Claude Help Center, accessed Nov 15, 2026.
Get started with custom connectors using remote MCP, Claude Help Center, accessed Nov 15, 2026.
What are skills?, Claude Help Center, accessed Nov 15, 2026.
Create custom subagents, Claude Code documentation, accessed Nov 15, 2026.
google-analytics-mcp, Google Analytics repository on GitHub, accessed Nov 15, 2026.
google-ads-mcp, Google Ads repository on GitHub, accessed Nov 15, 2026.
Ads MCP Server, Meta for Developers, accessed Nov 15, 2026.
HighLevel MCP Server, HighLevel documentation, accessed Nov 15, 2026.
How to Use the ClickUp MCP Server, ClickUp blog, published Sep 8, 2026.
Slack MCP server, Slack documentation, accessed Nov 15, 2026.
Presentation by Rodrigo Chernhak (Agência Tab) at the 3rd edition of Growth Lab, Florianópolis, Nov 12, 2026.
You might also like
An AI agent team for marketing: the writer never approvesFrequently asked questions
- What is MCP? It is the Model Context Protocol, an open standard Anthropic introduced in November 2024 to connect AI tools with data sources. It lets Claude query several tools from the same conversation.
- Can Claude change campaigns in Meta Ads or Google Ads? It depends on the connector and the permissions you grant. The Google Ads connector that Google publishes on GitHub asks for confirmation before applying each change and can be kept read only. We let Claude read and propose; turning campaigns on or moving budget stays with a person.
- Can Claude see data I do not have access to? No. According to the Claude help center, it inherits each person's permissions from the connected service. The exception is a connector with a shared credential: in that case everyone uses that credential's access.
- Do I need a paid Claude plan to connect tools? Not to get started. Custom connectors are also available on the Free plan, limited to one. For a team, Team or Enterprise makes more sense, since Owners control which actions are allowed. We compare the plans in our article on Claude pricing for companies.
- Where do I start if I have a small store? With the weekly ad report on read access. Connect Meta Ads or Google Ads and GA4, write what you want to see and compare it with the original dashboards for four weeks.
About the author

Mariángeles Leiva Luque
Marketing & Comms · We make it Lab
Explore more on



