Zulip MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZULIP_URL | Yes | Zulip server URL, e.g. https://zulip.example.com | |
| ZULIP_EMAIL | Yes | The bot's email | |
| ZULIP_API_KEY | Yes | The bot's API key | |
| ZULIP_INSECURE_TLS | No | Set to 1 to accept a self-signed certificate (self-hosted / LAN Zulip) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| zulip_list_channelsC | List available channels (streams) in the Zulip organization |
| zulip_post_messageC | Post a new message to a Zulip channel (stream) |
| zulip_send_direct_messageC | Send a direct message to one or more users |
| zulip_add_reactionC | Add an emoji reaction to a message |
| zulip_get_channel_historyC | Get recent messages from a channel (stream) and topic |
| zulip_get_topicsB | Get topics in a channel (stream) |
| zulip_subscribe_to_channelB | Subscribe the bot to a channel (stream) |
| zulip_get_usersB | Get list of users in the Zulip organization |
| zulip_get_my_mentionsA | Get messages that @-mention this bot or are direct messages to it, across all channels. Pass since_message_id (the highest id you've already handled) to get only newer ones. Returns plain-text messages with id, channel, topic and sender, oldest first. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools target a clearly distinct resource+action: channel listing, channel posting, DM sending, reactions, topics, subscriptions, and users are all separable. The only mild overlap is between zulip_get_channel_history and zulip_get_my_mentions, which both return messages but with different scopes (single channel/topic vs. cross-channel mentions/DMs), and descriptions make that distinction clear.
All nine tools follow a uniform zulip_<verb>_<noun> snake_case pattern (zulip_list_channels, zulip_post_message, zulip_get_topics, etc.). Verb choices vary (post/send/add/list/get) but each verb fits its object naturally rather than reflecting inconsistency.
Nine tools is well within the ideal 3-15 range for a chat-platform integration and each one maps to a distinct Zulip primitive. No tool feels redundant or like padding.
Core read/write flows are covered (list channels, post to channel, send DM, topics, history, mentions, users), but the message lifecycle is incomplete: there is no edit/update message, delete message, or remove-reaction operation, and no way to fetch direct-message history with a specific user. Agents wanting to correct or clean up messages will hit dead ends.