smartlead

SmartLead MCP Server acts as a centralized interface to access SmartLead's 116+ tools via MCP clients. It provides a guided, auto-configuring installer that wires up various AI tooling integrations (Claude, Cursor, Windsurf, Continue.dev, VS Code, Zed, and more) with your SmartLead account. After installation, you can run the MCP server to automatically detect and configure connected clients, validate API access in real time, and expose all supported endpoints through a unified API layer. Use the provided installer to set up the environment and then leverage the generated MCP endpoints to drive campaigns, manage leads, configure email accounts, and gather analytics across your AI-assisted workflows.

Prerequisites:

• Node.js and npm installed on your machine (recommended latest LTS).
• Access to a SmartLead API key.

1. Install the MCP server using NPX (recommended):

   • Run: npx smartlead-mcp-by-leadmagic install
   • When prompted, provide your SmartLead API key and allow the installer to auto-detect supported tools.

2. Alternative: Global install (if you prefer):

   • Run: npm install -g smartlead-mcp-by-leadmagic
   • Then run: smartlead-mcp-by-leadmagic install

3. After installation, start the MCP server (if it does not auto-start):

   • Follow the installer prompts to start the server, or run the server command provided by the installer documentation.

4. Verify connectivity:

   • Ensure SMARTLEAD_API_KEY is set in your environment if required by the installer.
   • Open the installer UI or console output to confirm successful auto-detection and API validation.

Tips and known considerations:

• The installer auto-detects compatible tools (Claude, Cursor, Windsurf, Continue.dev, VS Code, Zed) and configures MCP clients for you. If a tool is not detected, you may need to install or configure it separately.
• Keep your SmartLead API key secure. Do not commit it to version control.
• The MCP server exposes a large surface area (116+ tools). Use the installer’s validation features to confirm correct end-to-end connectivity before invoking tools in production.
• If you encounter network or permission issues on macOS/Linux, ensure your terminal has the necessary permissions and that network egress is allowed for npm/pnpm/yarn operations.
• Environment variables can be extended in the mcp_config under env to support additional keys required by your environment.