For marketing in Claude you need skills for the method and an MCP server for the data. A connector is an MCP server added to your claude.ai account, and a plugin is the package that ships skills and servers together, so the real choice comes down to one question: is the data in an account you own, or out in the world?
Your Search Console, Drive and CRM are accounts you own, and a connector covers them. A competitor's rankings, a prospect's work email and the ads another brand is running sit in accounts you'll never log into, and those take a data MCP server. Below is the map, a working file for each piece, and the marketing job each one is right for.
The map
| Piece | Gives Claude | Lives in | You write |
|---|---|---|---|
| Skill | A method: how to do the job |
.claude/skills/ in a repo, ~/.claude/skills/, or your account |
A folder with SKILL.md
|
| MCP server | Tools and data | Your machine, pointing at a local process or a remote URL |
claude mcp add or .mcp.json
|
| Connector | Tools and data | Your claude.ai account | Nothing: you add it under Customize > Connectors |
| Plugin | The above, plus commands, subagents and hooks | Your account or your machine | .claude-plugin/plugin.json |
MCP, the Model Context Protocol, is the open standard Anthropic open-sourced in November 2024 for connecting AI apps to tools and data. Connectors, local servers and the servers inside plugins all speak it, so from Claude's side a tool is a tool. What changes is where you configure it and which Claude apps can see it.
The setup below covers three jobs a small team runs every week: a keyword report for your own site, a look at which ads a competitor is running, and a short list of prospects with work emails.
1. A skill holds the method
A skill is a folder with a SKILL.md file: instructions, plus optional templates or scripts. Only the name and description sit in Claude's context until a task matches; then Claude loads the rest. So skills cost almost nothing to keep around, and every repeatable marketing process belongs in one: the brief format, the report layout, the voice rules.
---
name: keyword-report
description: Weekly keyword report for our site. Use when asked for SEO numbers, rankings, or how search did this week.
---
1. Pull the last 7 days and the 7 before from Search Console: clicks, impressions and average position per query.
2. Keep queries with 20 or more impressions. Sort by the change in clicks.
3. Write three sections: Climbing, Slipping, New. One line per query: position then and now, clicks then and now.
4. End with at most three pages to update, each with the query it should win.
5. Numbers only. No adjectives about performance.
Save it as .claude/skills/keyword-report/SKILL.md in a repo to share it with the team, or under ~/.claude/skills/ for yourself. In Claude Code, /keyword-report runs it by name.
Use a skill when Claude can already reach the data but does the job differently every time. A skill fetches nothing by itself, though. Step 1 needs a server.
2. An MCP server brings the data, configured on your machine
An MCP server exposes tools (search, create, update), resources (files and records) and prompts. It runs as a local process or remotely over HTTP. In Claude Code you add one from the terminal:
# a remote server, for you in this project (the default local scope)
claude mcp add --transport http notion https://mcp.notion.com/mcp
# a local process, written to .mcp.json for everyone who clones the repo
claude mcp add --scope project analytics -- npx -y @bytebase/dbhub --dsn "postgres://reader:reader@localhost:5432/analytics?sslmode=disable"
--scope project writes the server into .mcp.json at the repo root, which you commit. With both servers at project scope, the file looks like this:
{
"mcpServers": {
"notion": {
"type": "http",
"url": "https://mcp.notion.com/mcp"
},
"analytics": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@bytebase/dbhub", "--dsn", "postgres://reader:reader@localhost:5432/analytics?sslmode=disable"],
"env": {}
}
}
}
Claude Code asks each teammate to approve a server from .mcp.json before first use. The reader user in that connection string is deliberate: a read-only database role makes a write fail at the database, whatever Claude decides to try.
Use a local MCP server when the data sits where only your machine can reach it (a private database, files, an internal API behind the VPN), or when the service has no connector yet. Check before you build one: buildwithclaude.com listed 8,245 MCP servers when I looked on November 17, 2026.
3. A connector is the same server, added to your account
A connector is an MCP server added to your claude.ai account under Customize > Connectors. You authorize it once, usually by signing in to the service, and it works in the Claude app on web, desktop and mobile and follows you into Claude Code. There's no file to write: for a custom one, you add the server's URL as a custom connector and sign in.
Two limits catch marketing teams:
- Connectors call out from Anthropic's cloud, so a custom connector has to point at a server reachable over the public internet. The analytics database behind your VPN is a local server's job (Anthropic's plugin help page, read November 17, 2026).
- Claude Code loads connectors only when you sign in with a claude.ai subscription. Signed in with an API key or running through Amazon Bedrock, they don't show up.
Use a connector for SaaS accounts you own and want everywhere you use Claude: Drive, Notion, Slack, the CRM, Search Console.
4. A plugin ships the set
A plugin bundles skills, MCP servers, commands, subagents and hooks into one install. It adds no capability of its own. It's how a teammate gets your whole setup in one step, and under the hood it's a folder:
marketing-stack/
.claude-plugin/
plugin.json
.mcp.json
skills/
keyword-report/SKILL.md
competitor-ads/SKILL.md
commands/
weekly.md
The manifest only needs a name. A description and a version tell people what they're installing:
{
"name": "marketing-stack",
"description": "Weekly keyword report, competitor ad check, and the servers they use",
"version": "0.1.0"
}
To install it from Claude Code, put the folder in a git repo with a catalog at .claude-plugin/marketplace.json:
{
"name": "acme-marketing",
"owner": { "name": "Acme growth team" },
"plugins": [
{ "name": "marketing-stack", "source": "./marketing-stack", "description": "Weekly SEO and ads checks" }
]
}
Then, inside a session:
/plugin marketplace add acme/claude-plugins
/plugin install marketing-stack@acme-marketing

The example marketing-stack plugin from this post: one folder that ships the skills, the MCP servers and a slash command.
Where it runs depends on where you added it. Installed from Claude Code, it stays on that machine. Added under Customize > Plugins in the Claude app, it's saved to your account, works in chat and Cowork, and syncs into Claude Code each time Claude Code starts (v2.1.273 or later, signed in with your Claude account). In plain chat a plugin's skills, commands and remote servers work, while hooks, subagents and local MCP servers run only in Cowork and Claude Code. Plugins are on every paid plan (Pro, Max, Ultra, Team, Enterprise), and on Team and Enterprise you can publish one to the org library, which is how a marketing lead gives ten people the same setup.
Use a plugin when more than one person needs the setup, or when someone already packaged the job.
Your accounts vs data you don't own
Most answers to this question stop at connectors to your own tools: the CRM, the analytics, the shared drive. That covers reporting. Finding customers is a different job, because its data lives in accounts you'll never log into. Split the jobs by whose data each one needs:
| Marketing job | Whose data | What you add |
|---|---|---|
| Brief format, voice, report layout | Nobody's, it's a method | Skill |
| Weekly keyword report | Yours (Search Console) | Connector or server on your Google login, plus the skill |
| Campaign docs and brand assets | Yours (Drive, Notion) | Connector |
| Product usage for a launch email | Yours, in a private database | Local MCP server with a read-only user |
| Competitor rankings and keyword gaps | Someone else's | Data MCP server |
| A competitor's live ads | Someone else's (Meta's Ad Library) | Data MCP server |
| Prospects and their work emails | Someone else's | Data MCP server with enrichment and an email finder |
| The same setup for the whole team | n/a | Plugin |

Pick by whose data the job needs: your own accounts take a connector or a local server, someone else's data takes a data MCP server.
The bottom rows are where a connector can't help: there's no account of yours to authorize. You need a server that fetches that data and returns it as tool results. One option built for exactly these rows: superagnt is a marketing plugin for Claude and ChatGPT that helps businesses find customers through outbound, SEO and ads. Its base plugin connects an MCP server and its skill packs add the methods, so it's the four pieces from this post in one install. The server covers SEO data, an email finder, lead and company enrichment, and data from Reddit, LinkedIn, X and Facebook (the Ad Library included), plus a Search Console server on your own Google connection. Its connect page lists a separate URL per capability (/mcp/seo, /mcp/email-finder, /mcp/reddit and so on), which matters for the next section.
Keep the tool list short
Skills and servers cost context differently. A skill sits as a name and a one-line description until Claude needs it. A server's tools have to be described to the model before Claude can call them, so a server with dozens of tools is dozens of descriptions competing with your actual task, and more chances for Claude to grab the wrong one.
What I'd do for a marketing stack:
- Many skills, few servers. Ten skills cost ten short descriptions.
- Connect the narrowest endpoint the job needs. If a server offers one URL per capability, the keyword report session gets the SEO endpoint and nothing else.
- Turn off what you don't use.
/mcpin Claude Code shows each server's status and lets you disable the ones this session doesn't need.
Keep it from sending or publishing
"Can Claude be trusted?" sits in the People Also Ask box for this search. For a marketing setup it comes down to what you connect and what those tools are allowed to do.
- Every MCP tool has to declare
readOnlyHint(it only reads) anddestructiveHint(it can change or delete data), per Claude's MCP docs, updated November 12, 2026. Read them before you connect a server that can send email, post, or edit your site. - A connector's permissions mirror your access on the service, and you can disconnect it any time.
- A local server runs code on your machine with your permissions, and a server that fetches web pages can carry prompt injection: instructions hidden in the content it returns. Connect servers you trust, and give database servers a read-only user.
Research jobs (rankings, ads, prospect lists) need read-only tools and nothing more. Keep anything that sends, posts or spends behind your own approval.
If your team also uses ChatGPT
Can ChatGPT use MCP? Yes, with limits. According to aiagentslibrary.com's comparison, checked against vendor docs on September 26, 2026, ChatGPT runs MCP servers through developer mode, in beta for Business, Enterprise and Edu on the web, and read-only on Pro. It also reads SKILL.md skills, and its Plugin Directory replaced the App Directory on July 9, 2026.

ChatGPT support as summarized by aiagentslibrary.com from vendor docs, checked September 26, 2026.
So put your effort into the two pieces that move. A SKILL.md file works in both apps as is: the Agent Skills format moved on October 22, 2026 to the Agentic AI Foundation, the Linux Foundation project that also runs MCP, and more than 70 agent platforms read it. A remote MCP server serves any MCP client. Connectors have to be authorized again in each app (ChatGPT calls them apps), and a Claude plugin's commands and subagents have to become skills before ChatGPT can use them, per OpenAI's own guide for bringing a Claude plugin across.
When a tool doesn't show up
-
/mcplists every server with its origin: aclaude.aiprefix means a connector,plugin:means it came from a plugin, and anything else was configured locally. -
/statusshows which login is active. No claude.ai login, no connectors. -
claude mcp listshows.mcp.jsonservers still waiting for approval. -
/skillslists loaded skills, with the ones synced from your account underclaude.ai sync. - Works in Claude Code but not in chat? It was added on the machine, and chat only sees your account.
Short answers to the related searches
What is an MCP for Claude? An MCP server is a program that gives Claude tools and data from outside the chat over the open Model Context Protocol. You add it in Claude Code with claude mcp add, or to your account as a connector.
Claude MCP vs MCP? Same protocol. "Claude MCP" just means MCP servers used from Claude, and a server you connect works in other MCP clients too, often with the same JSON block. BeyondNoise's docs, for one, give the identical mcpServers entry for Claude Desktop and Cursor.
Is there a Claude MCP course? Anthropic's Claude Academy has an MCP lesson in Claude Code 101.
What does Reddit say? The Reddit post that Gemini and Google AI Mode both pull into their answers here is an r/ClaudeCode thread on skills vs MCP servers vs plugins.
Is Claude better than GPT-4? GPT-4 is an older OpenAI model, and I'm not settling benchmarks here. For this setup the useful fact is narrower: Claude and ChatGPT both read SKILL.md and both connect to MCP servers, so the skills and remote servers you build once keep the choice of app open.
Top comments (0)