Engage Platform for AI agents
Engage Platform provides customer data, list, and event APIs for building transactional and lifecycle messaging workflows, used by product and growth teams triggering messages off user behavior. 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 Platform.
Upsert a user's profile
Upsert a user record with updated attributes after they change their preferences.
Set a list subscription
Set a user's subscription status on a list once they confirm they want updates.
Confirm before archiving a list
Require approval before archiving a list, since it stops every message scheduled to send to it.
18 Engage Platform actions, graded by risk.
Every Engage Platform action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
6Look things up. Allowed by default.
- engage_platform.get_listGet List
- engage_platform.get_userGet User
- engage_platform.list_listsList Lists
- engage_platform.list_usersList Users
- engage_platform.list_account_membersList Account Members
- engage_platform.track_user_eventTrack User Event
write
8Create and change things. Allow, or ask the user first.
- engage_platform.create_listCreate List
- engage_platform.create_userCreate User
- engage_platform.update_listUpdate List
- engage_platform.add_user_to_listsAdd User to Lists
- engage_platform.add_user_to_accountsAdd User to Accounts
- engage_platform.upsert_userUpsert User
- engage_platform.set_list_subscriptionSet List Subscription
- engage_platform.set_account_member_roleSet Account Member Role
destructive
4Delete, cancel or archive. Ask first, or deny outright.
- engage_platform.archive_listArchive List
- engage_platform.delete_user_attributeDelete User Attribute
- engage_platform.remove_list_subscriberRemove List Subscriber
- engage_platform.remove_user_from_accountRemove User From Account
Engage Platform in three steps.
- 01Your users connect Engage PlatformThey add their Engage Platform 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 User Attribute” can be denied outright.
- 03Any agent can actYour agent calls Engage Platform 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_platform', { read: 'allow', write: 'ask', // create_list destructive: 'deny', // delete_user_attribute }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Engage Platform connects.
Users add their Engage Platform 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 Engage Platform 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 Engage Platform from any agent.
Engage Platform and Arc0, answered.
Can I use Engage Platform with Claude, ChatGPT or Cursor?
Yes. Connect Engage Platform 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 Platform actions you allow.
How do users connect Engage Platform?
Users add their Engage Platform 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 Engage Platform actions can my agent take?
18 in total: 6 read, 8 write and 4 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 Platform?
Yes. Actions like “delete User Attribute” 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 Platform too?
Yes. The same Engage Platform connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Engage Platform into your agent.
Your users connect Engage Platform once, under your brand. Your agent gets 18 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan