This MCP server exposes Smartlead campaign management capabilities over Server-Sent Events (SSE) via a Supergateway-enabled endpoint. After starting the Node server (normally via npm start or by running the built dist/index.js), you can connect clients to the SSE stream at /sse and, if needed, post messages to /message. The server supports creating and updating campaigns, managing campaign scheduling and settings, retrieving campaign details and lists, and handling related entities like email accounts and leads within campaigns. For client integration, you can either connect directly to the SSE URL or bridge the SSE stream to stdio using a local Supergateway instance. The server requires a Smartlead API key and optionally a base API URL and retry/configuration options. Ensure your environment provides SMARTLEAD_API_KEY and, if different, SMARTLEAD_API_URL.

Prerequisites:

• Node.js (LTS) installed
• Access to the Smartlead API and a valid SMARTLEAD_API_KEY

1. Clone the repository: git clone https://github.com/your-org/smartlead-mcp-server.git cd smartlead-mcp-server

2. Install dependencies: npm install

3. Create a .env (optional if you prefer environment variables in the command) and add your API key: echo 'SMARTLEAD_API_KEY=your_api_key_here' > .env

4. Build the project (if a build step is defined): npm run build

5. Run the server directly (stdio mode) or via a process manager. Example: npm start

   or

   node dist/index.js

6. Verify the server is up by checking the health endpoint or attempting to connect to the SSE stream at /sse.

Tips and notes:

• Always keep SMARTLEAD_API_KEY secure. Do not commit it to version control.
• The default SSE endpoint is /sse and the message endpoint (if used) is /message. The health check is at /healthz.
• If deploying via Docker, map the container port 8000 to a host port (e.g., -p 8001:8000) and ensure PORT and related env vars are set accordingly.
• Retry settings (SMARTLEAD_RETRY_*) control resilience against transient API failures; adjust based on network reliability.
• The AlwaysAllow list defines which MCP tools the client can invoke via this server. Keep it aligned with your access policy.
• If you prefer direct SSE connections, prepare your client with the exact SSE URL including the deployed host and port.
• For local debugging, you can run a separate Supergateway client to bridge /sse to local stdio and test command-driven workflows.