Integration

Zulip integration

Open-source team chat platform API. Send messages, manage streams, and handle user interactions. Thread-based conversations for organized communication. Essential for team messaging, chat automation, and collaboration.

Connect Zulip How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Zulip.Built from the 11 Zulip tools below, on the connection you add once.

Common Zulip use cases

feedback
chat history
profile view
user profile
notifications
user directory
channel creation
stream discovery
topic navigation
content moderation

What you can do with Zulip

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Message, 4 operations

delete_messageDelete messageDELETEDeletes a Zulip message.
get_messagesGet messagesGETRetrieves messages from Zulip streams or conversations.
send_messageSend messagePOSTSends a message to a Zulip stream or user.
update_messageUpdate messagePATCHEdits an existing Zulip message.

User, 3 operations

get_own_userGet own userGETRetrieves the authenticated user's profile.
get_userGet userGETRetrieves detailed information about a Zulip user.
list_usersList usersGETLists all users in the Zulip organization.

Stream, 2 operations

create_streamCreate streamPOSTCreates a new stream (channel) in Zulip.
list_streamsList streamsGETLists all streams in Zulip organization.

Reaction, 1 operation

add_reactionAdd reactionPOSTAdds an emoji reaction to a message.

Topic, 1 operation

get_stream_topicsGet stream topicsGETLists all topics in a Zulip stream.

Zulip API rate limits

200 requests per minute

Rate limits vary by endpoint

These are the limits Zulip documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Zulip documentation for current values.

Use Zulip from Claude Code, Cursor or Codex

Connect Zulip in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Zulip operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Zulip

Create your workspace
Sign up free. Nothing to install.
Connect Zulip once
Add your Zulip connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.