Zulip MCP Server
Related Servers
Alternatives to Zulip MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude to interact with Zulip workspaces, supporting capabilities such as posting messages, listing channels, sending direct messages, and accessing conversation history.812Apache 2.0
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that standardizes tool discovery, execution, and context management for AI applications.MIT
- AlicenseAqualityCmaintenanceA server implementing Model Context Protocol that enables AI assistants to interact with Slack API through a standardized interface, providing tools for messaging, channel management, user information retrieval, and more.11110Apache 2.0
- FlicenseNot gradedqualityFmaintenanceThis server implements the Model Context Protocol to facilitate meaningful interaction and understanding development between humans and AI through structured tools and progressive interaction patterns.57-
- AlicenseAqualityDmaintenanceA Model Context Protocol server that enables AI assistants to make HTTP requests (GET, POST, PUT, DELETE) to external APIs through standardized MCP tools.42MIT
- FlicenseNot gradedqualityDmaintenanceA Python server implementing the Model Context Protocol that exposes tools for querying external APIs, compatible with Claude Desktop and ChatGPT Desktop.-
TDQS
Scored across 25 tools
All 25 tools have clearly distinct purposes. Message tools are differentiated by operation type (single vs bulk, send vs edit vs delete). Stream and user tools each target a specific resource and action, leaving no ambiguity.
All tool names follow a consistent verb-noun pattern with hyphens (e.g., add-emoji-reaction, get-message, send-message). Even 'get-started' fits the pattern. No mixing of styles.
25 tools is on the higher end but appropriate for a comprehensive chat server like Zulip. The number covers message operations, streams, users, emoji, drafts, scheduled messages, and file uploads, though a few could be merged (e.g., get-user and get-user-by-email could be one tool).
The tool set covers core messaging and user operations well, but notable gaps exist: no tools to create or update streams, nor to manage user groups beyond listing them. Also, there is no tool to get all streams (only subscribed ones). These omissions could limit agent workflows.