Mailtrap Email Sending MCP Server
Base URL: https://mailtrap.io
API Info
- API License: Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) — https://creativecommons.org/licenses/by-sa/4.0/
- Contact: Mailtrap Support (support@mailtrap.io) — https://docs.mailtrap.io
Install
Quick Start (recommended)
API_KEY=YOUR_API_KEY \
BEARER_TOKEN=YOUR_BEARER_TOKEN \
uvx mcparmory-mailtrap-email-sending
With pip
pip install mcparmory-mailtrap-email-sending
API_KEY=YOUR_API_KEY \
BEARER_TOKEN=YOUR_BEARER_TOKEN \
mcparmory-mailtrap-email-sending
MCP Client Configuration
Add to your MCP client config (e.g. Claude Desktop, Cursor, Codex):
{
"mcpServers": {
"mailtrap-email-sending": {
"command": "uvx",
"args": ["mcparmory-mailtrap-email-sending"],
"env": {
"API_KEY": "YOUR_API_KEY",
"BEARER_TOKEN": "YOUR_BEARER_TOKEN"
}
}
}
}
Credentials
Set the following environment variables (via MCP client env config, shell export, or .env file):
API_KEY— API Key Authentication (Api-Token)BEARER_TOKEN— Bearer token Do not commit credentials to version control.
Run Locally
First, configure your credentials in .env (see Credentials above).
pip install -r requirements.txt
python server.py
Connect MCP Client
Edit .mcp.json and replace <SERVER_DIR> with the absolute path to this directory, then add to your MCP client configuration.
Example (if server is at /home/user/mcp-servers/mailtrap-email-sending):
{
"mcpServers": {
"mailtrap-email-sending": {
"command": "python",
"args": ["/home/user/mcp-servers/mailtrap-email-sending/server.py"]
}
}
}
Docker
First, configure your credentials in .env (see Credentials above).
docker build -t mailtrap-email-sending .
docker run -p 8000:8000 --env-file .env mailtrap-email-sending
Before running, make sure ports 8000 are free.For Docker, use SSE transport in your MCP client config:
{
"mcpServers": {
"mailtrap-email-sending": {
"type": "sse",
"url": "http://localhost:8000/sse"
}
}
}
Files
.env- Credentials and server configuration.mcp.json- MCP client config templateDockerfile- Container buildLICENSE- MIT license for this generated coderequirements.txt- Python dependenciesREADME.md- This fileserver.py- MCP server entry point_auth.py- Authentication handlers_models.py- Request/response models_validators.py- Input validation
Note: Files starting with . are hidden by default on macOS/Linux. Use ls -a in terminal or enable "Show hidden files" in your file manager to see .env and .mcp.json.
Generated by MCP Blacksmith · Quickstart docs · Report a bug
Metadata
Release files for mcparmory-mailtrap-email-sending 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcparmory_mailtrap_email_sending-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / mcparmory_mailtrap_email_sending-1.0.0-py3-none-any.whl
| Download URL | mcparmory_mailtrap_email_sending-1.0.0-py3-none-any.whl |
|---|---|
| Size | 39.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c9a8b75350a7ab9e5e21a73e31712a72130505fefa4eb1c0ac13a876819b0467
|
|
BLAKE2b-256 checksum How to use checksums |
57d70d87646bc80c1ce22e7a484e968a83c83328e96f3bae94f18e75ce21e234
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for mcparmory-mailtrap-email-sending 1.0.0
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.