BlueFox Email for AI agents

BlueFox Email is a transactional email service that developers use to send triggered emails and manage subscriber lists for their applications. 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.

EmailAPI keyMCP + RESTbluefox.email
AUDIT LOG · BLUEFOX EMAILPOLICY: acme-support
09:41:07 · claude · u_8f2read
bluefox_email.list_contacts
List Contacts✓ allowed · 212ms
09:41:08 · claude · u_8f2read
bluefox_email.get_contact
Get Contact✓ allowed · 164ms
09:41:09 · claude · u_8f2write
bluefox_email.create_contact
Create Contact✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
bluefox_email.delete_contact
Delete Contact✕ blocked · policy: deny
EVERY BLUEFOX EMAIL CALL, ON THE RECORD
01 · USE CASES

What agents do in BlueFox Email.

01

Send a transactional email

Send a transactional or triggered email to a contact after the user confirms the content and recipient.

02

Subscribe a contact to a list

Add a contact to a subscriber list so they start receiving the right campaign emails.

03

Require approval before deleting a contact

Flag a request to delete a contact record as needing confirmation since it removes their email history.

02 · ACTIONS

11 BlueFox Email actions, graded by risk.

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

read

4

Look things up. Allowed by default.

  • bluefox_email.get_contact
    Get Contact
  • bluefox_email.list_contacts
    List Contacts
  • bluefox_email.get_subscriber
    Get Subscriber
  • bluefox_email.list_subscribers
    List Subscribers

write

6

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

  • bluefox_email.create_contact
    Create Contact
  • bluefox_email.update_contact
    Update Contact
  • bluefox_email.update_subscriber
    Update Subscriber
  • bluefox_email.send_triggered_email
    Send Triggered Email
  • bluefox_email.send_transactional_email
    Send Transactional Email
  • bluefox_email.subscribe_to_list
    Subscribe To List

destructive

1

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

  • bluefox_email.delete_contact
    Delete Contact
03 · HOW IT WORKS

BlueFox Email in three steps.

  1. 01Your users connect BlueFox EmailThey add their BlueFox Email api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create Contact” can wait for the user, and “delete Contact” can be denied outright.
  3. 03Any agent can actYour agent calls BlueFox Email 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('bluefox_email', {
  read: 'allow',
  write: 'ask',        // create_contact
  destructive: 'deny',  // delete_contact
})

# 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 BlueFox Email connects.

Users add their BlueFox Email 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 BlueFox Email 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 BlueFox Email from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

BlueFox Email and Arc0, answered.

Q01

Can I use BlueFox Email with Claude, ChatGPT or Cursor?

Yes. Connect BlueFox Email 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 BlueFox Email actions you allow.

Q02

How do users connect BlueFox Email?

Users add their BlueFox Email 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 BlueFox Email actions can my agent take?

11 in total: 4 read, 6 write and 1 destructive, such as “create Contact”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in BlueFox Email?

Yes. Actions like “delete Contact” 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 BlueFox Email too?

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

Get started

Plug BlueFox Email into your agent.

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

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