Every Marketing MCP for Claude

• By Praveen Jha · Updated 2026-10-23 · 11 min read · Developer & MCP tools

Developer Guide - The complete connector directory for running marketing end to end inside Claude

• 53 connectors listed, verified row by row
• 16 categories, grouped by marketing job
• 5 min typical time to connect one tool

Model Context Protocol (MCP) connectors give Claude live access to your marketing stack - SEO data, ad accounts, email platforms, CRM, analytics and more - so you can research, create, publish and report from a single chat instead of switching between dashboards.

This guide is the full directory: every connector grouped by job, what it does, whether it connects in one click or needs a manual server URL, and the exact URL to paste in. Hand it to a developer and they can wire up the whole stack without hunting for endpoints.

How to use this guide: Find your category in the contents on the next page, copy the server URL exactly as printed, and follow the 4-step connection process on page 3. Do not open a server URL in a browser - it will show nothing useful. It only works pasted into Claude.

What is inside

How MCP connectors work and the two connection types | Step-by-step setup for developers | All 53 connectors in 16 category tables with copy-paste URLs | Starter stacks by role | Safety, permissions and troubleshooting | Pre-flight checklist

Contents - 16 categories, 53 connectors

1. SEO and search visibility - 6 connectors
2. Social media posting and scheduling - 2 connectors
3. Email and marketing automation - 5 connectors
4. Cold outreach and sales - 3 connectors
5. Paid ads - 5 connectors
6. CRM and lead generation - 4 connectors
7. Customer support and feedback - 2 connectors
8. Forms and lead capture - 2 connectors
9. Ecommerce - 1 connector
10. Design and creative - 2 connectors
11. Video, audio and content - 4 connectors
12. Analytics and data - 7 connectors
13. Reviews and competitive intel - 1 connector
14. Payments and revenue - 1 connector
15. Docs, comms and project management - 6 connectors
16. Automation and glue - 2 connectors

The two connection types

Marketplace means the connector is in Claude's connector directory. Connect it in one click: open Customize, go to Connectors, find the name, click Connect, and sign in to that service to authorise access.

Custom MCP means the connector is not in Anthropic's directory. Add it manually with its server URL: go to Customize > Connectors > "+" > "Add custom connector", paste the URL from this guide exactly, then complete the sign-in or API-key step the service asks for.

Check directory means the connector is available through Claude's connector directory without a published URL. Search for its name in the directory to connect it.

Developer note: A server URL is an endpoint for Claude, not a web page. Pasting it into a browser returns raw data or an error - that is expected, not a broken link.

How to add a connector - developer steps

1. Pick the connector. Find it in the category tables in this guide. Note its type and copy its server URL character for character, including any path and query string (for example, the Klaviyo URL includes?include-mcp-app=true ).
2. Connect it in Claude. For a Marketplace connector: Customize > Connectors > search the name > Connect. For a Custom MCP: Customize > Connectors > "+" > "Add custom connector" > paste the URL > Add.
3. Authorise with least privilege. Sign in to the service and approve access. Where the service offers scopes or read-only access, choose the narrowest option that still does the job. Use a dedicated marketing account, not a personal admin account, where possible.
4. Verify with a read-only test. Ask Claude a question that only reads data first - for example: "Using [connector], show me the last 7 days of data, do not change anything." Confirm the numbers match the native dashboard before asking Claude to create, send or publish anything.

Special cases a developer must know

Google Ads is self-hosted and read-only. It needs a Google Ads developer token and OAuth setup - allow extra time and follow the linked GitHub repository. LinkedIn Ads uses community servers, also via GitHub - review the code before connecting a live ad account. Zendesk has no official server; use a third-party bridge such as Composio and treat it as an integration to vet, not a one-click connect.

Test prompts after connecting

SEO: "What are my top 10 pages by clicks in Search Console this month, and which lost traffic?" Ads: "Summarise Meta Ads spend and cost per result for the last 14 days." Email: "Draft a campaign plan for the next two weeks from my recent Mailchimp performance - do not send anything." CRM: "List HubSpot deals closing this month with no activity in 7 days."

Rule for the team: Connect read first, write second. Every connector in this guide can be tested safely with a read-only prompt before Claude is allowed to post, send, spend or edit.

1. SEO and search visibility

Rankings, keywords, backlinks and local visibility.

2. Social media posting and scheduling

Create, schedule and post from one chat.

3. Email and marketing automation

Newsletters, campaigns and ecommerce email/SMS from chat.

4. Cold outreach and sales

Sequences, cadences, scraping and lead data for outbound.

5. Paid ads

Research, launch support and cross-channel reporting without living in Ads Manager.

6. CRM and lead generation

Pipeline, contacts and enriched prospect data inside Claude.

7. Customer support and feedback

Voice-of-customer input straight from real conversations.

8. Forms and lead capture

Build forms in chat and summarise responses automatically.

9. Ecommerce

Run store marketing tasks on products, orders and discounts from chat.

10. Design and creative

Generate creative and pull design context without switching tools.

11. Video, audio and content

Titles, thumbnails, scripts, generation and publishing for video-first channels.

12. Analytics and data

Product, web and cross-channel analytics you can question in plain English.

13. Reviews and competitive intel

Buyer intent and benchmarks from review data.

14. Payments and revenue

Tie campaigns to real money, not just clicks.

15. Docs, comms and project management

Assets, calendars and campaign docs Claude can read and update.

16. Automation and glue

Connect everything else and trigger actions across apps.

Starter stacks - do not connect all 53 at once

Connecting everything on day one creates noise, duplicate data and a large permission surface. Start with one stack for your role, use it for a week, then add the next category.

SEO and content lead

Google Search Console + DataForSEO (or Ahrefs/Semrush) + Keyword Tool + Google Drive + Notion. Covers rankings, keyword research, backlinks and a place to store and plan content.

Social and content creator

Zernio or Blotato + Canva + vidIQ + Google Calendar. Covers scheduling to 15+ platforms, creative, video growth data and a content calendar.

Performance marketer

Meta Ads + Windsor.ai or Supermetrics + Stripe + PostHog. Covers ad management, cross-channel reporting, revenue truth and product analytics in one view.

Email and ecommerce

Shopify + Klaviyo (or Mailchimp/Omnisend) + Jotform + Polar Analytics. Covers store data, campaigns, lead capture and unified ecommerce reporting.

Sales and outbound

HubSpot (or Close) + Apify + Vibe Prospecting + Outreach or Salesloft + Gmail. Covers CRM, scraping, enrichment, sequences and reply tracking.

Safety and permissions

A connector acts with the permissions of the account you authorise. If you connect an admin account, Claude can do what an admin can do in that tool. Review every action that spends money, sends email, publishes posts or edits CRM data before confirming it. Disconnect a connector from Customize > Connectors as soon as it is no longer needed, and revoke its access in the connected service as well for a complete disconnect. Keep API keys and tokens out of chats, docs and screenshots.

Troubleshooting

Pre-flight checklist

• Connector name, type and server URL copied exactly from this guide
• Correct service account authorised, with the narrowest permissions available
• Read-only test prompt run and one figure verified against the native dashboard
• Team rule agreed: Claude drafts first; a human approves sends, posts and spend
• Owner named for each connector, with a review date to disconnect unused ones

Keep this guide current

Connector availability and endpoints can change, so re-check the connector directory for the latest version before a production rollout. Related titles in this series - Praveen's Guide: Keyword Tool, Praveen's Guide: Google Search Console, Praveen's Guide: Blotato, Praveen's Guide: Apify, Praveen's Guide: Jotform, Praveen's Guide: Shopify, Praveen's Guide: Mailchimp Campaigns and Praveen's Guide: Meta Ads Audit Prompts - cover individual connectors in depth.

Related pages

• Free AI guides (Resources)
• Learn AI
• Contact Praveen