Ably for AI agents
Ably is a real-time messaging infrastructure platform for building chat, live updates and data sync into applications. Developers use it to publish and subscribe to channels at scale. 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 Ably.
Check channel presence
See which clients are currently connected to a channel before deciding whether to publish an update.
Publish a message to a channel
Send a message onto a specific channel so every subscribed client receives it in real time.
Send a push notification
Push a notification to registered devices, a write action worth confirming before it reaches end users.
25 Ably actions, graded by risk.
Every Ably action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
12Look things up. Allowed by default.
- ably.get_statsGet Application Stats
- ably.list_channelsList Channels
- ably.get_push_deviceGet Push Device Registration
- ably.get_service_timeGet Ably Service Time
- ably.list_push_channelsList Push Channels
- ably.get_channel_detailsGet Channel Details
- ably.get_channel_historyGet Channel History
- ably.get_channel_presenceGet Channel Presence
- ably.get_message_versionsGet Message Versions
- ably.get_presence_historyGet Channel Presence History
- ably.list_registered_push_devicesList Registered Push Devices
- ably.list_push_channel_subscriptionsList Push Channel Subscriptions
write
12Create and change things. Allow, or ask the user first.
- ably.update_push_deviceUpdate Push Device Registration
- ably.batch_presenceQuery Batch Presence
- ably.register_push_deviceRegister Push Device
- ably.request_access_tokenRequest Access Token
- ably.batch_presence_historyQuery Batch Presence History
- ably.publish_batch_messagesBatch Publish Messages
- ably.unregister_push_deviceUnregister Push Device
- ably.publish_push_notificationPublish Push Notification
- ably.publish_message_to_channelPublish Message to Channel
- ably.unregister_all_push_devicesUnregister All Push Devices
- ably.patch_push_device_registrationPatch Push Device Registration
- ably.publish_push_notifications_batchBatch Publish Push Notifications
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- ably.delete_channel_subscriptionDelete Channel Subscription
Ably in three steps.
- 01Your users connect AblyThey add their Ably api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “update Push Device Registration” can wait for the user, and “delete Channel Subscription” can be denied outright.
- 03Any agent can actYour agent calls Ably through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('ably', { read: 'allow', write: 'ask', // update_push_device destructive: 'deny', // delete_channel_subscription }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Ably connects.
Users add their Ably 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 Ably 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 Ably from any agent.
Ably and Arc0, answered.
Can I use Ably with Claude, ChatGPT or Cursor?
Yes. Connect Ably 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 Ably actions you allow.
How do users connect Ably?
Users add their Ably 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 Ably actions can my agent take?
25 in total: 12 read, 12 write and 1 destructive, such as “update Push Device Registration”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Ably?
Yes. Actions like “delete Channel Subscription” 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 Ably too?
Yes. The same Ably connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Ably into your agent.
Your users connect Ably once, under your brand. Your agent gets 25 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan