Skip to content

You have the tools. Mailly brings the email.

Your AI client, backend, terminal, or existing email library. Choose the entry point that fits. The data and workspace stay connected.

Connect your inbox to your AI client.

Add the remote MCP endpoint to a client that supports Streamable HTTP and OAuth. Sign in to Mailly and choose permissions. Your host agent can read threads, prepare drafts, and send once you confirm.

Remote MCP
https://mcp.mailly.site/mcp

Connect with OAuth. Configuration syntax depends on your client. Keep API keys out of chats and public configurations.

Keep your application in the conversation.

Connect incoming messages and delivery outcomes to your business workflow with webhooks.

Set up webhooks
email.received

A new message arrives

Notify your service, then read full context using the message and thread references. Set a default endpoint or several per address, then send a test event to verify.

delivered / hard_bounced

A delivery outcome is available

Inspect delivery, bounce, complaint, unsubscribe, and click events in your application and the workspace.

Verify the HMAC-SHA256 signature and deduplicate by event ID. Failed deliveries retry; events may arrive more than once.

Give your next agent an actual inbox.

Start with an address. Connect incoming mail, replies, and follow-ups in one workflow.

Create an account