mcp -smtp

This MCP server provides SMTP-based email sending capabilities for Claude and other MCP-compatible assistants. It supports managing multiple SMTP configurations, creating reusable HTML email templates, and sending both single emails and bulk campaigns with batching and rate limiting. Core tools exposed by the server include: send-email for sending a single email (with optional template support and inline template data), send-bulk-emails for batched delivery to many recipients, get-smtp-configs to list configured SMTP servers, add-smtp-config to add new SMTP configurations, update-smtp-config to modify existing configurations, delete-smtp-config to remove one, and get-email-templates / add-email-template / update-email-template / delete-email-template to manage templates. To use these tools, you typically configure one or more SMTP servers, create templates, and then invoke the respective commands with recipients, subjects, bodies, and any template data. The template system supports variables that get populated at send time, enabling dynamic, personalized content across emails.

Prerequisites:

• Node.js 14+ and npm installed
• Access to an SMTP server or service (e.g., Gmail, SES, SendGrid)

Install via Smithery (recommended):

npx -y @smithery/cli install @samihalawa/mcp-server-smtp --client claude

Manual installation:

# Clone the repository
git clone https://github.com/samihalawa/mcp-server-smtp.git
cd mcp-server-smtp

# Install dependencies
npm install

# Build the server
npm run build

Run locally (example):

npm start

If you prefer a different deployment method, ensure you build artifacts are available at build/index.js and reference that path in your MCP config as shown in the mcp_config example.

Tips and considerations:

• Ensure your chosen SMTP configurations are valid (host, port, TLS, and authentication).
• When using templates, provide templateData to populate variables like name or company to personalize emails.
• For bulk sends, adjust batchSize and delayBetweenBatches to respect recipient limits and avoid throttling.
• The server exposes an API-friendly interface; use get-email-logs to audit delivery history and troubleshoot failures.
• If you encounter path or node resolution issues in production, verify NODE_PATH and PATH in the environment block of your MCP config.
• Security: do not commit real SMTP credentials in configuration files. Prefer environment-based secrets management where possible.