mcp-email-client

This MCP server provides a Python-based email client that you can manage via Claude Desktop or your editor. It supports listing, adding, updating, and deleting email configurations, sending emails using a selected configuration, and reading the latest unread emails. To use it, ensure uv is installed and the repository is set up, then run the MCP server through uv using the provided configuration. The server exposes tools for managing your email accounts (IMAP/SMTP settings) and for performing actions like sending messages or fetching the most recent unread messages. After starting, you can invoke actions by supplying the appropriate configuration identifiers and message details through the MCP interface.

Prerequisites:

• Python environment (recommended version compatible with the project)
• uv installed (the Universal Validator/Runner used by MCPs)
• Access to the repository hosting the MCP (clone from GitHub)

Install and run:

1. Clone the repository: git clone https://github.com/gamalan/mcp-email-client.git cd mcp-email-client

2. Install uv (if not already installed): Linux/macOS: curl -LsSf https://astral.sh/uv/install.sh | sh Windows: powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

3. Install dependencies and set up the MCP server: uv sync

4. Run the MCP server using the configuration (example shown in the config): Use your preferred MCP client (Claude Desktop, VSCode, etc.) with the following configuration: { "mcpServers": { "mcp_email_client": { "command": "uv", "args": [ "run", "--directory", "/path/to/repo", "mcp_email_client" ] } } }

Tips and considerations:

• Ensure your email configurations (IMAP/SMTP) are stored securely and referenced by name when sending or fetching emails.
• The MCP supports listing, adding, updating, and deleting email configurations; keep credentials encrypted or use environment-protected storage when possible.
• For first-time runs, you may need to initialize configuration storage and grant necessary permissions for network access to SMTP/IMAP servers.
• If you encounter issues with UV path resolution, verify that the --directory path points to the root of the mcp-email-client project and that the entry point matches the server script/module name used by your MCP client.
• When deploying in different environments (Windows/Linux/macOS), ensure file paths in the configuration are appropriate for that OS (escape backslashes on Windows).
• Check logs or verbose output from UV/MCP for troubleshooting connection errors to mail servers (authentication failures, blocked ports, or TLS requirements).
• The server focuses on a 5-unread-emails read limit; modify client calls if you plan to fetch more than the default.