Connectors
May 16, 2026 · View on GitHub
How tool references work
Plugin files use ~~category as a placeholder for whatever tool the user connects in that category. For example, ~~CRM might mean HubSpot, Salesforce, or any other CRM with an MCP server.
Plugins are tool-agnostic — they describe workflows in terms of categories (SEO, email marketing, CRM, etc.) rather than specific products. The .mcp.json pre-configures specific MCP servers, but any MCP server in that category works.
Connectors for this plugin
| Category | Placeholder | Included servers | Other options |
|---|---|---|---|
| Chat | ~~chat | Slack | Microsoft Teams |
| Design | ~~design | Canva, Figma | Adobe Creative Cloud |
| CRM | ~~CRM | HubSpot | Salesforce, Pipedrive, Zoho |
| Product analytics | ~~product analytics | Amplitude | Mixpanel, Google Analytics |
| Knowledge base | ~~knowledge base | Notion | Confluence, Guru |
| SEO | ~~SEO | Ahrefs, Similarweb | Semrush, Moz, DataForSEO |
| Email marketing | ~~email marketing | Klaviyo | Mailchimp, Brevo, Customer.io, SendGrid |
| Calendar | ~~calendar | Google Calendar | Outlook Calendar |
~~email | Gmail | Outlook | |
| Payments | ~~payments | Stripe | — |
| Project management | ~~project management | Asana | Linear, Jira, Monday.com |
| CMS | ~~CMS | Webflow | WordPress, HubSpot CMS |
Platform-level integrations
Some services are connected at the Claude platform level rather than through MCP. These are managed in Claude Desktop → Settings → Integrations and work automatically in Cowork sessions.
| Service | Platform integration | MCP alternative |
|---|---|---|
| Google Drive | Yes — connect in Settings → Integrations | Also available via npx (mcp-google-drive) |
| Google Docs | Yes — connect in Settings → Integrations | Also available via npx (mcp-google-docs) |
Platform-level integrations work even if they don't appear in the /digital-marketing-pro:integrations connector dashboard.
Categories without HTTP connectors (Claude Code only)
The following categories require local npx/stdio MCP servers. They work in Claude Code but not in Cowork. See .mcp.json.example for configuration.
| Category | Available via npx | When HTTP becomes available |
|---|---|---|
| Productivity | Google Drive, Google Sheets, Google Docs | Google Drive/Docs also available as platform integration |
| Advertising | Google Ads, Meta Ads, LinkedIn Ads, TikTok Ads | Recommended: use a unified ads MCP (see "Unified ads MCPs" section below) instead of one stdio server per platform. Synter covers 14 platforms in one endpoint; Ryze covers Google + Meta + GA4 with confirmation patterns; Northbeam is self-hosted. All three are HTTP and Cowork-compatible. Per-platform OAuth still applies. |
| Analytics | Google Analytics, Google Search Console | Connect via Connectors panel when available |
| Social media | Buffer, Twitter/X, LinkedIn | Connect via Connectors panel when available |
| SMS/Messaging | Twilio | Connect via Connectors panel when available |
| Translation | DeepL, Sarvam AI | Connect via Connectors panel when available |
| Database | Supabase, PostgreSQL | Connect via Connectors panel when available |
Unified ads MCPs (added v3.4, corrected v3.4.1)
As of May 2026, three options exist for unifying multiple ad-platform connectors. Pick ONE — overlap creates duplicate tools. Configuration lives in .mcp.json.connectors-reference under _section_unified_ads_mcps; copy the entry you want into .mcp.json to activate. All endpoint URLs and platform-coverage claims below were verified May 2026 — re-verify before production use as these are early-stage services and endpoints may move.
| Option | Platforms covered | Auth | Source | When to pick |
|---|---|---|---|---|
| synter-media-ai | 7 platforms — Google, Meta, LinkedIn, Microsoft, Reddit, TikTok, X | X-Synter-Key header | github.com/Synter-Media-AI/mcp-server | Agencies running 3+ of these platforms |
| ryze-ai-google-ads | Google Ads (primary); separate per-platform connectors for Meta + GA4 via app.get-ryze.ai/mcp-connector | OAuth on first connect (managed service) | get-ryze.ai | Google-Ads-heavy teams that want a vendor-managed connector |
| northbeam-mcp-selfhosted | Google + Meta + LinkedIn + TikTok | BYO per-platform OAuth or API keys (self-hosted) | github.com/mattcoatsworth/Northbeam-MCP-Server (community-maintained) | Org policy forbids sending OAuth tokens to a third-party SaaS |
All three are HTTP — fully Cowork-compatible. They replace the per-platform stdio servers in .mcp.json.example for teams who want one ads tool surface instead of one per platform.
Managing connectors
Use these skills to discover and manage your integrations:
| Skill | What it does |
|---|---|
/digital-marketing-pro:integrations | Status dashboard — see what's connected, what's available, which skills each connector unlocks |
/digital-marketing-pro:connect <name> | Guided setup — step-by-step instructions for connecting a specific service (e.g., /digital-marketing-pro:connect google-ads) |
/digital-marketing-pro:add-integration | Custom setup — add any MCP server not in the registry (npm packages or custom APIs) |
/digital-marketing-pro:credential-switch | Agency mode — switch active credentials when managing multiple client accounts |
Advanced configuration (Claude Code)
For Claude Code CLI users who want the full 68-server configuration with npx/stdio transports, rename the example file:
cp .mcp.json.example .mcp.json
This replaces the HTTP-only configuration with the full set of local MCP servers. Requires Node.js, npx, and the appropriate API keys configured as environment variables.