Help us improve
Share bugs, ideas, or general feedback.
Guides adding custom MCP server integrations to plugins via .mcp.json: searches npm for packages, generates configs with npx commands and env vars, tests connectivity for tools and APIs.
npx claudepluginhub indranilbanerjee/digital-marketing-proHow this skill is triggered — by the user, by Claude, or both
Slash command
/digital-marketing-pro:add-integration [service-name][service-name]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guide users through adding a custom MCP server integration to the Digital Marketing Pro plugin. Search for existing MCP packages that provide the desired service connection, configure the server entry in `.mcp.json` with proper command, arguments, and environment variables, test connectivity to verify the integration works, and document the available tools. Supports both pre-built MCP servers f...
Guides setup of MCP connectors for Google Ads, Salesforce, Mailchimp, and other services to plugins. Checks status, provides credential instructions, .mcp.json configs, and verification.
Guides integrating MCP servers into Claude Code plugins for external tool/service access. Covers .mcp.json configuration, server types (stdio, SSE, HTTP), and authentication.
Guides integration of Model Context Protocol (MCP) servers into Claude Code plugins using .mcp.json or inline plugin.json configs, covering stdio, SSE, HTTP, WebSocket types for external services.
Share bugs, ideas, or general feedback.
Guide users through adding a custom MCP server integration to the Digital Marketing Pro plugin. Search for existing MCP packages that provide the desired service connection, configure the server entry in .mcp.json with proper command, arguments, and environment variables, test connectivity to verify the integration works, and document the available tools. Supports both pre-built MCP servers from npm and custom implementations for proprietary APIs or internal tools.
The user must provide (or will be prompted for):
~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Check for agency credential profiles at ~/.claude-marketing/credentials/ — if agency mode is active, the new integration may need to be mapped to specific client credential sets. Check for agency SOPs at ~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults..mcp.json entry — server name (following the plugin's naming convention: lowercase with hyphens), command (npx for npm packages), args array with the package name and any required flags, env object mapping environment variable names to credential references, and a description field summarizing what the integration provides. Show the user the exact JSON block to add.docs/custom-mcp-guide.md — project structure, required tool definitions, input/output schemas, authentication handling, and error response patterns. Include a starter implementation skeleton for the specific API the user wants to connect, with placeholder endpoints and authentication flow.SERVICE_API_KEY convention), where to add them (.env file in the project root or system environment variables for CI/CD), and how to reference them in the .mcp.json configuration. For agency setups, explain how to add the credentials to the appropriate credential profile at ~/.claude-marketing/credentials/.A complete integration setup report containing:
.mcp.json — server name, command, args, env, and description — formatted and validated against the plugin's configuration schema