Zulip MCP Server

MCP server for interacting with Zulip

Local serverstdio

What is the Zulip MCP MCP server?

Most developer tooling work still happens through a UI a human drives. Zulip MCP MCP server moves it into the conversation instead. MCP server for interacting with Zulip.

The short version

MCP Server for the Zulip API, enabling AI assistants like Claude to interact with Zulip workspaces.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

The tools it exposes

The server publishes 2 tools. What each one is for:

  • Returns — List of streams with their IDs and information
  • Troubleshooting — If you encounter permission errors, verify that: 1. The bot API key is correct 2. The bot has been subscribed to the channels it needs to access 3

What it needs from you

Configuration is passed through the environment: ZULIP_EMAIL, ZULIP_API_KEY, ZULIP_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Zulip MCP's toolset — Returns, Troubleshooting — is a fair guide to whether it matches your workflow. It is maintained by Monadical-SAS; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
ReturnsList of streams with their IDs and information
TroubleshootingIf you encounter permission errors, verify that: 1. The bot API key is correct 2. The bot has been subscribed to the channels it needs to access 3. The Zulip URL is correct and accessible

How to install the Zulip MCP MCP server

{
  "mcpServers": {
    "zulip": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-zulip"
      ],
      "env": {
        "ZULIP_EMAIL": "your-bot@example.zulipchat.com",
        "ZULIP_API_KEY": "your-bot-api-key",
        "ZULIP_URL": "https://example.zulipchat.com"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
ZULIP_EMAILConfiguration value read at startup.Optional
ZULIP_API_KEYCredential the server authenticates with.Yes
ZULIP_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Zulip MCP to Returns.
  • Use Zulip MCP to Troubleshooting.

Frequently asked questions

It connects Zulip MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Returns, Troubleshooting) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Zulip MCP directly.