/digital-marketing-pro:connect

/digital-marketing-pro:connect

Script location. If your host does not set ${CLAUDE_PLUGIN_ROOT}, the scripts are in this plugin's scripts/ folder, next to skills/. Run them with Python 3.10 or newer: python, or python3 where python is not found (macOS, many Linux systems).

Purpose

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.

Input Required

The user must provide (or will be prompted for):

• 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
• 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

Process

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.

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.

3. Present setup instructions based on transport type:

   For HTTP connectors (the registry-backed ones: Slack, Canva, Figma, HubSpot, Ahrefs, Similarweb, Klaviyo, Amplitude, Google Calendar, Gmail, and the official ad-platform servers meta-ads, google-ads-mcp, amazon-ads-mcp):

   • Nothing is pre-connected. No .mcp.json ships (it is gitignored), 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.
   • 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.
   • 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."
   • Notion, Stripe, Asana, and Webflow are catalog-only HTTP servers: configure them directly from .mcp.json.connectors-reference the same way, but they are not in the connector registry, so /digital-marketing-pro:doctor and connector-status.py will not report on them.
   • List the skills this connector would enable once added

   Official ad-platform and CRM servers (checked 2026-10-04; see the CONNECTORS.md section "Official ad-platform and CRM MCP servers"): the setup guide returns an access field and a setup_note. Read both to the user:

   • meta-ads (https://mcp.facebook.com/ads, open beta): read + write, with a business-authenticated Meta login.
   • google-ads-mcp: read-only. It runs locally via pipx (Claude Code only), or the user self-hosts it over Streamable HTTP, so the URL has a <...> placeholder.
   • amazon-ads-mcp: partners with active Amazon Ads API credentials only. The endpoint comes from their API onboarding.
   • hubspot (https://mcp.hubspot.com, GA): OAuth 2.1 + PKCE with the user's connector app credentials.

   For every read-write server, tell the user plainly:

   • writes happen only through /digital-marketing-pro:launch-ad-campaign's typed approval gate;
   • new ad objects are created PAUSED;
   • DMP never deletes through these servers.