Unisender for AI agents
UniSender runs email and SMS marketing campaigns, used by small businesses managing subscriber lists and sending newsletters or promotions. 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 Unisender.
Get a campaign's status
Check whether a campaign has sent and how it performed, a read-only lookup.
Subscribe a contact to a list
Add a contact to a mailing list ahead of a campaign.
Confirm before deleting a list
Check with the user before deleting a subscriber list, since its contacts and history go with it.
33 Unisender actions, graded by risk.
Every Unisender action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
15Look things up. Allowed by default.
- unisender.get_tagsGet Tags
- unisender.get_listsGet Lists
- unisender.get_fieldsGet Fields
- unisender.get_contactGet Contact
- unisender.get_messagesGet Messages
- unisender.get_templateGet Template
- unisender.get_campaignsGet Campaigns
- unisender.get_templatesGet Templates
- unisender.list_messagesList Messages
- unisender.list_templatesList Templates
- unisender.get_campaign_statusGet Campaign Status
- unisender.get_sender_domain_listGet Sender Domain List
- unisender.get_contact_field_valuesGet Contact Field Values
- unisender.check_emailCheck Email Status
- unisender.export_contactsExport Contacts
write
12Create and change things. Allow, or ask the user first.
- unisender.create_listCreate List
- unisender.update_listUpdate List
- unisender.create_fieldCreate Field
- unisender.update_fieldUpdate Field
- unisender.create_email_templateCreate Email Template
- unisender.update_email_templateUpdate Email Template
- unisender.create_subscriber_noteCreate Subscriber Note
- unisender.update_subscriber_noteUpdate Subscriber Note
- unisender.excludeExclude Contact from Lists
- unisender.subscribeSubscribe Contact to Lists
- unisender.import_contactsImport Contacts (Bulk)
- unisender.is_contact_in_listsCheck if Contact is in Lists
destructive
6Delete, cancel or archive. Ask first, or deny outright.
- unisender.delete_tagDelete Tag
- unisender.delete_listDelete List
- unisender.delete_fieldDelete Field
- unisender.delete_templateDelete Template
- unisender.delete_subscriber_noteDelete Subscriber Note
- unisender.unsubscribeUnsubscribe Contact
Unisender in three steps.
- 01Your users connect UnisenderThey add their Unisender 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 Tag” can be denied outright.
- 03Any agent can actYour agent calls Unisender through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('unisender', { read: 'allow', write: 'ask', // create_list destructive: 'deny', // delete_tag }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Unisender connects.
Users add their Unisender 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 Unisender 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 Unisender from any agent.
Unisender and Arc0, answered.
Can I use Unisender with Claude, ChatGPT or Cursor?
Yes. Connect Unisender 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 Unisender actions you allow.
How do users connect Unisender?
Users add their Unisender 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 Unisender actions can my agent take?
33 in total: 15 read, 12 write and 6 destructive, such as “create List”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Unisender?
Yes. Actions like “delete Tag” 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 Unisender too?
Yes. The same Unisender connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Unisender into your agent.
Your users connect Unisender once, under your brand. Your agent gets 33 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan