# Connect

Connect a known MCP integration: check the registry and status, return exact setup steps.

- Repository: https://github.com/indranilbanerjee/digital-marketing-pro (921 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-10-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add indranilbanerjee/digital-marketing-pro --skill connect -g -a claude-code -y`
Codex: `npx skills add indranilbanerjee/digital-marketing-pro --skill connect -g -a codex -y`
Cursor: `npx skills add indranilbanerjee/digital-marketing-pro --skill connect -g -a cursor -y`
Gemini CLI: `npx skills add indranilbanerjee/digital-marketing-pro --skill connect -g -a gemini-cli -y`

## Description

Connect a known MCP integration: check the registry and status, return exact setup steps. \"connect Google Ads\

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# /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.

The rest: https://github.com/indranilbanerjee/digital-marketing-pro/blob/HEAD/skills/connect/SKILL.md