mcp-email-server
IMAP and SMTP via MCP Server
- Github repository: https://github.com/ai-zerolab/mcp-email-server/
- Documentation https://ai-zerolab.github.io/mcp-email-server/
Installation
Manual Installation
We recommend using uv to manage your environment.
Try uvx mcp-email-server@latest ui to config, and use following configuration for mcp client:
{
"mcpServers": {
"zerolib-email": {
"command": "uvx",
"args": ["mcp-email-server@latest", "stdio"]
}
}
}
This package is available on PyPI, so you can install it using pip install mcp-email-server
After that, configure your email server using the ui: mcp-email-server ui
Then you can try it in Claude Desktop. If you want to intergrate it with other mcp client, run $which mcp-email-server for the path and configure it in your client like:
{
"mcpServers": {
"zerolib-email": {
"command": "{{ ENTRYPOINT }}",
"args": ["stdio"]
}
}
}
If docker is avaliable, you can try use docker image, but you may need to config it in your client using tools via MCP. The default config path is ~/.config/zerolib/mcp_email_server/config.toml
{
"mcpServers": {
"zerolib-email": {
"command": "docker",
"args": ["run", "-it", "ghcr.io/ai-zerolab/mcp-email-server:latest"]
}
}
}
Installing via Smithery
To install Email Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @ai-zerolab/mcp-email-server --client claude
Development
This project is managed using uv.
Try make install to install the virtual environment and install the pre-commit hooks.
Use uv run mcp-email-server for local development.
Releasing a new version
- Create an API Token on PyPI.
- Add the API Token to your projects secrets with the name
PYPI_TOKENby visiting this page. - Create a new release on Github.
- Create a new tag in the form
*.*.*.
For more details, see here.
Metadata
Release files for iflow-mcp_mcp-email-server 0.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iflow_mcp_mcp_email_server-0.0.5.tar.gz | 116.3 kB | Without provenance | Details for iflow_mcp_mcp_email_server-0.0.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_mcp_email_server-0.0.5-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_mcp_email_server-0.0.5-py3-none-any.whl |
Total release size: 135.1 kB
Release files / iflow_mcp_mcp_email_server-0.0.5.tar.gz
| Download URL | iflow_mcp_mcp_email_server-0.0.5.tar.gz |
|---|---|
| Size | 116.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ac0cdab593f25c3c35bba8d153406c7d8d66fdbec524c7b1a826439186841598
|
|
BLAKE2b-256 checksum How to use checksums |
ed85fe591630df29b48fa3006ef08d932386ab1a7d6bbe5883e2f4211d39f343
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.11
|
Release files / iflow_mcp_mcp_email_server-0.0.5-py3-none-any.whl
| Download URL | iflow_mcp_mcp_email_server-0.0.5-py3-none-any.whl |
|---|---|
| Size | 18.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fe044502f465ada9b90f0961498d991bf2e7f27a02fe6c2316a180043d28e9ae
|
|
BLAKE2b-256 checksum How to use checksums |
e269dbac108628bc6f2014b0b2baea09a56956021ba3d5e73b381f28d4d44814
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.11
|
Security for iflow-mcp_mcp-email-server 0.0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.