LiteMX
Get access

Documentation

LiteMX Docs

Start with one command: create a custom-domain address and connect it to an inbox you already use.

Quickstart

  1. Install the CLI and configure your LiteMX token.
  2. Create the custom-domain address and connect a forwarding destination.
  3. Add the returned DNS records at your current DNS provider and verify the domain.
  4. Reply from your existing inbox; issue scoped tokens only when automation needs access.
npm install -g litemx
litemx login --token <token>
litemx addresses create support@example.com --forward-to owner@example.net
litemx domains verify example.com --timeout 120 --interval 5

The address and forwarding commands require litemx@0.1.1 or newer. During the private build, only exact founder destinations on the server allowlist can complete verification. Other destinations remain pending until one-time challenge delivery ships. See the existing-inbox guide for current availability and limitations.

Reference

Existing inboxForward incoming mail to a verified inbox and reply securely from your custom-domain address.CLICreate an address, connect a forwarding destination, inspect delivery, and use JSON output.Domain setupAdd MX, TXT, CNAME, DKIM, SPF, DMARC, and provider verification records at your existing DNS host.MCPConnect agent clients through scoped tokens and the LiteMX MCP endpoint.SecurityScoped tokens, audit logging, retention, outbound controls, and send limits.APIREST endpoint map, authentication model, OpenAPI location, and scoped-token behavior.Sending policyAllowed sending, abuse controls, plan caps, and sender responsibilities.

How Domain Setup Works

LiteMX does not require moving nameservers. The CLI prints the mail and verification records to add at your existing DNS provider, then verifies receive and send readiness separately.