Claude MCP Servers for a Marketing Agency: Which Ones to Connect, Which to Keep Read-Only
One consultant on this site wired Claude into eight MCP servers to run client marketing through conversation. Here is what is official, what is community-built, and a safe order to connect them.
Eight dashboards or one conversation
A consultant named Tom Crawshaw, documented on this site, connected Claude to eight MCP servers covering ad platforms, analytics and GoHighLevel, so he could run client campaigns by asking questions instead of logging into eight tools. He reports $600,000 generated for clients in 90 days and more than 1,000 meetings booked, but those numbers describe his whole stack, including n8n automations, not the MCP setup alone, and they are self-reported and unverified. What is not in doubt is the pattern: an assistant that can read your clients' numbers and tell you what changed is useful on Monday morning.
The risk is just as clear. An assistant that can also change budgets can spend a client's money wrongly in seconds. This guide covers which connections exist today, which are official, which are community builds you should vet, and a connection order that keeps the risky parts for last.
What MCP does for an agency, in one paragraph
MCP is a standard way for an AI app to call tools in other software. Instead of you exporting a CSV from Google Analytics and pasting it into Claude, Claude asks Google Analytics directly and gets the numbers back. Each connection is a server that exposes a set of tools, such as run a report or list campaigns, and a login that decides what Claude is allowed to see and change. Everything that follows comes down to controlling that login.
What exists and who made it
As of November 2026, these are the connections we could verify against official or near-official sources.
Google Analytics has an official open-source server from Google's own GitHub organization. By default it only reads: account and property info, core and realtime reports. Write tools, such as creating annotations or key events, only switch on if you pass an allow-write flag and grant an edit scope. It needs Python 3.10 or newer, a Google Cloud project with the Analytics Admin and Data APIs enabled, and credentials for a user with access to the properties.
Google Ads also has an open-source server from Google's GitHub organization. It runs GAQL queries and lists accessible accounts. It is not strictly read-only: it has tools to create assets, upload video and manage labels, and those changes use a propose-and-confirm step where a dry run returns a checksum before anything commits. You can turn the write categories off in its config file. It needs Python 3.11 or newer and a Google Cloud project. The repository does not describe a formal support commitment, so expect to fix your own setup problems.
Meta Ads has a hosted connector at mcp.facebook.com/ads, reported by several guides to be in open beta since April 29, 2026. You add it to Claude as a custom connector and sign in with the Facebook profile that has admin access to the ad account. Guides list the permissions as ads_read, ads_management, read_insights and business_management, and note that Meta treats you as responsible for any spend or changes it makes. We found this in secondary sources, not a Meta announcement, so check Meta's own documentation before you rely on the details.
GoHighLevel and Smartlead are murkier. We found community-built servers for both and could not confirm an official first-party server for either one. One widely cited Smartlead server from a partner was archived by its owner on February 3, 2026. If you use these, read the code, give them the narrowest API key the platform allows and expect breakage.
A worked example: the Monday client report
Take a four-person agency running paid social and search for 12 local service clients. Today an account manager spends about 20 minutes per client every Monday pulling spend, leads and cost per lead from Meta, Google Ads and Analytics, then writing three sentences of commentary. That is four hours a week, an estimate for illustration.
With Google Analytics, Meta Ads and Google Ads connected read-only, the account manager opens a Claude project for one client and asks the same fixed question each week: compare last week to the week before, list anything that moved more than 20 percent, and draft the three-sentence summary. Claude pulls the numbers, flags what changed and drafts the note. The manager reads the numbers against the platform for one or two clients to confirm they match, edits the commentary and sends it. Realistically that takes five to seven minutes a client once the prompt is dialed in. Nothing in this workflow can change an account.
Step by step: connect it safely
Step 1: Decide what Claude is allowed to do before you connect anything
Write two lists for each platform: reads you want, and writes you will never allow without a human click. For most agencies the second list is: change budgets, pause campaigns, publish ads, send email. Keep that list taped to the screen while you set up.
Step 2: Start with Google Analytics and Search Console, read-only
Follow the official Google Analytics repository instructions, authorize with the read-only scope and do not pass the allow-write flag. Run three test questions where you already know the answer, such as sessions last month, and check the numbers against the Analytics interface. If they do not match, stop and find out why before moving on.
Step 3: Add ad accounts using the narrowest access the platform offers
For Meta, connect with a login that has analyst-level access to the ad account if the client has set that up, not an admin login. For Google Ads, use the official server with the write categories set to false in its config. If you cannot get a narrower login than admin, keep the connection on a separate Claude project with instructions that say never to propose changes, and treat that as a weak control, because instructions are not permissions.
Step 4: Keep one client per project
Create one Claude project per client with that client's connections only, and name it clearly. Mixing clients in one conversation is how one client's numbers end up in another client's report. It also means you can remove a departing client's access in one place.
Step 5: Turn on writes for one job, with approval on every action
If you want Claude to change something, pick one narrow job, such as pausing ads whose cost per lead is double target for seven days. Let it propose the change as a list with the numbers behind it, and make the change yourself or approve each tool call. Never leave writes on in an unattended scheduled run.
Step 6: Log every change it proposes and every change you make
Keep a running note per client: what Claude suggested, what you did, what happened. After a month you will know whether the suggestions are worth anything, and you will have an answer ready when a client asks why the budget moved.
Step 7: Review the connections every month
Remove tokens for clients who left, rotate keys and check which logins each server uses. Connections accumulate and nobody remembers them.
What it costs
The servers themselves are free. Claude Pro is $20 a month billed monthly or $17 with annual billing, and Max is $100 a month, as of November 2026. Claude Team starts at $20 per seat a month on the standard plan with annual billing, and plan rules for adding custom connectors differ between individual and Team accounts, with some guides saying an owner must add them first. Check Anthropic's current pricing and connector settings before you plan around a seat count. The listing for the case study on this site puts startup cost at $50 to $200 a month, which is a reasonable range for plans plus a small server. Budget your own time more carefully: a day to set up one client's connections and test them, then a few minutes a week.
When not to do this
Skip it if you manage two clients and report from a template in 30 minutes a week, because the setup will not pay back. Skip write access if you cannot explain to a client, in one sentence, what the assistant is allowed to change. Do not connect a client's accounts through your own personal login if you are leaving the agency's tools in a shared workspace. And remember the numbers still come from the platforms. Claude can misread a report, mix up date ranges or round badly, so check the first few weeks against the dashboards.
Frequently Asked Questions
What is an MCP server for marketing?▾
An MCP server is a connector that lets an AI app such as Claude call tools in another product, for example running a Google Analytics report or listing Meta ad campaigns. It exposes a set of actions and uses a login to decide what the AI can read or change.
Is there an official Google Ads MCP server?▾
Google publishes an open-source Google Ads MCP server on its GitHub organization. It runs queries and has limited write tools with a propose-and-confirm step, and you can disable the write categories. It requires Python and a Google Cloud project, and the repository does not describe a formal support commitment.
Can Claude run Meta ads for me?▾
Meta has a hosted ads connector that guides say works with Claude and exposes reporting and campaign management tools. With management permissions it can change real ad spend, so start with read access, review every proposed change and keep a person in the approval loop.
Is there a GoHighLevel MCP server?▾
We found several community-built GoHighLevel servers but could not confirm an official one as of November 2026. Read the code before connecting a community server and use the narrowest API key GoHighLevel allows.
Do I need Claude Max for MCP?▾
Not necessarily. Custom connectors are described as available on paid plans, but rules differ between individual and Team accounts, so check Anthropic's current documentation. Pro at $17 to $20 a month is enough to test one client.
How do I stop Claude changing client accounts by mistake?▾
Use read-only scopes where the platform offers them, disable write tools in the server config, keep one client per project and approve every change by hand. Instructions telling Claude not to change things are not a substitute for permissions.