Zulip MCP. Let your agent read history, send DMs, and manage presence.

Listen up—the zulip_ toolset gives your AI client direct control over your entire Zulip workspace. Instead of you manually copying threads or checking statuses, your agent can perform every chat action, from reading history to managing who's online. It’s about making the platform truly actionable for your automation.

Understanding Your Workspace Structure:

The server lets your agent map out your whole organization first. You can run zulip_get_streams to pull a comprehensive list of every public and private stream available across Zulip. If you need to know who's talking, zulip_get_users lists every account registered in the instance. To narrow down context, zulip_get_stream_topics reads out all distinct topics within any single specified stream.

You can also grab your own details using zulip_get_own_profile, which fetches the profile information for the bot or user that's running the agent.

Getting Set Up and Staying Current:

To make sure your agent is ready to talk, you'll use zulip_subscribe_to_stream to automatically subscribe the account to any specific stream. This ensures it can participate in future conversations and receive notifications. The agent keeps track of its status using zulip_set_presence, letting you update the connected account’s presence indicator—you can mark it as active, away, or whatever state you need.

Reading Messages: History Retrieval:

When your agent needs information, it pulls thread data directly. The zulip_get_messages tool retrieves message history from any specified stream or channel; this function is powerful because you can anchor the search to get only the newest messages, which is critical for keeping up with real-time conversations.

Writing and Interacting: Sending Messages:

For sending information out, zulip_send_message handles two scenarios. You can send a message into a designated public stream—a full channel conversation—or you can bypass the group chat entirely by sending it directly as a private direct message (DM) to one specific user.

Beyond just sending text, your agent can interact with existing content. zulip_add_reaction lets your client add any specified emoji reaction to an already posted message, letting you acknowledge or reference specific points in the thread without writing a whole new reply. This means it can read messages using zulip_get_messages, update who's online using zulip_set_presence, map out all available communication channels by listing streams with zulip_get_streams, and send targeted responses via zulip_send_message—all without you ever having to open the Zulip app yourself.