Discord

Community opens at launch.

Discord server opens at Phase 1 launch (Q3 2026). Holding it back deliberately so the first conversations are with developers actually shipping on the platform.

Where to reach us now

Two asynchronous channels until Discord opens. (GitHub goes public with the SDK + MCP server at Phase 1 launch.)

X / Twitter

Build updates, deliverability commentary, agent-mail discussion. DMs open for closed-beta inquiries.

Email

support@mails.ai for closed-beta access requests, partnership conversations, support questions.

What the Discord will look like

Eight channels at launch. Topic-scoped, not general-chat-soup.

#announcements

Releases, Phase rollouts, postmortems

#getting-started

Setup help, MCP wiring, SDK usage, first-send debugging

#api-feedback

Surface gaps, missing endpoints, ergonomic complaints

#agents-in-the-wild

Show + tell what you built on the platform

#deliverability

Inbox-placement issues, DKIM/SPF/DMARC questions, postmaster talk

#routing

Routing decisions, classifier behavior, pool questions

#mcp

MCP-server-specific topics — runtimes, custom tools, extension SDK (Phase 2)

#feature-requests

What we should build that we haven't

Subscribe to /changelog for the Discord launch invite.

Closed beta

Built for agents.
Self-serve at every volume.

Public API opens Q3 2026. Drop ~6 lines into your agent and ship.

npmpnpmbunpip
$ npm install @mailsai/sdk
Packages publish with cohort 1 · Q3 2026
Reserve your seatRead the docs