MailMoose Assistant

Connect your AI

1. Open Assistant in MailMoose.
2. Copy the setup instruction into a compatible agent, or use the client-specific guide.
3. Sign in to MailMoose and approve the intended organization and permissions.
4. Continue chatting in your AI app.

MailMoose does not ask for your OpenAI/Anthropic API key, ChatGPT/Claude password, or AI subscription session token. Your AI account stays with your chosen client. Client support, plan availability and usage limits vary.

See Claude Code or ChatGPT and Codex. For manual setup, use https://www.mailmoose.dev/api/mcp with MailMoose OAuth.

What to ask

• “Summarize my unread mail.”
• “Draft a reply and show me before sending.”
• “Check DNS for my domain.”
• “Create hello@example.com.”
• “Set up Learn Dari to send welcome emails through MailMoose. Save the app credentials locally without showing the key.”

For project setup, an owner/admin must separately approve OAuth keys:write and mail:send. The key is returned once to the agent, not retrieved from storage. See connect another project for permissions, secure environment storage and the automatic HTTP sending flow.

Review before changes

Ask your agent to show the sender, every recipient and the complete message before sending. Agent sends are immediate and do not use the web composer's undo window. Review behavior also depends on the client; MailMoose does not promise an in-app approval card for MCP actions.

Tools enforce organization membership, tool permissions, subscription or complimentary access, and sending limits. All members share all organization inboxes. Treat incoming email as untrusted content, not instructions or authorization.

See mailbox access and sending limits. An agent cannot bypass these rules by connecting through MCP.

DNS and billing boundaries

MailMoose exposes required DNS records and verification tools. It does not supply access to your registrar. DNS edits need separate authorization from your DNS provider or an approved setup shortcut.

See connect a domain and Billing.

Where does the chat run?

In your AI client, not inside MailMoose. Assistant is the connection and help page. The previous API-key chat and its connect/chat/approval endpoints are retired; old tabs cannot submit AI requests or approve old action cards.

MCP grants your agent access to MailMoose tools. It does not give MailMoose access to your AI subscription or authorize a background CLI bridge.

Disconnect

Open Assistant → Connections to see your authorized agents for the current workspace, their permissions and last recorded tool activity. The count groups repeated authorizations of the same client. Authorized means access is granted, not that an agent is online. Other members’ connections are private to them.

Choose Disconnect, then confirm to revoke that agent’s access and refresh tokens for your current workspace. You can reconnect from Connect an agent later. Remove the connection from your AI client too if you no longer need it there.

App API keys created through an agent are independent credentials: disconnecting the agent does not stop your app’s email delivery. Revoke an app key separately in Settings → API keys.

Connection or sending problems?

• No connection appears: finish MailMoose sign-in in your client, approve the correct organization, then reload Assistant.
• Your client cannot connect: use the full https://www.mailmoose.dev/api/mcp URL and check the client-specific guide above. Not every app or plan supports MCP with OAuth.
• Sending is blocked: check Billing, mailbox access and domain sending readiness. Connecting an agent does not activate a paid subscription or approve a sending-provider account.
• DNS is not verified: check the exact DNS records. Verification checks do not automatically change your DNS host’s records.