Engage for AI agents
Engage sends personalized customer messaging across email, push, in-app notifications, and SMS to turn users into repeat customers, used by growth and lifecycle marketing teams. 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 Engage.
Subscribe a user to a list
Subscribe a new user to a messaging list once they opt in during onboarding.
Track a user event
Track a user event so a triggered message fires the next time they complete an action.
Confirm before deleting a user
Require approval before deleting a user record, since it removes their full messaging history.
22 Engage actions, graded by risk.
Every Engage action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
7Look things up. Allowed by default.
- engage.get_listGet List
- engage.get_userGet User By ID
- engage.list_listsList Lists
- engage.list_usersList Users
- engage.get_account_membersGet Account Members
- engage.track_user_eventTrack User Event
- engage.convert_user_typeConvert User Type
write
9Create and change things. Allow, or ask the user first.
- engage.create_listCreate List
- engage.create_userCreate User
- engage.update_userUpdate User
- engage.add_user_to_listsAdd User to Lists
- engage.send_batch_requestBatch Request
- engage.update_account_roleUpdate Account Role
- engage.add_customer_to_accountsAdd Customer to Accounts
- engage.update_subscriber_statusUpdate Subscriber Status
- engage.subscribe_user_to_listSubscribe User to List
destructive
6Delete, cancel or archive. Ask first, or deny outright.
- engage.delete_userDelete User
- engage.archive_listArchive List
- engage.archive_userArchive User
- engage.delete_subscriber_from_listDelete Subscriber From List
- engage.remove_customer_from_accountRemove Customer from Account
- engage.merge_usersMerge Users
Engage in three steps.
- 01Your users connect EngageThey add their Engage username and password 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 User” can be denied outright.
- 03Any agent can actYour agent calls Engage through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('engage', { read: 'allow', write: 'ask', // create_list destructive: 'deny', // delete_user }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Engage connects.
Users add their Engage username and password 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 Engage 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
- Username and password
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Engage from any agent.
Engage and Arc0, answered.
Can I use Engage with Claude, ChatGPT or Cursor?
Yes. Connect Engage 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 Engage actions you allow.
How do users connect Engage?
Users add their Engage username and password 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 Engage actions can my agent take?
22 in total: 7 read, 9 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 Engage?
Yes. Actions like “delete User” 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 Engage too?
Yes. The same Engage connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Engage into your agent.
Your users connect Engage once, under your brand. Your agent gets 22 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan