Zulip MCP Server

Created By
avisekratha year ago
unofficial zulip mcp server
Overview

What is Zulip MCP Server?

Zulip MCP Server is an unofficial Model Context Protocol (MCP) server that exposes Zulip REST API capabilities, allowing AI assistants to interact programmatically with your Zulip workspace.

How to use Zulip MCP Server?

To use the Zulip MCP Server, clone the repository, install dependencies, configure your Zulip credentials in a .env file, and run the server using Node.js.

Key features of Zulip MCP Server?

  • User and Channel Directories: Access to organization members and channels.
  • Message Operations: Send, retrieve, edit, and delete messages.
  • Scheduled Messages: Create and manage scheduled messages and drafts.
  • User Operations: Manage user statuses and groups.
  • Integration Support: Compatible with various MCP clients like Claude Desktop, Cursor IDE, and Raycast.

Use cases of Zulip MCP Server?

  1. Automating message sending and retrieval in Zulip.
  2. Integrating Zulip with AI assistants for enhanced communication.
  3. Managing user interactions and channel activities programmatically.

FAQ from Zulip MCP Server?

  • Is Zulip MCP Server free to use?

Yes! It is open-source and free to use.

  • What are the prerequisites for installation?

You need Node.js 18+, TypeScript 5+, and access to a Zulip instance with API credentials.

  • Can I use it with other MCP clients?

Yes! It is compatible with any MCP-compliant client.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
avisekrath
Star
1
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago