$npx -y skills add indranilbanerjee/digital-marketing-pro --skill connectSet up an MCP connector. Use when: connecting Google Ads, Salesforce, Mailchimp, or any service to the plugin.
| 1 | # /digital-marketing-pro:connect |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | Guide users through connecting a specific MCP integration to the Digital Marketing Pro plugin. Provides platform-specific setup instructions, credential requirements, configuration steps, and verification. This is the user-friendly entry point for adding integrations — it handles the common cases (known connectors with established setup paths) while `/digital-marketing-pro:add-integration` handles custom or unknown MCP servers. |
| 6 | |
| 7 | ## Input Required |
| 8 | |
| 9 | The user must provide (or will be prompted for): |
| 10 | |
| 11 | - **Connector name**: The service to connect — e.g., "google-ads", "salesforce", "mailchimp", "twilio", "deepl". If the user provides a partial or informal name (e.g., "google analytics", "fb ads", "linkedin"), match it to the closest connector in the registry |
| 12 | - **Environment** (optional): Whether they're using Claude Code (supports HTTP + npx) or Cowork (HTTP only). Defaults to auto-detect based on available context. If the requested connector is npx-only and the user is on Cowork, explain the limitation and suggest HTTP alternatives in the same category |
| 13 | |
| 14 | ## Process |
| 15 | |
| 16 | 1. **Look up connector**: Execute `python "${CLAUDE_PLUGIN_ROOT}/scripts/connector-status.py" --action setup-guide --name <connector>` to get the detailed setup guide for the requested connector. If the name doesn't match exactly, search the registry for close matches and suggest the correct name. |
| 17 | |
| 18 | 2. **Check current status**: Execute `python "${CLAUDE_PLUGIN_ROOT}/scripts/connector-status.py" --action check --name <connector>` to determine if the connector is already configured. If already connected, report that and show which skills it powers — ask if the user wants to verify connectivity or reconfigure. |
| 19 | |
| 20 | 3. **Present setup instructions based on transport type**: |
| 21 | |
| 22 | **For HTTP connectors** (Slack, Canva, Figma, HubSpot, Notion, Ahrefs, Similarweb, Klaviyo, Google Calendar, Gmail, Stripe, Asana, Webflow): |
| 23 | - **Nothing is pre-connected.** The shipped `.mcp.json` is empty (`{"mcpServers":{}}`) so a fresh install has zero auto-connecting MCP servers — this is deliberate (it keeps Cowork and multi-tenant installs safe). These HTTP connectors are an **opt-in catalog**, documented in `.mcp.json.connectors-reference`. |
| 24 | - To enable one, the user copies its block from `.mcp.json.connectors-reference` into their own `.mcp.json` (or adds it via `/digital-marketing-pro:add-integration`), then restarts the client. HTTP connectors need no API key in the file — once the server is added, Claude prompts for OAuth on first use. |
| 25 | - Example: "Slack isn't connected yet. Copy the Slack block from `.mcp.json.connectors-reference` into your `.mcp.json` (or run `/digital-marketing-pro:add-integration slack`), restart, then run `/digital-marketing-pro:send-notification` — you'll be prompted to authorize Slack via OAuth." |
| 26 | - List the skills this connector would enable once added |
| 27 | |
| 28 | **For npx connectors** (Google Ads, Meta, Salesforce, Twilio, etc.): |
| 29 | - List the specific environment variables needed with clear descriptions |
| 30 | - Provide platform-specific instructions for obtaining credentials: |
| 31 | - Where to go in the platform's dashboard to create API keys |
| 32 | - What permissions/scopes are needed |
| 33 | - Any prerequisites (developer accounts, app creation, etc.) |
| 34 | - Show the exact `.mcp.json` entry to add (from the setup guide) |
| 35 | - Offer two setup paths: |
| 36 | 1. **Quick**: "Set the environment variables and run `/digital-marketing-pro:add-integration <name>` to configure automatically" |
| 37 | 2. **Manual**: Show the JSON block to add to `.mcp.json` directly |
| 38 | - Note that npx connectors work in Claude Code only, not Cowork |
| 39 | |
| 40 | 4. **Handle unknown connectors**: If the connector name isn't in the registry: |
| 41 | - Search for close matches and suggest them |
| 42 | - If no match found, explain that it's a custom integration and guide them to `/digital-marketing-pro:add-integration` which handles npm package discovery and custom MCP server setup |
| 43 | - List the categories of connectors available so they can explore alternatives |
| 44 | |
| 45 | 5. **Verify after setup** (for npx connectors): After the user confirms they've set up credentials, offer to verify connectivity: |
| 46 | - Check that all required environment variables are set and non-empty |
| 47 | - Suggest running a read-only test via the connector to confirm it works |
| 48 | - Report success or diagnose failure with specific guidance |
| 49 | |
| 50 | ## Output |
| 51 | |
| 52 | A connector setup guide containing: |
| 53 | |
| 54 | - **Connector info**: Name, category, description, transport type (HTTP/npx), and current status (connected/not connected) |
| 55 | - **Skills unlocked**: List of all skills this connector enables, with brief descriptions of what each skill does |
| 56 | - **Setup instructions**: Step-by-step guide appropriate to the transport type — OAuth flow for HTTP, credential se |