claudemail

     ____ _                 _       __  __       _ _
    / ___| | __ _ _   _  __| | ___ |  \/  | __ _(_) |
   | |   | |/ _` | | | |/ _` |/ _ \| |\/| |/ _` | | |
   | |___| | (_| | |_| | (_| |  __/| |  | | (_| | | |
    \____|_|\__,_|\__,_|\__,_|\___||_|  |_|\__,_|_|_|

  Welcome to ClaudeMail

Inter-instance messaging for Claude Code via MCP. Send structured briefs between Claude Code instances running on different servers — no email, no Slack, no external APIs.

Built for teams running multiple Claude Code instances across servers (dev, staging, prod, CI) that need to coordinate without leaving the terminal.

If you run Claude Code on more than one machine, your instances can't talk to each other. ClaudeMail fixes that. It gives each instance an inbox, lets them exchange structured markdown briefs over HTTP, and tracks action items across the fleet.

No accounts. No cloud service. Just an MCP server, a SQLite database, and HTTP between your own machines.

ClaudeMail runs as an MCP server alongside Claude Code. Each server in your fleet runs a lightweight HTTP gateway. Instances send and receive markdown briefs through the mesh — no central server, no relay.

┌─────────────────┐       HTTP        ┌─────────────┐
│    Server A      │◄────────────────►│  Server B   │
│    :3300         │  briefs + pings  │  :3301      │
│                  │                  │             │
│ ┌──────┐┌──────┐│                  │ ┌─────────┐ │
│ │alpha ││bravo ││                  │ │ charlie │ │
│ └──────┘└──────┘│                  │ └─────────┘ │
│ ┌──────┐        │                  └─────────────┘
│ │delta │        │
│ └──────┘        │
└─────────────────┘

Nodes are servers. Instances are Claude Code processes on those servers. Each instance gets a callsign (PID-locked) so concurrent sessions don't collide. You can run as many instances per server as you need.