Bigmailer for AI agents
BigMailer is a white-label email marketing platform for agencies managing multiple brands, used to run separate contact lists, campaigns, and templates under different brand identities. 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.
What agents do in Bigmailer.
Add a contact to a brand's list
Create a contact under the right brand and list so it doesn't mix with another client's audience.
Launch a transactional campaign
Create a transactional campaign to send a one-off email tied to a specific customer action.
Delete a contact on request
Delete a contact only after the person asks to be removed, since suppressing them is usually safer than deleting.
57 Bigmailer actions, graded by risk.
Every Bigmailer action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
27Look things up. Allowed by default.
- bigmailer.get_listGet List
- bigmailer.get_userGet User
- bigmailer.get_brandGet Brand
- bigmailer.get_fieldGet Custom Field
- bigmailer.list_listsList Contact Lists
- bigmailer.list_usersList Users
- bigmailer.get_contactGet Contact
- bigmailer.get_segmentGet Segment
- bigmailer.list_fieldsList Fields
- bigmailer.get_templateGet Template
- bigmailer.list_sendersList Senders
- bigmailer.get_user_infoGet User Information
- bigmailer.list_contactsList Contacts
- bigmailer.list_segmentsList Segments
- bigmailer.list_templatesList Templates
- bigmailer.list_all_brandsList All Brands
write
23Create and change things. Allow, or ask the user first.
- bigmailer.create_listCreate List
- bigmailer.create_userCreate User
- bigmailer.update_listUpdate List
- bigmailer.update_userUpdate User
- bigmailer.create_brandCreate Brand
- bigmailer.create_fieldCreate Field
- bigmailer.update_brandUpdate Brand
- bigmailer.update_fieldUpdate Field
- bigmailer.create_contactCreate Contact
- bigmailer.create_segmentCreate Segment
- bigmailer.update_contactUpdate Contact
- bigmailer.update_segmentUpdate Segment
- bigmailer.create_templateCreate Template
- bigmailer.update_templateUpdate Template
- bigmailer.create_bulk_campaignCreate Bulk Campaign
- bigmailer.create_contact_batchCreate Contact Batch
destructive
7Delete, cancel or archive. Ask first, or deny outright.
- bigmailer.delete_listDelete List
- bigmailer.delete_userDelete User
- bigmailer.delete_fieldDelete Custom Field
- bigmailer.delete_contactDelete Contact
- bigmailer.delete_segmentDelete Segment
- bigmailer.delete_templateDelete Template
- bigmailer.delete_brand_propertyDelete Brand Property
Bigmailer in three steps.
- 01Your users connect BigmailerThey add their Bigmailer api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create List” can wait for the user, and “delete List” can be denied outright.
- 03Any agent can actYour agent calls Bigmailer through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('bigmailer', { read: 'allow', write: 'ask', // create_list destructive: 'deny', // delete_list }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Bigmailer connects.
Users add their Bigmailer 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 Bigmailer 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
Use Bigmailer from any agent.
Bigmailer and Arc0, answered.
Can I use Bigmailer with Claude, ChatGPT or Cursor?
Yes. Connect Bigmailer 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 Bigmailer actions you allow.
How do users connect Bigmailer?
Users add their Bigmailer 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.
Which Bigmailer actions can my agent take?
57 in total: 27 read, 23 write and 7 destructive, such as “create List”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Bigmailer?
Yes. Actions like “delete List” 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.
Can my own backend call Bigmailer too?
Yes. The same Bigmailer connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Bigmailer into your agent.
Your users connect Bigmailer once, under your brand. Your agent gets 57 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan