zulipchat

ZulipChat MCP Server bridges your favorite MCP clients (such as Claude Code, Gemini CLI, Cursor, Windsurf, and others) to your Zulip workspace. It exposes a core set of tools that let the AI assistant read and send Zulip messages, search history, resolve users, and manage identities. By using the included two-tier tool architecture, you can rely on the default Core Mode for common tasks (messaging, search, user resolution, and basic agent communications) or enable Extended Mode to unlock additional capabilities like scheduling messages, file uploads, event handling, and advanced searches. Start the server with your Zulip configuration so the MCP client can authenticate and interact with Zulip chat data in real time.

Prerequisites:\n- Python 3.8+ (or a compatible Python runtime)\n- pip (Python package installer)\n- Zulip API credentials configured via a zuliprc file (e.g., ~/.zuliprc)\n\nInstall:\nbash\npip install zulipchat-mcp\n\nConfigure for your environment:\n- Ensure you have a Zulip API key and server details saved in ~/.zuliprc or provide an equivalent zuliprc path.\n- Prepare your MCP client configuration to point to the ZulipChat MCP server.\n\nRun:\nbash\nuvx zulipchat-mcp --zulip-config-file ~/.zuliprc\n\nThis starts the ZulipChat MCP server using the uvx runner and your zuliprc for authentication. To enable extended tools, add the --extended-tools flag or the ZULIPCHAT_EXTENDED_TOOLS=1 environment variable.\n\nIntended usage with clients (example):\nbash\nuvx zulipchat-mcp --zulip-config-file ~/.zuliprc \n

Notes and tips:\n- Extended tools: Use --extended-tools or set ZULIPCHAT_EXTENDED_TOOLS=1 to register the full ~55 tools. This increases capability at the cost of additional token usage.\n- Debugging: Use --debug to enable verbose logging for troubleshooting.\n- Identity: Zulip supports dual identity (user + bot). If you need the assistant to post as the bot, supply a separate zuliprc for the bot via --zulip-bot-config-file.\n- Configuration options: You can customize the server behavior via the zuliprc file and environment variables; refer to the docs for details on supported options.\n- Common issues: Ensure your zuliprc is valid and accessible, and that network access to Zulip servers is allowed from the host running the MCP server.\n- Compatibility: Built on FastMCP with DuckDB for state persistence; it is designed for local execution with no external telemetry.