home / mcp / smartlead mcp server

Smartlead MCP Server

Local version of Smartlead MCP for quick download and deployment to MCP compatible clients or n8n.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "jonathan-politzki-smartlead-mcp-server": {
      "command": "npx",
      "args": [
        "smartlead-mcp-server",
        "start"
      ],
      "env": {
        "SMARTLEAD_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

You can run Smartlead’s MCP Server locally to interact with Smartlead’s email marketing features from AI assistants and automation tools. This server exposes practical actions like campaign management, analytics, and delivery controls, and you control access via your API key. With the MCP server, you can start the service from your shell or integrate it into automation workflows using standard MCP client patterns.

How to use

Connect your MCP client to the Smartlead MCP Server by starting the local MCP service and pointing your client at the same runtime. You’ll typically run the server in one terminal and use your client to send requests for campaigns, leads, analytics, and delivery preferences. When you start the server, provide your Smartlead API key to authenticate and enable features. The server supports both Claude-style and n8n-style integrations, so you can pick the workflow that matches your setup.

How to install

Prerequisites you need before installation: Node.js installed on your machine (LTS version recommended). You should also have npm available in your shell. If you prefer, you can run the server directly with npx without a global install.

Step 1: Install the MCP server package locally (optional) or prepare to run via npx.

Step 2: Start the server using the provided CLI commands. The following commands start the server with the appropriate configuration:

npx smartlead-mcp-server start

Step 3: When using Claude or another MCP client, configure the client to launch the MCP server with your API key via an environment variable. For example, set SMARTLEAD_API_KEY to your key before starting the server.

Additional configuration and usage notes

Two common startup patterns are supported. You can either start the server directly to listen for client connections or run a dedicated streaming/event endpoint (SSE) for n8n integrations. In both cases, you must supply your API key to access Smartlead features.

Example startup options you may encounter include starting with the standard start command or an SSE mode for streaming updates. Use the mode that matches your client integration.

Security and credentials

Keep your API key secret. Do not share it in client configurations or public scripts. Store it in a secure environment variable (for example SMARTLEAD_API_KEY) and reference it from your MCP client or startup script. If you suspect your key was exposed, rotate it immediately and update all client configurations.

Notes on downloads tracking and analytics

Download analytics are collected to help you understand engagement. The server tracks download events and writes analytics data to a local file path for later review. If you need to review analytics, check the designated data store location used by the server.

Available tools

smartlead_download_campaign_data

Downloads campaign data with tracking for analytics, supporting different download formats like json or csv.

smartlead_view_download_statistics

Retrieves download statistics over a specified time period and grouping.

start_server

Launches the MCP server using the provided start command and environment variables.