MCP Integration Status Dashboard for Marketing Connectors
See which MCP connectors are active in your Claude Code marketing setup, which skills each one powers, and which three to connect next, grouped by CRM, SEO, ads, email and analytics.
You installed a marketing plugin with dozens of skills, but half of them quietly fall back to guesswork because the CRM, analytics or ad-platform connector behind them was never connected. This dashboard shows exactly what's live, what's missing, and which connection unlocks the most.
Who it's for: digital marketers, marketing ops leads, growth marketers, agencies running Claude Code across several client stacks
Example
"Show me which integrations are connected for SEO and advertising" → Coverage summary (e.g. 4 of 19 connectors active), connected vs. available connectors by category with the skills each unlocks, the top 3 to add next, and the exact command to connect each
CLAUDE.md Template
New here? 3-minute setup guide → | Already set up? Copy the template below.
# Integrations
# /dm:integrations
## Purpose
Show a complete integration status dashboard — which MCP connectors are currently connected, which are available but not yet configured, and which skills each connector unlocks. This is the first thing users should check after installing the plugin to understand what capabilities are active and what additional connections they can set up.
## Input Required
The user may optionally provide:
Get new playbooks like this one
One email a week with new Claude Code workflows. Free, like everything here.
No spam. Unsubscribe anytime.
What This Does
Gives you a status dashboard of the MCP connectors behind a Claude Code marketing setup: which are connected, which are available but not set up, and which skills each one powers. It's the first thing to run after installing the plugin, and again whenever a skill gives you generic output where you expected real data.
Important: This Is a Plugin Command, Not a Standalone Template
This playbook is the /dm:integrations command from the Digital Marketing Pro plugin. It works by running scripts/connector-status.py, a script that ships with the plugin, against the plugin's connector registry. Dropping the CLAUDE.md into an empty folder gives Claude the instructions but not the script, so the dashboard has nothing to read.
To use it as intended:
- Install the full plugin from its source repository, following the setup steps in its README.
- Run
/dm:integrationsinside a project where the plugin is active.
If you only want to know what's connected in plain Claude Code, without the plugin, see the next section.
Checking MCP Status Without the Plugin
Claude Code has this built in, just without the marketing-specific grouping:
- Run
/mcpinside a Claude Code session to see every configured MCP server, whether it connected, and to sign in to servers that use OAuth. - Run
claude mcp listin your terminal for the same list outside a session. - Look at
.mcp.jsonin your project root for servers configured at project level, which is the file the plugin's script reads.
What the plugin adds on top is the mapping from each connector to the plugin skills it powers, a per-category coverage count, and advice on what to connect next.
Reading the Dashboard
The plugin sorts connectors into two transport types, and the difference decides how much setup each one takes:
| Type | How it connects | Setup effort | Where it works |
|---|---|---|---|
| HTTP (remote) | Hosted server, you authorize with OAuth the first time a skill needs it | Low: a browser sign-in | Claude Code and other MCP clients |
| npx (local) | Runs on your machine, reads an API key from an environment variable | Higher: create an API key, set the variable | Claude Code only |
That's why the "quick wins" list favors HTTP connectors: you get skill coverage for a sign-in instead of an API-key hunt.
Options
- Filter by category:
crm,seo,advertising,email-marketing,social-media, and others. Useful when you only care about one part of the stack. - Show:
connected,available, orall(default).
Example: "Show available advertising integrations" lists only ad-platform connectors you haven't set up yet, with what each would unlock.
When to Run It
- Right after installing the plugin, to see your starting coverage.
- When a skill returns generic advice instead of numbers from your account. Usually its connector isn't active.
- Before onboarding a new client (for agencies), to check the connectors match that client's stack.
Related Playbooks
- Connect — the same plugin's
/dm:connectcommand, for setting up one connector the dashboard flagged - MCP Server Hub Manager — browse and manage a large catalog of MCP tools
- MCP Server Builder — build your own MCP server when a tool you need has no connector