Skip to content

Mail, agents, and automation. One connected workflow.

Start with a programmable inbox. Receive context, prepare replies, and connect contacts and events to follow-up messages. The workspace keeps each step visible to you.

One address. Both directions.

Create a dedicated inbox for each job. Start with @mailly.site or connect your brand domain so notifications and replies return to the same address.

Create your first inbox
support@your-domain.com

Complete conversations

Messages are threaded by reply references. Replies and follow-ups remain in the original conversation.

Message bodies & attachments

Read HTML and plain text, retrieve attachments, and strip quoted history when processing a message.

Incoming events

Set a workspace inbox webhook or a separate endpoint for each address.

Unified sent mail

Inspect mail from the web, API, CLI, SMTP, and campaigns in one sent-mail view.

Bring your own agent. Or let Mailly host it.

Email is independent of your model and orchestration. Choose how your agent works and keep clear control over sending.

MCP / API / CLI

Your own agent

Connect Mailly in a remote MCP client, or use the API, CLI, and webhooks with your existing application.

  • Your host agent analyzes mail and prepares drafts
  • Separate MCP read, draft, and send permissions
  • Your review UI or application controls sending
See integrations
Mailly Agent

A Mailly-hosted agent

Create an agent in the workspace, connect an inbox, and add instructions and skills. Incoming mail starts analysis; you can continue the discussion in the thread.

  • Thread summaries, replies, and follow-up drafts
  • Skills and memory managed by you
  • Drafts are sent only after your approval
Set up a hosted agent

Turn a single send into an ongoing conversation.

Define email resources with the CLI and API, then inspect and control them in the workspace. Notifications, outreach, and lifecycle mail share templates, contacts, and delivery data.

Read the automation guide
Example · Product onboarding
  1. event
    setup.completed

    Your application reports setup completion

  2. template
    getting-started

    Use a published template and contact variables

  3. wait
    Wait 2 days

    Continue according to your Workflow definition

  4. delivery
    Inspect the delivery result

    Review the run and mail for each contact

Templates

Versioned content, variables, localized templates, previews, and test sends.

Contacts & audiences

Sync attributes, manage subscription preferences, and prepare static lists or dynamic segments.

Campaign

Freeze content and audience, then track progress and per-recipient results.

Workflow

Define event triggers, sends, and wait steps. Inspect, pause, and resume runs.

Clear permissions. Clear outcomes.

Automation does not mean handing over every permission. Reading, drafting, approval, and delivery remain inspectable steps.

OAuth & account isolation

MCP exposes tools within the granted scopes. Reads and writes check workspace ownership. Keep API keys in trusted clients or on your server.

Approve the current draft

Draft approval checks the reviewed text and revision. Reply approvals use stable idempotency keys to avoid a second delivery on retries.

Verify event sources

Inbox and delivery webhooks use HMAC-SHA256 signatures. Failed deliveries retry; your receiver should verify signatures and deduplicate event IDs.

Delivery is a separate state

Accepted requests, queue progress, and delivery are separate states. Inspect delivery, bounce, complaint, unsubscribe, and click events.

Feature availability

Hosted agents draft and do not approve their own sends. Remote MCP is available with OAuth in supported clients; see pricing for plans and usage billing.

View pricing

Give your next agent an actual inbox.

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

Create an account