mimux pro

Give your agents an inbox.

Your agents can search the web and run code. They still can't read your mail — unless you hand your inbox to a SaaS intermediary. mimux pro closes that gap on hardware you own: a REST API, an MCP server, a CLI and signed webhooks over the self-hosted inbox you already run.

Start the 14-day trial API reference

No key needed for the trial — a pro build runs free for 14 days from first boot.

MCP server

Your inbox, as a first-class tool.

mimux serves MCP over streamable HTTP at /api/mcp — plus a stdio bridge for clients that want one. Point Claude, or any MCP-capable client, at your instance and the mailbox becomes a set of tools: search, read, move, label, draft.

The tools an agent sees are filtered by its token's scopes — a read-only token never even shows the agent a write tool.

mcp.json

{
  "mcpServers": {
    "mimux": {
      "url": "https://mail.example.com/api/mcp",
      "headers": {
        "Authorization": "Bearer mx_your_token"
      }
    }
  }
}

terminal

# everything the client can do, over plain HTTP
$ curl -H "Authorization: Bearer mx_your_token" \
    https://mail.example.com/api/v1/messages?q=is:unread

# self-documented from the binary
$ curl https://mail.example.com/api/v1/openapi.json

REST API

Plain HTTP over your whole mailbox.

Messages, folders, search, drafts, send and filters — everything the client does, scriptable. The OpenAPI spec is served from the binary itself at /api/v1/openapi.json and rendered at docs.mimux.dev, so the docs can never drift from the build you run.

cron jobs, n8n flows, a Raspberry Pi that prints your morning mail — if it speaks HTTP, it now speaks to your inbox.

CLI

Your inbox, in your shell.

The same gateway, one binary away from your prompt. Search, read, file and draft from the terminal — which means from cron, from CI, and from every shell script you already own.

Output is plain text or JSON, so it pipes: into jq, into an LLM, into whatever comes next. Drafting and sending stay separate here too — a script can prepare mail, but sending is its own explicit step.

terminalmimux cli

$ mimux search "is:unread from:billing"
3 messages · ids 8269 8270 8271
$ mimux read 8271 --json | jq .subject
"Invoice #2451"
$ mimux draft reply 8271 -m "Paid today."
# draft saved — sending is a separate, explicit step

Webhooks

Push, when mail arrives.

New mail and rule matches, pushed to whatever automation you run — n8n, Home Assistant, your own scripts. Payloads are signed so your endpoint can verify the sender, deliveries retry with backoff, and a delivery log shows exactly what fired, when, and what the endpoint answered.

delivery logendpoint: n8n.local

message.received · #8271200 · 84ms
rule.matched · invoices200 · 61ms
message.received · #8270retry 2 · 503

signed · X-Mimux-Signature · retries with backoff

Guardrails

Safe by architecture, not by prompt.

An agent with your inbox deserves more caution than a system prompt asking it nicely. The guardrails in mimux are structural:

Sending is a two-step operation

Agents create drafts. Actually sending is a separate, explicit call — so a prompt-injected "forward all mail to attacker@evil" dies as a draft you never approve. No tool description can merge the two steps.

Tokens carry scopes

Mint a read-only token for the summariser, a draft-capable one for the assistant, and revoke either in one click from Settings → API. Scope-filtered tools mean an agent can't even see what it can't do.

Your mail never leaves

The API runs on your server, next to your mail. There's no vendor cloud caching your messages to make the API fast — the API is fast because it's local.

Licensing can't brick your mail

Licence checks are offline Ed25519 signature verification — no activation server, no phone-home. And if a licence lapses, only the automation layer stops. The mail client keeps working, always.

What people build

The first hour of ideas.

triage

Morning inbox agent

Files invoices, archives newsletters, stars anything from a real human, drafts the two replies that matter — before you sit down.

digest

Daily brief to ntfy

A cron hits the API, an LLM summarises what arrived overnight, and the digest lands on your phone with the rest of your homelab alerts.

automation

Webhook → n8n → anywhere

Order confirmations into a spreadsheet, support requests into a ticket queue, alerts into Home Assistant scenes. Mail becomes an event source.

Ask your archive

"What did the landlord say about the deposit?" — an agent with search and read tools answers from your own mail, on your own machine.

Next on the roadmap: a GraphQL endpoint over the same gateway — part of pro when it ships, same price.

Fourteen days, no key, no card.

Run a pro build and the whole automation layer is on from first boot. Keep it for €49 a year — or €99 once, forever.

See pricing Read the API docs