Smartlead

Provides an MCP server exposing Smartlead API tools to manage campaigns, leads, email accounts, and analytics.
  • typescript

0

GitHub Stars

typescript

Language

6 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "griffinwork40-smartlead-mcp": {
      "command": "node",
      "args": [
        "/absolute/path/to/smartlead-mcp/build/index.js"
      ],
      "env": {
        "SMARTLEAD_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

A dedicated MCP server that exposes the Smartlead API as a set of tools you can access through your AI assistant. It lets you manage campaigns, leads, email accounts, and analytics using natural language, while handling authentication and API requests automatically.

How to use

You connect your MCP client to the Smartlead MCP Server and start issuing high-level actions in natural language. You can manage campaigns, add or list leads, handle email accounts, and retrieve analytics all through the AI assistant. Your client translates your requests into MCP tool calls and returns results in a readable format.

How to install

Prerequisites: Node.js and npm must be installed on your system.

Install dependencies for the project.

npm install

Build the project to produce the MCP server bundle.

npm run build

Obtain your Smartlead API key to authorize requests to the Smartlead API.

Set up environment variables for the MCP server.

cp .env.example .env

Edit the environment file to include your API key.

# Edit .env and add your API key
SMARTLEAD_API_KEY=your_api_key_here

Configuration

Configure how you connect to the Smartlead MCP Server from your MCP client. You can run the server locally as a standard MCP stdio process or connect to a remote MCP endpoint if one is provided.

Local deployment configuration (stdio) shown for Claude Desktop clients and other MCP clients.

{
  "mcpServers": {
    "smartlead": {
      "command": "node",
      "args": ["/absolute/path/to/smartlead-mcp/build/index.js"],
      "env": {
        "SMARTLEAD_API_KEY": "your_api_key_here"
      }
    }
  }
}

Claude Desktop and other MCP clients can use the following configurations to connect to the local server.

// Claude Desktop config (macOS)
{
  "mcpServers": {
    "smartlead": {
      "command": "node",
      "args": ["/absolute/path/to/smartlead-mcp/build/index.js"],
      "env": {
        "SMARTLEAD_API_KEY": "your_api_key_here"
      }
    }
  }
}
// Claude Desktop config (Windows)
{
  "mcpServers": {
    "smartlead": {
      "command": "node",
      "args": ["/absolute/path/to/smartlead-mcp/build/index.js"],
      "env": {
        "SMARTLEAD_API_KEY": "your_api_key_here"
      }
    }
  }
}

Security

Never commit your API key to version control. Store keys as environment variables and pass them to the MCP server at runtime.

The API key is required to authenticate requests to Smartlead. Keep it in a secure location and rotate regularly.

Troubleshooting

If you encounter issues starting the server, verify that SMARTLEAD_API_KEY is set in the environment where the MCP server runs.

Common API errors include 401 Unauthorized for an invalid API key, 404 Not Found for non-existent campaigns/leads, and 429 Too Many Requests when hitting rate limits.

Development

Build the project to keep your local development environment up to date.

npm run build

Available tools

create_campaign

Create a new email campaign

get_campaign

Get campaign details by ID

list_campaigns

List all campaigns

update_campaign_schedule

Update scheduling settings for campaigns

update_campaign_settings

Update general settings for campaigns

update_campaign_status

Pause, stop, or start campaigns

delete_campaign

Delete a campaign

list_campaign_email_accounts

List email accounts associated with a campaign

add_campaign_email_accounts

Add email accounts to a campaign

remove_campaign_email_accounts

Remove email accounts from a campaign

list_campaign_leads

List leads in a campaign (with pagination)

add_leads_to_campaign

Add up to 100 leads to a campaign

pause_lead

Pause a lead in a campaign

resume_lead

Resume a paused lead

delete_lead_from_campaign

Delete a lead from a campaign

unsubscribe_lead_from_campaign

Unsubscribe lead from a specific campaign

get_lead_by_email

Get lead details by email address

unsubscribe_lead_globally

Unsubscribe lead from all campaigns

get_lead_campaigns

Get all campaigns for a lead

list_email_accounts

List all email accounts

get_email_account

Get email account details

update_warmup_settings

Configure email warmup settings

get_warmup_stats

Get warmup statistics (last 7 days)

reconnect_failed_accounts

Reconnect failed email accounts

get_campaign_statistics

Get detailed campaign statistics

get_campaign_analytics

Get top-level campaign analytics

get_campaign_analytics_by_date

Get analytics for a date range

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational