Get started

MailerSend for AI agents

MailerSend is a transactional email and SMS service developers use to send, track, and manage programmatic messages triggered by application events. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect MailerSendSee the 23 actions ↓
EmailAPI keyMCP + RESTmailersend.com
AUDIT LOG · MAILERSENDPOLICY: acme-support
09:41:07 · claude · u_8f2read
mailersend.get_users
Get users✓ allowed · 212ms
09:41:08 · claude · u_8f2read
mailersend.get_domain
Get Domain✓ allowed · 164ms
09:41:09 · claude · u_8f2write
mailersend.create_token
Create API Token✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
mailersend.delete_webhook
Delete Webhook✕ blocked · policy: deny
EVERY MAILERSEND CALL, ON THE RECORD
01 · USE CASES

What agents do in MailerSend.

01

Check sent message activity

Pull recent sent messages and their delivery status for a customer's transactional emails, read-only.

02

Check remaining API quota

Look up the account's sending quota before triggering a large batch of transactional emails.

03

Approve before deleting a domain

Require approval before deleting a sending domain, since it would stop outgoing mail from that domain.

02 · ACTIONS

23 MailerSend actions, graded by risk.

Every MailerSend action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

18

Look things up. Allowed by default.

  • mailersend.get_users
    Get users
  • mailersend.get_domain
    Get Domain
  • mailersend.get_tokens
    Get API Tokens
  • mailersend.get_domains
    Get sending domains
  • mailersend.get_messages
    Get sent messages
  • mailersend.get_webhooks
    List webhooks
  • mailersend.get_api_quota
    Get API Quota
  • mailersend.get_templates
    Get email templates
  • mailersend.get_identities
    List Sender Identities
  • mailersend.get_recipients
    Get email recipients
  • mailersend.get_smtp_users
    Get SMTP users
  • mailersend.get_sms_numbers
    Get SMS Numbers
  • mailersend.get_sms_activity
    Get SMS Activity
  • mailersend.get_sms_inbounds
    Get SMS Inbounds
  • mailersend.get_sms_messages
    List SMS Messages
  • mailersend.get_sms_recipients
    Get SMS recipients
+ 2 MORE

write

4

Create and change things. Allow, or ask the user first.

  • mailersend.create_token
    Create API Token
  • mailersend.create_domain
    Create Sending Domain
  • mailersend.create_webhook
    Create Webhook
  • mailersend.create_smtp_user
    Create SMTP User

destructive

1

Delete, cancel or archive. Ask first, or deny outright.

  • mailersend.delete_webhook
    Delete Webhook
03 · HOW IT WORKS

MailerSend in three steps.

  1. 01Your users connect MailerSendThey add their MailerSend api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create API Token” can wait for the user, and “delete Webhook” can be denied outright.
  3. 03Any agent can actYour agent calls MailerSend through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('mailersend', {
  read: 'allow',
  write: 'ask',        // create_token
  destructive: 'deny',  // delete_webhook
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How MailerSend connects.

Users add their MailerSend api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same MailerSend connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use MailerSend from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More email apps.

Gmail62 actionsOutlook306 actionsSendGrid364 actionsMixmax94 actionsElastic Email91 actionsResend66 actionsLettr60 actionsPostmark46 actions
ALL EMAIL APPS →
07 · FAQ

MailerSend and Arc0, answered.

Q01

Can I use MailerSend with Claude, ChatGPT or Cursor?

Yes. Connect MailerSend to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the MailerSend actions you allow.

Q02

How do users connect MailerSend?

Users add their MailerSend api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which MailerSend actions can my agent take?

23 in total: 18 read, 4 write and 1 destructive, such as “create API Token”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in MailerSend?

Yes. Actions like “delete Webhook” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call MailerSend too?

Yes. The same MailerSend connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug MailerSend into your agent.

Your users connect MailerSend once, under your brand. Your agent gets 23 actions behind your policies, with every call on the record.

Connect MailerSendBrowse all apps →

Free to build · MCP + REST · Audit log on every plan