localSMTP-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@localSMTP-mcp show me the latest 5 emails"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
localSMTP
Local dummy SMTP server for development. It accepts messages and writes the
original bytes to .eml files.
SMTP server
uv run localsmtp --host 127.0.0.1 --port 25 --out ./mailThe legacy entry point also works:
uv run python .\main.py --host 127.0.0.1 --port 25 --out ./mailRelated MCP server: mcp-imap
MCP server
The MCP entry point starts both the MCP stdio server and an SMTP listener. This lets coding agents start the mail catcher only when they need it.
uv run localsmtp-mcp --smtp-host 127.0.0.1 --smtp-port 25By default, the MCP server stores received mail in a temporary directory. Pass
--out when you want to keep messages in a specific location.
After publishing the package, use it from an MCP client with uvx:
{
"mcpServers": {
"localsmtp": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/fclef819/localSMTP-mcp.git",
"localsmtp-mcp",
"--smtp-host",
"127.0.0.1",
"--smtp-port",
"25"
]
}
}
}MCP tools
list_messages(limit = 50, newest_first = true)get_message(id, include_raw = false)clear_messages()get_server_status()
Available Tools
4 toolsclear_messagesA
Delete all received email messages from the output directory.
Inputs: no named parameters. Returns: object
get_messageB
Get a received email message by id.
Inputs: id (required), include_raw. Returns: object
get_server_statusA
Get SMTP listener and message store status.
Inputs: no named parameters. Returns: object
list_messagesC
List received email messages.
Inputs: limit, newest_first. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a distinct purpose: clearing all messages, retrieving a specific message, checking server status, and listing messages. No overlap in functionality.
All tools follow a consistent verb_noun pattern (e.g., clear_messages, get_message), making it predictable for agents.
With only 4 tools, the set is well-scoped for a local SMTP server, covering essential operations without unnecessary bloat.
The set covers core operations (list, get, clear, status) but lacks individual message deletion or filtering, which could be useful but not critical.
Related MCP Connectors
MCP server for MailTempo's public free temporary email inboxes.
Hosted MCP server for custom-domain email: send, receive and wait for mail on your domain.
Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.
Related MCP Servers
AlicenseDqualityBmaintenanceAn MCP server implementation that allows sending emails over MailPace's fast transactional email API.186 npm1MIT- FlicenseNot gradedqualityDmaintenanceA minimal MCP server for reading and sending emails via IMAP/SMTP, supporting multiple accounts in a single instance with zero external dependencies.1-
- AlicenseAqualityCmaintenanceMCP server for the Guerrilla Mail temporary/disposable email API. Spin up throwaway inboxes, poll for mail, and read messages from any MCP client.614 npm1MIT
- AlicenseNot gradedqualityCmaintenanceExposes any IMAP mailbox and SMTP relay as MCP tools, enabling email management (read, search, send, delete) through MCP-compatible agents.1MIT