Smartlead MCP Server

Smartlead MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. smaertlead mcp server for Campaign.

What you get

This is a Model Context Protocol (MCP) server for Smartlead campaign management integration. It provides tools for creating and managing campaigns, updating campaign settings, and managing campaign sequences.

• Create new campaigns
• Update campaign schedule settings
• Update campaign general settings
• Get campaign details
• List all campaigns with filtering options
• Manage campaign email sequences (save, get, update, delete)

What the assistant can call

Once Smartlead is connected, these are the calls the assistant has available:

• smartlead_create_campaign — The smartlead_create_campaign tool exposed by this server
• smartlead_update_campaign_schedule — The smartlead_update_campaign_schedule tool exposed by this server
• smartlead_update_campaign_settings — The smartlead_update_campaign_settings tool exposed by this server
• smartlead_get_campaign — The smartlead_get_campaign tool exposed by this server
• smartlead_list_campaigns — The smartlead_list_campaigns tool exposed by this server
• smartlead_save_campaign_sequence — Save a sequence of emails for a campaign with A/B testing variants
• smartlead_get_campaign_sequence — The smartlead_get_campaign_sequence tool exposed by this server
• smartlead_update_campaign_sequence — The smartlead_update_campaign_sequence tool exposed by this server
• smartlead_delete_campaign_sequence — The smartlead_delete_campaign_sequence tool exposed by this server
• smartlead_add_email_account_to_campaign — The smartlead_add_email_account_to_campaign tool exposed by this server
• smartlead_add_lead_to_campaign — The smartlead_add_lead_to_campaign tool exposed by this server
• smartlead_update_lead_in_campaign — The smartlead_update_lead_in_campaign tool exposed by this server

Configuration and credentials

You will need 2 environment variables: SMARTLEAD_API_KEY, SMARTLEAD_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Smartlead's toolset — smartlead_create_campaign, smartlead_update_campaign_schedule, smartlead_update_campaign_settings and 10 more — is a fair guide to whether it matches your workflow. It is maintained by lkm1developer; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Smartlead's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 13 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Smartlead.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the smartlead mcp server does with a few real requests.