litemx --agent-first
Give your agents an inbox.
CLI-first custom-domain email hosting for people and AI agents. Create real role inboxes, receive and send mail, then grant scoped MCP or API access without handing over the whole account.
Claude / Codex / customread · search · draft3 messages · 1 unreadmissing: email:sendsupport-agent · draft.created$pnpm dlx litemx@latest domains add project.devOne inbox. Two operators. Explicit permissions.
The same mailbox primitives work for you at the terminal and for an external agent over MCP. The agent gets only the tools and mailboxes named in its token.
litemx domains add
Bring the inbox. Keep your DNS.
LiteMX shows the records to add, verifies the domain, and creates the mailboxes and aliases you need. Your website, registrar, and DNS provider stay put.
pnpm dlx litemx@latest loginlitemx domains add project.dev✓ DNS checks ready · provider unchangedlitemx mailboxes create support@project.devlitemx aliases create hello@project.dev --to support@project.devlitemx messages list
Operate email from the terminal.
List messages, read threads, create drafts, and send replies without opening a webmail client. Outbound sending stays capped and audited so LiteMX does not become a bulk sender.
litemx messages list --mailbox support@project.dev3 messages · 1 unreadlitemx drafts create --thread thr_123 --body-file reply.txt✓ draft saved · ready for reviewlitemx drafts send draft_456sent · audit event recordedlitemx mcp connect
Let agents act inside a boundary.
External agents can search, read, draft, and send through MCP or the API. Each token is limited by mailbox and action, so you decide exactly what an agent can do.
litemx mcp connect --client claude✓ connected · 7 tools availablelitemx tokens create support-agent --mailbox support@project.devscopes: messages:read · messages:search · drafts:writelist_mailboxes · list_threads · read_messagesend_draft — requires email:sendA Google Workspace alternative for project inboxes.
Google Workspace and Proton Mail are great when every person needs a full mailbox UI. LiteMX is for projects that need support@, hello@, billing@, and admin@ across a lot of domains.
The product surface is intentionally smaller: domain setup, real mailboxes, aliases, receive/send, CLI, REST, MCP, scoped tokens, and audit logs. Less suite. More mailbox infrastructure.
| Capability | Google Workspace | Proton Mail | LiteMX |
|---|---|---|---|
| Billing model | Per user, per domain | Per user / mailbox | Flat — many domains |
| Official starting point | $7/user/mo | 1 custom domain on Mail Plus | $8/mo Starter |
| 20 custom domains | Depends on setup | Not a personal-plan fit | Included |
| Many domains, one account | No | Limited | Yes |
| Unlimited aliases | Capped | Capped | Yes |
| First-class CLI | No | No | Yes |
| Mailbox REST API | Admin only | No | Yes |
| Agent access | No | No | Yes |
| Designed for | Human teams | Private human inboxes | Project inboxes + agents |
Competitor notes are June 2026 snapshots from Google Workspace pricing and Proton Mail plans. Exact cost depends on seats, domains, aliases, and tier. LiteMX is not a full webmail or office-suite replacement.
No seats. No alias tax. Just mailbox limits.
Pay for domains, mailboxes, retention, and outbound volume. Aliases are included.
| Plan | Domains | Mailboxes | Sends / mo | Retention | Price |
|---|---|---|---|---|---|
| free | 1 | 1 | 500 | 30d | $0 |
| starter ← recommended | 20 | 50 | 3,000 | 60d | $8/mo |
| scale | 50 | 150 | 15,000 | 1y | $18/mo |
Questions, answered plainly.
LiteMX creates real mailboxes for your domains. You operate them from the CLI. External agents can use scoped MCP or API access when you want automation.
What is LiteMX?
LiteMX is CLI-first email hosting for people who run lots of domains. It lets you create real mailboxes like support@, hello@, billing@, and admin@ without buying another Google Workspace seat for every project.
Is LiteMX a Google Workspace alternative?
Yes, for project and role inboxes. Google Workspace is a full productivity suite priced around users and seats. LiteMX is the lighter alternative for custom-domain mailboxes you manage from the CLI, API, and MCP.
Why not just use Google Workspace or Proton Mail?
Use them when every person needs a full mailbox UI. Use LiteMX when every project needs support@ or hello@, and you want the terminal or an external agent to read, draft, and send under explicit permissions.
How much does custom-domain email cost with LiteMX?
LiteMX starts free for one domain, one mailbox, and capped low-volume sending. Paid plans are $8/month for Starter and $18/month for Scale, billed annually. Aliases are included on every plan.
Can I use LiteMX for newsletters or cold outbound?
No. LiteMX is for human-scale mailbox email, replies, support conversations, and operational messages. It is not a bulk sender, newsletter platform, marketing automation tool, or cold outbound product.
Who is LiteMX for?
LiteMX is for founders, indie hackers, agencies, and automation builders who keep creating new domains and need real inboxes for each project.
Does LiteMX replace Gmail?
Not for personal email. LiteMX replaces the habit of creating a new Google Workspace account just to get project inboxes. The first interface is the CLI, with REST API and MCP access for automation.
How do agents use LiteMX?
External agents connect through MCP or the REST API using LiteMX tokens. Tokens can be limited to one mailbox and specific actions, so an agent can read and draft without being allowed to send.
What email infrastructure does LiteMX use?
LiteMX is DNS-provider-agnostic for inbound mail. The initial production provider is AWS SES Email Receiving, with Cloudflare Workers, D1, Durable Objects, R2, Queues, and Cron Triggers as the application runtime and storage layer.
Start with one domain.
Request access, add one domain, create support@, receive a test message, and send a reply from the CLI. Then connect an agent when you are ready.