smartlead

The Smartlead MCP Server provides a simplified interface to Smartlead's email marketing features, exposing campaign management, lead management, analytics, webhooks, and client management to automation tools and AI assistants. It supports integrations through a lightweight middleware layer that can be run via npx or as part of a Smithery deployment. Once running, you can access a streaming event interface (SSE) for real-time updates and a message endpoint for programmatic interactions with Smartlead resources. The server is designed to be developer-friendly, prompting for your Smartlead API key on first run and then enabling all features by default without requiring a separate license.

You can use the Claude Extension or n8n integration examples provided in the README to connect your tools. For Claude, you can start the server with npx smartlead-mcp-server start and configure the integration to point to the appropriate endpoints. For n8n, you can run the server using npx smartlead-mcp-server sse to enable server-sent events and then point your n8n MCP Client to the SSE URL and Message URL. The server exposes capabilities such as Campaign & Lead Management, Statistics and Analytics, Smart Delivery & Webhooks, Client Management, Smart Senders, and Download Tracking and Analytics, giving you a unified API surface for routine marketing workflows.

In practice, you’ll typically authenticate with your Smartlead API key, then issue higher-level actions like creating campaigns, managing leads, or retrieving analytics. The Download Tracking features extend visibility into campaign data and download statistics, with dedicated tools for exporting campaign data and viewing statistics, which are tracked locally under ~/.smartlead-mcp/downloads.json for analytics purposes.

Prerequisites:

• Node.js (recommended: LTS version) and npm installed on your system.
• Access to a terminal/command prompt with internet connectivity.

Install (npm):

1. Install the MCP server package globally via npm (or run via npx without installation):

npm install -g smartlead-mcp-server@1.2.1

2. Run the server (using npx style if you prefer):

npx smartlead-mcp-server start

3. Alternatively, install through Smithery for Claude Desktop integration:

npx -y @smithery/cli install @jean-technologies/smartlead-mcp-server-local --client claude

4. If you’re configuring via a client (example integration):

# As shown in the integration example, you can wire your client with:
npx smartlead-mcp-server sse

Prerequisites to configure API access:

• Obtain your Smartlead API key from your Smartlead account or the developer portal.
• Set the API key in your environment or via the integration configuration (see env example in the mcp_config).

Notes:

• The first run will prompt for your Smartlead API Key. No separate license key is required.
• If you prefer non-interactive setup, you can pass the API key via an environment variable (SMARTLEAD_API_KEY) or use appropriate CLI flags as supported by the server.

Environment and configuration tips:

• SMARTLEAD_API_KEY must be kept secret; do not commit it to version control.
• The server exposes endpoints for SSE (real-time updates) and message-based interactions; ensure your firewall or proxy allows access to the required ports (default 3000 for SSE in many local setups).
• Download tracking is stored locally at ~/.smartlead-mcp/downloads.json for analytics; ensure the parent directory exists or the server has permissions to create it.
• If you need to customize the server beyond defaults, you can override environment variables or modify the configuration file generated by the onboarding flow.
• Common issues often relate to API key permissions or network access; verify that the API key has access to the required Smartlead resources and that outbound requests are not blocked by a corporate proxy.