mails.ai
All updates

Sign in from your AI client, a real inbox, and a CLI

Today's release adds sign-in for AI clients, a full inbox, a command line and the whole API in the SDKs and the MCP server. Four changes at the end are worth a look if your code reads webhooks or uses a key tied to one agent.

The mails.ai team

New

  • Connect by signing in. Claude, Claude Code, Cursor, Codex and VS Code connect to https://api.mails.ai/mcp by signing in to mails.ai: choose the workspace, press Allow, and there is no API key to paste.
  • A real inbox. Attachments with download links, the original email as it was sent, search across your mail, five folders (inbox, archive, spam, trash and sent) and coloured labels.
  • The mails command line. Send, read and manage mail from a terminal: npx @mailsai/cli.
  • The whole API in the SDKs and the MCP server. @mailsai/sdk and the Python mailsai 0.3.0 cover every call. @mailsai/mcp-server 0.3.0 has a tool for every endpoint except the event stream, the billing portal and the two unsubscribe links, named like mails_send; the old dotted names still work.
  • Agent skills. npx skills add mailsai/skills teaches Claude Code and other agents to send and receive through mails.ai.
  • Single sign-on with any OpenID Connect provider, on the Scale plan.
  • See and revoke connected apps from code. GET and DELETE /v1/oauth/grants list the apps connected to your workspace and revoke one, like Settings › Connected apps, and the CLI has mails connected-apps list and mails connected-apps revoke.
  • A drafts-only API key. The new draft scope writes drafts and never sends them, for an agent whose mail a person approves first.
  • Received mail shows its scan result. Each received message carries its injection score and whether it was quarantined.
  • Change plans yourself. On Billing, "Switch to Pro" or "Switch to Scale" opens Stripe's billing page.
  • A new dashboard, and a live demo on the home page.

Check these before you rely on the old behaviour

  • Keys tied to one agent now stay inside that agent. Another agent's message, thread, draft, attachment or original email answers 404, and lists and search hold only its own agent's mail. Webhooks and labels belong to the whole workspace, so such a key cannot change them (403).
  • Webhooks on * no longer receive thread.created, thread.updated or thread.deleted. Name those events on the endpoint to keep getting them. The new message.delayed also comes only to an endpoint that names it.
  • After you rotate a webhook signing secret, each delivery carries two v1 signatures for 24 hours. Accept the delivery when any v1 matches, not only the last one. The 0.3.0 SDKs do.
  • Received mail is authenticated from the original email. DKIM is verified, DMARC passes when a signature aligned with the sender's domain verifies, and spf_pass is null, because SPF can only be judged where the mail arrived. message.received.unauthenticated now fires only when a domain that asks for signed mail (a DMARC policy of quarantine or reject) sends without a valid signature.
  • A 429 says when the limit resets. The body carries resets_at and retry_after_seconds, and the Retry-After header comes only when the wait is 60 seconds or less. The 0.3.0 SDKs wait and retry then, and otherwise raise an error that carries the reset time.
  • An agent paused for its bounce or complaint rate stays paused until the rate recovers. Setting it active answers 403 agent_suspended.
  • A reply or forward on mail of an agent your key cannot read answers 404, without naming that agent.

— the mails.ai team

Subscribe