How do I install Java MCP Server For SMTP Mailing?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Java MCP Server For SMTP Mailing need an API key?

No required environment variable is listed on this record.

What transport does Java MCP Server For SMTP Mailing use?

Java MCP Server For SMTP Mailing runs locally over stdio.

Servidor MCP Java MCP Server For SMTP Mailing

Q: When was Java MCP Server For SMTP Mailing last checked?

Last checked 2026-10-28. A Model Context Protocol (MCP) server (using java sdk 0.11.0) that provides email sending capabilities through SMTP integration. This server acts as a bridge between MCP-compatible AI assistants (like Claude Desktop) and email services.

Potencia tu agente

Añadir este servidor

Install from the publisher. Not a PlugMCP endpoint.

Ejecutar en PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Ejecutar en PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Abrir

Server facts

Local

Transport: stdio
Last checked: 2026-10-28

Stars: 2
Tools: —
Uptime: —

Overview

About Java MCP Server For SMTP Mailing

A Model Context Protocol (MCP) server (using java sdk 0.11.0) that provides email sending capabilities through SMTP integration. This server acts as a bridge between MCP-compatible AI assistants (like Claude Desktop) and email services.

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

SMTP MCP Server (Java SDK 0.11.0)

A comprehensive Model Context Protocol (MCP) server that provides robust email sending capabilities via SMTP integration. This server supports multiple transport protocols (STDIO, SSE, and Streamable HTTP) and exposes email functionality through both MCP tools and REST endpoints, making it ideal for integrating email capabilities into AI applications, automation workflows, and testing environments.

🚀 Features

Core Functionality

Multiple Transport Protocols: STDIO, Server-Sent Events (SSE), and Streamable HTTP
MCP Tool Integration: Provides a send-email tool for MCP clients
REST API: Simple REST endpoints for testing and integration
Gmail SMTP Support: Pre-configured for Gmail SMTP with TLS security
Multiple Recipients: Support for TO, CC, and BCC recipients
Health Monitoring: Built-in health check endpoints
Claude Desktop Compatible: Ready-to-use with Claude Desktop and other MCP clients

Advanced Features

Rich Email Formatting: Support for HTML and plain text emails
Attachment Support (planned): File attachment capabilities
Email Templates (planned): Reusable email templates
Retry Mechanism: Automatic retry on failed email deliveries
Rate Limiting: Built-in protection against spam and overuse
Comprehensive Logging: Detailed logs for debugging and monitoring

📋 Prerequisites

Java 21 or higher
Maven 3.6+
Gmail account with app-specific password (or other SMTP server credentials)
MCP Client (Claude Desktop, custom clients, or MCP Inspector for testing)

🏗️ Architecture Overview

┌─────────────────┐    ┌──────────────────┐    ┌─────────────────┐
│   MCP Client    │    │   MCP Server     │    │   SMTP Server   │
│  (Claude, etc.) │◄───┤  (This Project)  │────►│   (Gmail, etc.) │
└─────────────────┘    └──────────────────┘    └─────────────────┘
                              │
                         ┌────▼────┐
                         │ REST API│
                         │ Testing │
                         └─────────┘

The application consists of:

MCP Server: Handles MCP protocol communication via multiple transports
Email Service: Core SMTP email sending functionality with JavaMail
REST Endpoints: Additional HTTP endpoints for testing and health checks
Transport Layer: Supports STDIO, SSE, and Streamable HTTP protocols
Configuration Layer: Flexible configuration for different SMTP providers

🛠️ Installation & Building

1. Clone the Repository

git clone https://github.com/RayenMalouche/Java-MCP-Server-For-SMTP-Mailing.git
cd Java-MCP-Server-For-SMTP-Mailing

2. Configure Email Settings

Edit the SMTP configuration in Application.java:

// SMTP Configuration - Update these values
private static final String SMTP_USERNAME = "[email protected]";
private static final String SMTP_PASSWORD = "your-app-password";
private static final String SMTP_HOST = "smtp.gmail.com";
private static final int SMTP_PORT = 587;
private static final boolean SMTP_TLS_ENABLED = true;
private static final boolean SMTP_SSL_ENABLED = false;

3. Build the Project

# Clean build
mvn clean compile

# Create JAR file
mvn clean package -DskipTests

# Build with tests (optional)
mvn clean package

⚙️ Configuration

Gmail App Password Setup

Enable 2-factor authentication on your Gmail account
Go to Google Account settings > Security > App passwords
Generate a new app password for this application
Use the generated password in the SMTP_PASSWORD field

Alternative SMTP Providers

Microsoft Outlook/Hotmail

private static final String SMTP_HOST = "smtp-mail.outlook.com";
private static final int SMTP_PORT = 587;
private static final boolean SMTP_TLS_ENABLED = true;

Yahoo Mail

private static final String SMTP_HOST = "smtp.mail.yahoo.com";
private static final int SMTP_PORT = 587;
private static final boolean SMTP_TLS_ENABLED = true;

Custom SMTP Server

private static final String SMTP_HOST = "your-smtp-server.com";
private static final int SMTP_PORT = 25; // or 465/587
private static final boolean SMTP_TLS_ENABLED = true;

📖 Usage

Finding Required Paths

Before using the server, identify these paths on your system:

Project Path

Windows: Right-click folder → Properties → Location

Example: C:\Users\YourName\Documents\Java-MCP-Server-For-SMTP-Mailing

macOS/Linux:

cd /path/to/project && pwd
# Example: /home/username/Java-MCP-Server-For-SMTP-Mailing

Java Executable Path

Windows:

where java
# Example: C:\Program Files\Common Files\Oracle\Java\javapath\java.exe

macOS/Linux:

which java
# Example: /usr/bin/java or /opt/homebrew/bin/java

Java Home Path

Windows:

echo %JAVA_HOME%
# Example: C:\Program Files\Java\jdk-21

macOS/Linux:

echo $JAVA_HOME
# Example: /usr/lib/jvm/java-21-openjdk

1. STDIO Transport (Recommended for Claude Desktop)

Testing with MCP Inspector

# From inside your project directory:

# 1. Start the server
java -jar target/RayenMalouche-0.0.1-SNAPSHOT.jar --stdio

# 2. In another terminal, run the inspector
npx @modelcontextprotocol/inspector java -jar "<FULL_PATH_TO_PROJECT>/target/RayenMalouche-0.0.1-SNAPSHOT.jar" --stdio

Claude Desktop Integration

Windows Configuration (%APPDATA%\Claude\config.json):

{
  "mcpServers": {
    "smtp-email-server": {
      "command": "<JAVA_EXECUTABLE_PATH>",
      "args": [
        "-jar",
        "<FULL_PATH_TO_PROJECT>\\target\\RayenMalouche-0.0.1-SNAPSHOT.jar",
        "--stdio"
      ],
      "env": {
        "JAVA_HOME": "<JAVA_HOME_PATH>"
      }
    }
  }
}

macOS/Linux Configuration (~/Library/Application Support/Claude/config.json or ~/.config/Claude/config.json):

{
  "mcpServers": {
    "smtp-email-server": {
      "command": "<JAVA_EXECUTABLE_PATH>",
      "args": [
        "-jar",
        "<FULL_PATH_TO_PROJECT>/target/RayenMalouche-0.0.1-SNAPSHOT.jar",
        "--stdio"
      ],
      "env": {
        "JAVA_HOME": "<JAVA_HOME_PATH>"
      }
    }
  }
}

Note: The env section is optional but recommended for consistency.

2. Server-Sent Events (SSE) Transport

Start SSE Server

java -jar target/RayenMalouche-0.0.1-SNAPSHOT.jar --sse

Testing with MCP Inspector

npx @modelcontextprotocol/inspector java -jar "<FULL_PATH_TO_PROJECT>/target/RayenMalouche-0.0.1-SNAPSHOT.jar" --sse

Direct MCP Client Connection

Connect your MCP client to: http://localhost:45450/sse

3. Streamable HTTP Transport

Start HTTP Server

java -jar target/RayenMalouche-0.0.1-SNAPSHOT.jar --streamable-http

Testing with MCP Inspector

npx @modelcontextprotocol/inspector java -jar "<FULL_PATH_TO_PROJECT>/target/RayenMalouche-0.0.1-SNAPSHOT.jar" --streamable-http

🧪 Testing

REST API Testing

Send Email

curl -X POST http://localhost:45450/api/test-email \
  -H "Content-Type: application/json" \
  -d '{
    "to": "[email protected]",
    "subject": "Test Email from MCP Server",
    "body": "This is a test email sent via the MCP SMTP server!",
    "cc": "[email protected]",
    "bcc": "[email protected]"
  }'

Health Check

curl http://localhost:45450/api/health

Using Postman

Import the endpoints into Postman
Base URL: http://localhost:45450
Endpoints:
- POST /api/test-email (Email sending)
- GET /api/health (Health check)

MCP Tool Testing via Claude Desktop

After setting up Claude Desktop integration, you can test by asking Claude:

"Send an email to [email protected] with the subject 'Meeting Reminder' and body 'Don't forget about our meeting tomorrow at 2 PM.'"

Claude will use the MCP tool to send the email through your configured SMTP server.

📚 API Reference

MCP Tool: send-email

Parameters:

to (required): Recipient email address
subject (required): Email subject line
body (required): Email body content
cc (optional): CC email address
bcc (optional): BCC email address

Example Usage in MCP Client:

{
  "tool": "send-email",
  "parameters": {
    "to": "[email protected]",
    "subject": "Hello from MCP",
    "body": "This email was sent via Model Context Protocol!",
    "cc": "[email protected]"
  }
}

REST Endpoints

POST /api/test-email

Send an email via REST API.

Request Body:

{
  "to": "[email protected]",
  "subject": "Email Subject",
  "body": "Email body content",
  "cc": "[email protected]",
  "bcc": "[email protected]"
}

Success Response (200 OK):

{
  "status": "success",
  "message": "Email sent successfully",
  "details": {
    "to": "[email protected]",
    "subject": "Email Subject",
    "cc": "[email protected]",
    "bcc": "[email protected]"
  }
}

Error Response (500 Internal Server Error):

{
  "status": "error",
  "message": "Failed to send email: [error details]",
  "errorType": "AuthenticationFailedException"
}

GET /api/health

Check server health status.

Response (200 OK):

{
  "status": "UP",
  "timestamp": "2025-08-29T10:30:00Z",
  "smtp": {
    "status": "UP",
    "host": "smtp.gmail.com",
    "port": 587
  }
}

Transport Protocol Comparison

Transport	Use Case	Connection	Pros	Cons
STDIO	Claude Desktop, Direct integration	Process pipes	Simple, Direct, Efficient	Requires process management
SSE	Web applications, Real-time	HTTP/SSE	Real-time updates, Web-friendly	More complex setup
Streamable HTTP	Testing, REST clients	HTTP/JSON	Easy testing, Standard HTTP	Less efficient for real-time

Server Endpoints (HTTP Transports)

Endpoint	Method	Description
`/message`	POST	MCP protocol endpoint (Streamable HTTP)
`/sse`	GET	Server-Sent Events endpoint
`/api/test-email`	POST	REST endpoint for sending emails
`/api/health`	GET/POST	Health check endpoint

🔗 Related Projects

This server is part of a comprehensive MCP ecosystem:

1. MCP Client Dataset Creating Assistant

Purpose: AI-powered dataset generation using web scraping
Integration: Uses this SMTP server for completion notifications
Transport: SSE connection to this server
Use Case: Automatically email generated datasets to users

2. AI Agents Performance Testing MCP Server

Purpose: Performance testing and benchmarking of MCP clients
Integration: Can test this SMTP server's performance under load
Features: Load testing, metrics collection, cost analysis
Use Case: Validate email server performance in production scenarios

3. AI Agents Performance Testing MCP Client

Purpose: Client application that connects to performance testing server
Integration: Can use this SMTP server for test result notifications
Features: Automated testing workflows, result reporting
Use Case: End-to-end testing of MCP email workflows

Integration Examples

With Dataset Creation Assistant

// The dataset assistant sends completion emails like:
{
  "to": "[email protected]",
  "subject": "Dataset Generation Complete - 150 samples created",
  "body": "Your requested dataset has been generated successfully. Total samples: 150. Processing time: 45 seconds. Dataset available at: /datasets/company-solutions-2025-08-29.json"
}

With Performance Testing

// Performance test results notification:
{
  "to": "[email protected]",
  "subject": "MCP Performance Test Results - Dataset Assistant",
  "body": "Performance test completed. Average response time: 12.5s. Success rate: 95%. Total cost: $0.45. Full report attached."
}

🐛 Troubleshooting

Common Issues

1. Authentication Failed

Symptoms: Email sending fails with authentication error

Solutions:

Ensure you're using an app-specific password for Gmail (not your account password)
Verify 2FA is enabled on your Google account
Double-check the username and password in Application.java
Test SMTP credentials with a simple email client

Debug Steps:

# Enable detailed JavaMail debug logging
java -Dmail.debug=true -jar target/RayenMalouche-0.0.1-SNAPSHOT.jar --stdio

2. Connection Refused

Symptoms: Cannot connect to SMTP server

Solutions:

Check if SMTP server settings are correct
Verify firewall allows outbound connections on port 587
Ensure TLS settings match your SMTP provider requirements
Try different SMTP ports (25, 465, 587)

Network Test:

# Test SMTP server connectivity
telnet smtp.gmail.com 587

3. Port Already in Use

Symptoms: Server fails to start with port binding error

Solutions:

The server uses port 45450 by default
Stop any existing processes using the port
Or modify the port in Application.java

Check Port Usage:

# Windows
netstat -ano | findstr 45450

# macOS/Linux  
lsof -i :45450

4. MCP Inspector Connection Issues

Symptoms: Inspector cannot connect to MCP server

Solutions:

Ensure the server is running before starting the inspector
Check that the correct transport argument is used (--stdio, --sse, --streamable-http)
Verify the JAR file path is correct and absolute
Check server logs for startup errors

5. Claude Desktop Integration Issues

Symptoms: Claude doesn't recognize the email tool

Solutions:

Verify config.json file location and syntax
Restart Claude Desktop after configuration changes
Check Java paths are absolute and correct
Ensure JAR file is built and accessible
Verify JAVA_HOME environment variable

Configuration Validation:

# Test Java path
"<JAVA_EXECUTABLE_PATH>" -version

# Test JAR file
"<JAVA_EXECUTABLE_PATH>" -jar "<FULL_PATH_TO_PROJECT>/target/RayenMalouche-0.0.1-SNAPSHOT.jar" --stdio

Debug Mode

Enable comprehensive logging:

# Full debug mode with JavaMail debugging
java -Dmail.debug=true -Dlogging.level.com.mcp=DEBUG -jar target/RayenMalouche-0.0.1-SNAPSHOT.jar --stdio

Testing Recommendations

Start with STDIO: Easiest to test and debug
Use REST endpoints: Test email functionality independently of MCP
Verify with Inspector: Confirm MCP protocol integration works
Check logs: Monitor console output for detailed error messages
Test email delivery: Send to a test email account you control
Validate SMTP settings: Use a separate email client to verify SMTP credentials

📊 Performance & Monitoring

Performance Characteristics

Startup Time: ~5-10 seconds (including SMTP connection validation)
Email Sending: ~1-3 seconds per email (depends on SMTP server)
Memory Usage: ~100-200 MB (varies with Java heap size)
Throughput: Up to 100 emails/minute (Gmail rate limits apply)

Monitoring

Health Check Endpoint

# Check server status
curl http://localhost:45450/api/health

# Expected response
{
  "status": "UP",
  "smtp": {
    "status": "UP",
    "host": "smtp.gmail.com", 
    "port": 587
  }
}

Log Monitoring

# Monitor real-time logs
java -jar target/RayenMalouche-0.0.1-SNAPSHOT.jar --stdio | tee server.log

# Search for errors
grep -i error server.log
grep -i exception server.log

Rate Limiting

Gmail and other providers have rate limits:

Gmail: ~100 emails/day for free accounts, higher for paid
Outlook: ~300 emails/day for personal accounts
Yahoo: ~100 emails/day

Implement client-side rate limiting for production use.

🔧 Dependencies

Spring Boot 3.5.4: Application framework
MCP SDK 0.11.0: Model Context Protocol implementation
Eclipse Jetty 12.0.18: Embedded server for HTTP transports
Jakarta Mail 2.0.1: Email sending functionality
Jackson 2.15.2: JSON processing
SLF4J + Logback: Logging framework

🔒 Security Notes

Production Considerations

Never commit credentials to version control

Use environment variables for sensitive configuration:

export [email protected]
export SMTP_PASSWORD=your-app-password

Implement rate limiting for REST endpoints to prevent abuse
Use TLS encryption for all SMTP connections
Consider OAuth2 instead of app passwords for enterprise deployments
Validate and sanitize all email inputs to prevent injection attacks

Environment Variable Configuration

// Example environment variable usage
private static final String SMTP_USERNAME = System.getenv("SMTP_USERNAME");
private static final String SMTP_PASSWORD = System.getenv("SMTP_PASSWORD");

🤝 Contributing

We welcome contributions! Here's how to get started:

Development Setup

Fork the repository

Clone your fork:

git clone https://github.com/yourusername/Java-MCP-Server-For-SMTP-Mailing.git

Create a feature branch:

git checkout -b feature/amazing-feature

Make your changes and test thoroughly
Test with all transport protocols
Submit a pull request

Code Style

Follow standard Java conventions
Add comprehensive JavaDoc comments
Include unit tests for new features
Ensure all existing tests pass

Testing Requirements

# Run all tests
mvn test

# Run with different transports
mvn test -Dtest.transport=stdio
mvn test -Dtest.transport=sse  
mvn test -Dtest.transport=http

📄 License

This project uses Spring Boot and other open-source libraries. Please refer to individual dependency licenses for more information.

💡 Support

For issues and questions:

Create an Issue

Bug reports: Provide detailed reproduction steps
Feature requests: Describe the use case and expected behavior
Questions: Check existing issues first

Debugging Checklist

✅ Review the troubleshooting section
✅ Check server logs for detailed error messages
✅ Verify SMTP configuration with a separate email client
✅ Test with the REST endpoint before using MCP integration
✅ Try different transport protocols to isolate issues
✅ Confirm Java and Maven versions meet requirements

Getting Help

Documentation: Check this README and inline code comments
Examples: See the related projects for integration examples
Community: Open a GitHub issue for community support
Enterprise: Consider professional support for production deployments

Made with ❤️ for the MCP ecosystem

This server bridges the gap between AI applications and email communication, enabling powerful automation workflows and seamless user notifications.

Añadir este servidor

Host a copy with our keys and logs.

Server facts

About Java MCP Server For SMTP Mailing

Tools

Questions

How do I install Java MCP Server For SMTP Mailing?

Does Java MCP Server For SMTP Mailing need an API key?

What transport does Java MCP Server For SMTP Mailing use?

When was Java MCP Server For SMTP Mailing last checked?

Documentation

SMTP MCP Server (Java SDK 0.11.0)

📋 Table of Contents

🚀 Features

Core Functionality

Advanced Features

📋 Prerequisites

🏗️ Architecture Overview

🛠️ Installation & Building

1. Clone the Repository

2. Configure Email Settings

3. Build the Project

⚙️ Configuration

Gmail App Password Setup

Alternative SMTP Providers

Microsoft Outlook/Hotmail

Yahoo Mail

Custom SMTP Server

📖 Usage

Finding Required Paths

Project Path

Java Executable Path

Java Home Path

1. STDIO Transport (Recommended for Claude Desktop)

Testing with MCP Inspector

Claude Desktop Integration

2. Server-Sent Events (SSE) Transport

Start SSE Server

Testing with MCP Inspector

Direct MCP Client Connection

3. Streamable HTTP Transport

Start HTTP Server

Testing with MCP Inspector

🧪 Testing

REST API Testing

Send Email

Health Check

Using Postman

MCP Tool Testing via Claude Desktop

📚 API Reference

MCP Tool: send-email

REST Endpoints

POST /api/test-email

GET /api/health

Transport Protocol Comparison

Server Endpoints (HTTP Transports)

🔗 Related Projects

1. MCP Client Dataset Creating Assistant

2. AI Agents Performance Testing MCP Server

3. AI Agents Performance Testing MCP Client

Integration Examples

With Dataset Creation Assistant

With Performance Testing

🐛 Troubleshooting

Common Issues

1. Authentication Failed

2. Connection Refused

3. Port Already in Use

4. MCP Inspector Connection Issues

5. Claude Desktop Integration Issues

Debug Mode

Testing Recommendations

📊 Performance & Monitoring

Performance Characteristics

Monitoring

Health Check Endpoint

Log Monitoring

Rate Limiting

🔧 Dependencies

🔒 Security Notes