Zulip MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZULIP_URL | Yes | Your Zulip instance URL (e.g., https://example.zulipchat.com) | |
| ZULIP_EMAIL | Yes | Your Zulip bot's email address | |
| ZULIP_API_KEY | Yes | Your Zulip bot's API key |
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
Server capabilities have not been inspected yet.
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 |
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 8 tools
Each tool has a clearly distinct purpose targeting different Zulip operations: reactions, message history, topics, users, channels, posting messages, direct messages, and subscriptions. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.
All tools follow a consistent 'zulip_verb_noun' pattern with snake_case, such as 'zulip_add_reaction' and 'zulip_get_channel_history'. This predictable naming convention enhances readability and usability across the tool set.
With 8 tools, this server is well-scoped for interacting with Zulip's core features like messaging, channels, users, and subscriptions. Each tool serves a specific, necessary function without bloat or redundancy, making the count appropriate for the domain.
The tool set covers essential Zulip operations including reading and posting messages, managing channels and users, and handling reactions. Minor gaps exist, such as updating or deleting messages, but agents can likely work around these with the provided tools for most workflows.