Automation interfaces
There is no local HTTPS mail API, no bind address, and no
Settings → AI Agents → REST API toggle. Do not copy curl
examples against 127.0.0.1:7332. Those endpoints are not served
by the desktop app, the CLI, or primail-mcp.
primail-sync is experimental server code. It is not a
user-facing local mail REST product and does not prove a public
host.
What to use instead
Section titled “What to use instead”| Job | Interface |
|---|---|
| Interactive agent | stdio primail-mcp — install and connect |
| Scripts on this machine | primail CLI (primail --help lists groups; --json matches MCP envelopes) |
| Read / search / send verbs | Same Core names as MCP: account_list, mailbox_list, email_search, email_send, … |
Example CLI shapes (no live mail in this page; substitute your ids):
primail account list --jsonprimail --helpDo not run primail-mcp --help.
What this page used to describe
Section titled “What this page used to describe”Older copy documented bearer tokens, PRIMAIL_REST_TOKEN,
send_at over HTTP, 300/60/20 rate limits, and LAN bind. None of
those controls exist in the current Settings sheet or in the MCP
binary’s argv parser.
Scheduled send from an agent is the MCP email_send field
send_at (RFC 3339 UTC), which routes through Core’s local
scheduler on this device. That is not a REST call and not a
cloud relay.