Browse
→ Communication
→ tmail MCP
tmail MCP
Gives agents private email through Stalwart and a Dockerized MCP bridge on a Tailscale network. Requires Docker Compose, an existing tailnet and explicitly created agent mailboxes. The bridge uses local stdio with mailbox credentials in protected files. Sending and replying are enabled, so require human approval before mail leaves an agent. HTTPS certificate issuance exposes the hostname in transparency logs. Public repository created November 6, 2026 (UTC).
MCP unverified
Integration
| Transport | stdio |
| Auth | none |
| Endpoint | docker compose --env-file /path/to/tmail/.clients/<client>/client.env -f /path/to/tmail/compose.client.yaml run --rm -T --no-deps mail |
| Install | Review the server and client Compose files, configure an owned tailnet and mailbox, keep credentials in protected client files, start the dedicated client gateway and register the documented Docker stdio mail command; require approval for sends |
Use Cases
| 01 | Read an approved agent mailbox |
| 02 | Prepare an email reply for review |
Tags
email tailscale docker private-network
Machine-readable: /api/servers.json
· JSON-LD schema embedded in <head>