Zulip for AI agents
Zulip is team chat organized by topic threads, used by distributed teams that want the immediacy of chat with the structure of email threading. 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 Zulip.
Send a message to a channel
Post a message to a channel and topic thread.
Get another user's presence
Check whether a teammate is currently online, a read-only status check.
Confirm before deleting a topic
Check with the user before deleting a topic, since its messages go with it.
111 Zulip actions, graded by risk.
Every Zulip action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
43Look things up. Allowed by default.
- zulip.get_iconGet realm icon
- zulip.get_userGet user by email
- zulip.get_draftsGet drafts
- zulip.get_eventsGet Events
- zulip.get_invitesGet all invitations
- zulip.get_messageGet message
- zulip.get_streamsGet All Channels
- zulip.get_messagesGet Messages
- zulip.get_own_userGet own user
- zulip.get_remindersGet reminders
- zulip.get_stream_idGet Channel ID
- zulip.get_linkifiersGet linkifiers
- zulip.get_alert_wordsGet alert words
- zulip.get_attachmentsGet Attachments
- zulip.get_subscribersGet Channel Subscribers
- zulip.get_user_groupsGet user groups
write
49Create and change things. Allow, or ask the user first.
- zulip.update_userUpdate user by email
- zulip.add_reactionAdd Reaction
- zulip.send_messageSend Message
- zulip.add_linkifierAdd Linkifier
- zulip.create_draftsCreate Drafts
- zulip.update_statusUpdate Status
- zulip.update_streamUpdate Channel
- zulip.add_apns_tokenAdd APNs Device Token
- zulip.create_channelCreate Channel
- zulip.update_messageUpdate Message
- zulip.add_alert_wordsAdd Alert Words
- zulip.update_settingsUpdate Settings
- zulip.update_linkifierUpdate Linkifier
- zulip.update_user_topicUpdate User Topic
- zulip.add_default_streamAdd Default Stream
- zulip.create_invite_linkCreate reusable invitation link
destructive
19Delete, cancel or archive. Ask first, or deny outright.
- zulip.delete_draftDelete Draft
- zulip.delete_queueDelete Event Queue
- zulip.delete_topicDelete Topic
- zulip.archive_streamArchive Channel
- zulip.delete_messageDelete Message
- zulip.delete_reminderDelete Reminder
- zulip.remove_reactionRemove Reaction
- zulip.remove_fcm_tokenRemove FCM Token
- zulip.remove_linkifierRemove Linkifier
- zulip.remove_attachmentRemove Attachment
- zulip.remove_alert_wordsRemove Alert Words
- zulip.delete_saved_snippetDelete Saved Snippet
- zulip.remove_default_streamRemove Default Stream
- zulip.remove_code_playgroundRemove Code Playground
- zulip.remove_navigation_viewRemove Navigation View
- zulip.delete_scheduled_messageDelete Scheduled Message
Zulip in three steps.
- 01Your users connect ZulipThey add their Zulip username and password on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Drafts” can wait for the user, and “delete Draft” can be denied outright.
- 03Any agent can actYour agent calls Zulip through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('zulip', { read: 'allow', write: 'ask', // create_drafts destructive: 'deny', // delete_draft }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Zulip connects.
Users add their Zulip 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 Zulip 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 Zulip from any agent.
Zulip and Arc0, answered.
Can I use Zulip with Claude, ChatGPT or Cursor?
Yes. Connect Zulip 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 Zulip actions you allow.
How do users connect Zulip?
Users add their Zulip 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 Zulip actions can my agent take?
111 in total: 43 read, 49 write and 19 destructive, such as “create Drafts”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Zulip?
Yes. Actions like “delete Draft” 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 Zulip too?
Yes. The same Zulip connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Zulip into your agent.
Your users connect Zulip once, under your brand. Your agent gets 111 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan