LiteMX
Private build
esc

Custom-domain email with CLI, API, and MCP access.

Email hosting for every domain.

Run support@, hello@, billing@, and admin@ across projects without buying another workspace. Give agents scoped mailbox access through CLI, API, and MCP.

Request private buildSee CLI flow
Founder setup4 tasks
Domain
project.dev
pending setup
Mailbox
support@project.dev
ready
Token
support-agent
read + draft
Retention
60 days
content only

CLI bring-up

litemx domains add project.dev
litemx mailboxes create support@project.dev
litemx tokens create support-agent \
  --mailbox support@project.dev \
  --scopes messages:read,messages:search,drafts:write

Many domains, one account.

Scoped access for tools and agents.

Retention and audit built in.

From domain to agent-readable inbox.

LiteMX becomes useful when a founder can add a domain, create role inboxes, issue a scoped token, and read real mail from the terminal.

  1. 01

    Add the domain record.

    LiteMX stores the domain, shows the Cloudflare DNS and Email Routing work, and tracks setup status until inbound mail can land.

    domains add
  2. 02

    Create role inboxes.

    Make support@, hello@, billing@, admin@, aliases, and catchalls without creating a paid workspace for every project.

    mailboxes create
  3. 03

    Issue scoped access.

    CLI, API, and MCP clients use LiteMX-owned tokens restricted by mailbox and scope. Sending is never implied by read access.

    tokens create
  4. 04

    Operate from terminal first.

    List mailboxes, read messages, search threads, draft replies, and send only when the token explicitly carries send scope.

    messages read

The dashboard stays small.

P0 needs enough UI to configure domains, mailboxes, aliases, tokens, audit, and setup docs around a working CLI and MCP backend.

Domains
Cloudflare-first setup instructions, verification status, inbound and outbound switches.
Mailboxes
Role inboxes with retention policy, inbound/outbound state, and mailbox-local storage.
Aliases
Cheap address routing into a target mailbox without independent storage.
MCP
Remote endpoint with read, search, draft, and send tools gated by scopes.
CLI
First-class commands for domains, mailboxes, aliases, messages, threads, drafts, and tokens.
Audit
Structured events for agent, API, and CLI reads and sends.

CLI first. MCP first. Webmail later.

The power interface is terminal-shaped: create infrastructure, inspect messages, issue scoped tokens, and connect agent clients without pretending LiteMX is a Gmail clone.

litemx auth login --token <token>
litemx mailboxes list
litemx messages list --mailbox support@example.com
litemx messages read <message_id>
litemx threads reply <thread_id> --body-file reply.txt
  • list_mailboxes
  • search_messages
  • read_thread
  • create_draft
  • send_draft requires send scope

Pricing shaped around domains, not seats.

Billing comes after mail and MCP work. These working tiers keep the promise honest: annual-first pricing, capped outbound sending, and retention as a cost control.

Free

$0 inbound-only

  • 1 domain
  • Unlimited aliases
  • Draft-only agent flow
  • 30-day retention
  • No meaningful outbound

Starter

$8/mo $79/year

  • 20 domains
  • 50 mailboxes
  • Unlimited aliases
  • 60-day retention
  • MCP + API + CLI
  • 1,000 outbound sends/month

Scale

$18/mo $179/year

  • 50 domains
  • 150 mailboxes
  • Unlimited aliases
  • 1-year retention
  • MCP + API + CLI
  • 5,000 outbound sends/month

Sharp boundaries keep the product legible.

Not a personal email replacement.

Not a helpdesk replacement.

Not a newsletter sender.

Not a cold outbound platform.

Not native AI summaries.

Not unlimited storage.

Start with one real domain.

Add a Cloudflare-managed domain, create support@, receive an email, read it from CLI, then let an MCP client draft a reply with scoped access.

Request private build