A Zulip MCP that is honest about what reaches real people
113 nodes across channels and topics, messages and reactions, drafts, scheduled messages and reminders, users, user groups, invitations, uploads and organization settings. Six of them deliver something a person receives, and each says so on the node before it runs. Two safe rehearsals are built beside them, because Zulip has no test mode, no sandbox and no idempotency key anywhere on its API.
What the Zulip MCP connector does
The Zulip connector for Mattering Automations is 113 nodes on Zulip's REST API, generated from the machine readable OpenAPI description in Zulip's own source tree rather than written from memory. Forty nodes read and seventy three act. Channels, channel folders, topics, subscriptions and default channels cover the places conversation happens. Messages, reactions, message flags, edit history, read receipts and message search cover the conversation itself. Drafts, scheduled messages and reminders cover text that is composed now and delivered later, or never. Users, user groups, custom profile fields, invitations and invitation links cover who is in the organization. Alert words, linkifiers, code playgrounds, allowed domains, saved snippets, custom emoji and attachments cover the organization settings and reference data around all of it.
Every capability is a node on the Automations canvas, and every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and any other MCP capable assistant can use them, alongside Matter, the AI assistant built into the platform. So an assistant can read a week of a channel with Zulip: Get Messages, draft a summary, and stop at Zulip: Create Drafts, where a person decides whether it is ever sent.
The credential is three fields, not two, and this is the thing people get wrong first. Zulip authenticates with HTTP Basic where the username is an email address rather than a username, and the password is the API key. That alone is only a labelling surprise. The part that forces a third field is that every Zulip organization is its own realm on its own hostname, whether that is a Zulip Cloud subdomain or a self hosted server, and an API key is a row in exactly one realm. A key issued by one organization means nothing at another. So the site travels with the key, on the credential, and no node in this connector carries a site field. If you arrive expecting a single token to paste, this is the page section to read before anything else.
Sending a message reaches real people and nothing here can undo that. Six nodes deliver something somebody receives: Zulip: Send Channel Message, Zulip: Send Direct Message, Zulip: Create Scheduled Message, Zulip: Create Message Reminder, Zulip: Send Invitations and Zulip: Resend Email Invitation. There is no test mode and no sandbox, and deleting a message afterwards does not recall the notification email or the mobile push it already triggered, so a deleted message can still have been read. There are also no idempotency keys anywhere on this API, which means a retried send posts twice and the guard against that has to live in your workflow rather than in Zulip. Two rehearsals are built for exactly this: Zulip: Render Message Preview renders the same Markdown to HTML, resolving mentions, channel links and emoji, and sends nothing, and Zulip: Create Drafts stores text visible only to the account holding the credential, which is the human in the loop pattern for anything an automation composed.
Zulip is midway through renaming streams to channels, and you will see both words in the node list below. That is Zulip's transition rather than our inconsistency, and it is worth one paragraph because it confuses people reading Zulip's own documentation too. The product now calls them channels, and so do the node names here: Zulip: List Channels, Zulip: Create Channel, Zulip: Archive Channel. The wire has not finished moving, and the two spellings sit side by side in the current API: creating one is a channels path while listing them is still a streams path, and the identifier every other endpoint asks for is still called stream_id. So configuration fields in this connector keep the wire spelling, because renaming a field would be a quiet lie about the request being sent and would break the moment you compared a workflow against Zulip's docs. Node names use the word you will search the palette for; field names use the word the API takes.
This is a curated catalog rather than a wrapper over everything. The API describes 167 operations, of which 153 are callable by a client once the deprecated ones, the two that exist only on a Zulip development server and the three documentation pages Zulip carries as fake paths are set aside. This connector builds 111 of those 153 and deliberately leaves 42 out: the endpoints that mint or return API keys, the event queue that belongs to a trigger surface rather than a canvas node, raw image uploads, the endpoints that only mean something inside a Zulip client such as typing notifications and device registration, the two settings endpoints that carry around sixty options each and would render as a wall of controls, whole organization deletion and data export, list reordering, and the video call endpoints that depend on a third party being configured server side. Zulip: API Request is the advanced escape hatch that reaches any of them: it calls any Zulip API endpoint with the same credential and handles the form encoding for you.
One more behaviour is worth knowing before you build, because it makes a working connector look broken. A successful Zulip response can carry a list named ignored parameters, naming request parameters the server did not understand and silently dropped. The request returns success and the thing you asked for did not happen. This connector surfaces that list on the node output with a hint rather than swallowing it, because on this API it is usually a version signal: Zulip gates capability by an integer server feature level rather than by anything in the URL, so a self hosted realm a few releases behind drops newer parameters exactly this way. Zulip: Get Server Settings reads that feature level and the server version, needs no credential at all, and is the right first call when something behaves unexpectedly on a self hosted server.
One connection, three surfaces
- Visual automations. Drag Zulip nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Zulip node, ready to drop on the canvas
113 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 40
Zulip: Check Messages Match Narrow
Test a set of message ids against a search narrow and get back only those that match, with the matching text highlighted. This is how a workflow answers whether a message that just arrived belongs to a filter, without refetching the whole narrow.
Zulip: Check User Group Membership
Answer whether one person is in one group, counting subgroup membership unless direct_member_only is set. The right node for an approval gate that asks whether the requester belongs to a team.
Zulip: Get Channel
Fetch one channel by its numeric id, including its permission groups, retention policy and subscriber count.
Zulip: Get Channel Email Address
Get the email address that posts into a channel, so a system that can only send email can still reach Zulip. Treat the result as sensitive: anyone holding that address can post to the channel without a Zulip account. Requires the organization to have the email gateway configured.
Zulip: Get Channel ID By Name
Look up a channel's numeric id from its name. Worth a node of its own because names are what a person types and ids are what the rest of the API wants, and a name that no longer exists fails here clearly instead of failing later as a confusing error on a send.
Zulip: Get Channel Subscribers
List the user ids of everyone subscribed to a channel. Ids only, with no names attached, so pair it with List Users when you need people rather than numbers.
Zulip: Get File Temporary URL
Turn an uploaded file's path into a short lived unauthenticated download URL, so a downstream worker can fetch the bytes without holding a Zulip credential. The URL grants access to the file to anyone who has it, so treat it as sensitive and do not store it. The path parameters come from splitting a user_uploads path: the first segment is the numeric realm id and the rest is the filename part, which contains literal slashes.
Zulip: Get Message
Fetch one message by id, including its raw Markdown source alongside the rendered content. Useful after a trigger hands you a message id and you need the body the author actually typed.
Zulip: Get Message Edit History
Fetch every edit ever made to a message, oldest first, with the previous content and previous topic recorded on each revision and an HTML diff of what changed. Returns an error when the organization has message edit history disabled.
Zulip: Get Messages
Fetch a slice of message history. Pagination here is ANCHOR based rather than offset or cursor: name an anchor message, ask for a number of messages before and after it, and read found_oldest and found_newest in the response to know whether the history ran out. To walk backwards, anchor on the oldest id you already have and repeat until found_oldest is true. Use narrow to filter by channel, topic, sender or search text.
Zulip: Get Organization Presence
Read presence for everyone in the organization in one call, keyed by email address, with a server timestamp to compare against. People who have turned presence sharing off are absent rather than reported as offline.
Zulip: Get Own User
Fetch the account the credential belongs to, including its role and its own user id. The cheapest way to confirm a connection is alive and to discover which account an automation is acting as, which matters because every message this connector sends is attributed to this account.
Zulip: Get Read Receipts
List the user ids who have read a message. Read receipts are off by default in most organizations and each person can opt out individually, so an empty list means either nobody has read it or nobody who has is sharing that fact. Never present this count as a delivery guarantee.
Zulip: Get Server Settings
Read the server's version, its FEATURE LEVEL and the organization's public identity. This is the diagnostic node for this connector: Zulip gates capability by the integer zulip_feature_level rather than by anything in the URL, so a node that behaves unexpectedly on a self hosted realm is usually running against a server older than the feature it needs. Zulip Cloud tracks the latest release; a self hosted realm is whatever its administrator installed. This endpoint needs no credential, which also makes it a safe first call.
Zulip: Get Subscription Status
Answer whether one person is subscribed to one channel. Cheaper than listing a channel's subscribers when the question is about a single person, and note the path keeps the old spelling at /subscriptions/{stream_id} while the sibling endpoint one level up uses /channels.
Zulip: Get User
Fetch one person by their numeric user id.
Zulip: Get User By Email
Fetch one person by email address, which is the bridge from a record in another system to a Zulip user id. Whether this resolves at all depends on the organization's email visibility setting: where addresses are hidden, only an administrator can look someone up this way.
Zulip: Get User Channels
List the channel ids one person is subscribed to. The result is limited by what the acting account is allowed to see, so a short list can mean a narrow view rather than a quiet colleague. This path uses the new channels spelling while its sibling one level deeper still says subscriptions.
Zulip: Get User Group Members
List the user ids in a group. By default this includes people who are only in it through a subgroup, which is usually what a notification workflow wants; set direct_member_only to see the group's own roster instead.
Zulip: Get User Group Subgroups
List the group ids nested inside a group. Groups nest arbitrarily deep, so leave direct_subgroup_only off to see the whole tree flattened.
Zulip: Get User Presence
Read whether one person is currently active or idle, with the timestamps behind it. The path parameter is POLYMORPHIC: it accepts either a numeric user id or an email address, which is unusual on this API and is why the field is typed as a string.
Zulip: Get User Status
Read one person's status text and status emoji, which is the away or in a meeting line they set for themselves. Different from presence, which is whether they are online.
Zulip: List Alert Words
List the words that notify the acting account whenever they appear in a message. Personal to that account and invisible to everyone else.
Zulip: List Allowed Domains
List the email domains allowed to join the organization. Empty usually means the organization is invitation only rather than open to everybody.
Zulip: List Attachments
List the files the acting account has uploaded, with the messages each one appears in and the total storage used. An attachment with an empty message_ids array is orphaned, which is what a storage cleanup workflow looks for.
Zulip: List Channel Folders
List the organization's channel folders, which group channels in the sidebar. This is the lister behind every folder picker here. The spec declares this GET's parameter under a request body; on a GET it travels in the query string.
Zulip: List Channel Topics
List the topics in a channel that the acting account can see, most recently active first, each with the id of its newest message. This is the lister behind every topic picker in this connector, which is why it takes the channel as a path parameter: a topic only means something inside one channel.
Zulip: List Channels
List the organization's channels. This is the lister behind every channel picker in this connector. The path is /streams even though the product calls these channels: Zulip is midway through renaming streams to channels and the create endpoint has moved while the lister has not. Private channels the acting account cannot see are simply absent rather than reported as an error. Unpaginated: the whole set comes back in one response.
Zulip: List Custom Emoji
List the organization's custom emoji. Note the SHAPE OF THE RESPONSE: emoji is an object keyed by emoji id rather than an array, so a workflow reads it by key rather than looping a list. That shape is also why custom emoji cannot back a picker in this connector.
Zulip: List Custom Profile Fields
List the organization's custom profile fields with their ids, types and hints. Read this before writing profile data: the id is what every profile write takes, and the type decides the value format. Type 1 is short text, 2 long text, 3 a list of options, 4 a date, 5 a link, 6 a person, 7 an external account, 8 pronouns.
Zulip: List Drafts
List the acting account's synced drafts. Drafts are private to the account that owns them and are never delivered, which makes them the safest place for an automation to stage message text a person will review before sending.
Zulip: List Invitations
List the organization's outstanding invitations. Both kinds come back in one array and are told apart by is_multiuse: an email invitation carries the address it went to, and a reusable link carries link_url. Treat link_url as sensitive, because anyone holding it can join the organization.
Zulip: List Linkifiers
List the organization's linkifiers, which turn patterns in message text into links, such as a ticket number becoming a link to the tracker. Note the path asymmetry with the write endpoints, which live under /realm/filters.
Zulip: List Reminders
List the reminders the acting account has set on messages. Each carries the message it points back at and when it will fire.
Zulip: List Saved Snippets
List the acting account's saved snippets, which are reusable blocks of message text. Useful as a source of approved wording an automation can insert rather than composing prose itself.
Zulip: List Scheduled Messages
List the messages the acting account has queued for future delivery. A scheduled message that could not be delivered comes back with failed set to true, which is worth checking on a schedule because nothing else tells you.
Zulip: List Subscriptions
List the channels the acting account is subscribed to, with its own per channel settings such as colour, muting and notification preferences. Different from List Channels, which describes the organization; this describes one account's relationship to it.
Zulip: List User Groups
List the organization's user groups, each with its direct members and subgroups. SYSTEM GROUPS ARE INCLUDED and are the ones with is_system_group true and names like role:members; they are Zulip's own role groups and cannot be edited. This is the lister behind every group picker here. The spec declares this GET's parameter under a request body; on a GET it travels in the query string.
Zulip: List Users
List everyone in the organization. This is the lister behind every person picker in this connector. BOTS AND DEACTIVATED ACCOUNTS ARE INCLUDED, told apart by is_bot and is_active, so filter downstream when you mean humans. Email addresses come back in delivery_email only when the organization's email visibility setting permits it, and are null otherwise. Unpaginated: the whole membership comes back in one response.
Zulip: Render Message Preview
Render Zulip Markdown to HTML without sending anything. This is the safe rehearsal for a send: it resolves mentions, channel links and emoji exactly as the real message would, and nobody is notified. Use it to check generated message text before a Send Channel Message node runs.
Action nodes 73
Zulip: API Request
Call any Zulip REST endpoint this connector does not ship as its own node, using the same site URL and credential. This exists because the catalog is curated: 42 of the API's current operations are deliberately not built, and this node reaches them without waiting for a release. It handles Zulip's form encoding for you, including the rule that non string values are JSON encoded inside the form. Prefer a purpose built node where one exists, because those carry the pickers, the defaults and the warnings.
Zulip: Add Alert Words
Add words that will notify the acting account. Returns the full list afterwards, not just what was added, so the response is a complete picture rather than a diff.
Zulip: Add Allowed Domain
Allow an email domain to join the organization. This widens who can sign up, so it is a security change: adding a shared consumer mail domain effectively opens the organization to anyone. Administrator only.
Zulip: Add Code Playground
Register an external code playground, so fenced code blocks in a given language get a button that opens the snippet there. Administrator only. The code is sent to whatever site the template names, so point it somewhere the organization is willing to paste source into.
Zulip: Add Default Channel
Add a channel to the set every new member of the organization joins automatically. Administrator only. The path is /default_streams, one of the places the old spelling survives.
Zulip: Add Linkifier
Create a linkifier. Administrator only, and it changes how EVERY message in the organization renders, including messages already sent, so a pattern that is too broad quietly turns ordinary text into links everywhere. The write path is /realm/filters even though the read path is /realm/linkifiers.
Zulip: Add Reaction
React to a message with an emoji, as the account holding the credential. For standard emoji the name alone is enough. A reaction is visible to everyone who can see the message, so this is a public acknowledgement rather than a private note.
Zulip: Archive Channel
Archive a channel. The HTTP verb is DELETE but the effect is archival: the channel and its messages stop appearing for members, and an administrator can restore it by setting is_archived to false with Update Channel. Every subscriber loses access at once, so this is disruptive even though it is reversible.
Zulip: Create Channel
Create a channel and subscribe an initial set of people to it. Note the path: creating uses the NEW spelling at /channels/create while listing and updating still use /streams, which is the clearest sign the rename is unfinished. Turning announce on posts a notice to the organization's announcements channel, which reaches real people. is_web_public makes the channel readable by anyone on the internet.
Zulip: Create Channel Folder
Create a folder for grouping channels in the sidebar. Another path using the new create suffix, alongside /channels/create.
Zulip: Create Custom Profile Field
Add a custom profile field to the organization. Administrator only. field_type is a number: 1 short text, 2 long text, 3 list of options, 4 date, 5 link, 6 person, 7 external account, 8 pronouns. Marking a field required prompts every member to fill it in, which is visible to all of them.
Zulip: Create Drafts
Create one or more drafts for the acting account. Nothing is sent and nobody is notified: a draft is private to its owner until they choose to send it. This is the human in the loop pattern for a message an automation composed.
Zulip: Create Message Reminder
Ask Zulip to remind the acting account about a message at a future time. THIS REACHES A REAL PERSON when it fires, though only the account that owns the credential: the reminder arrives as a direct message from the reminder bot. Nothing is sent now.
Zulip: Create Reusable Invitation Link
Mint a reusable join link. Nothing is emailed, which makes this the quieter half of invitations, but THE RETURNED LINK IS A CREDENTIAL: anyone who has it can join the organization at the role it encodes until it expires or is revoked. Do not post it anywhere the intended audience is not already the whole audience, and prefer a short expiry.
Zulip: Create Saved Snippet
Save a reusable block of message text for the acting account. Private to that account and never delivered.
Zulip: Create Scheduled Message
Queue a message for delivery at a future time. THIS REACHES REAL PEOPLE when it fires. Nothing is sent now, which makes this the gentler way to automate an announcement: the queued message is visible in Zulip and can be edited or deleted before its time. The delivery time is a Unix timestamp in seconds and must be in the future.
Zulip: Create User
Create an account directly, without an invitation. Administrator only, and it takes a PASSWORD, which means this node is only appropriate where the password is generated and delivered securely by something else. For normal onboarding, prefer Send Invitations, which lets the person set their own password. The password is never echoed back and is redacted from this node's output.
Zulip: Create User Group
Create a user group, which is a mentionable set of people that can also be granted permissions on channels. Another path using the create suffix rather than a bare POST to the collection.
Zulip: Deactivate Custom Emoji
Retire a custom emoji. Existing reactions and messages using it keep rendering; it stops being offered for new use. Uploading a new custom emoji is not built here because it takes raw image bytes; use the API Request passthrough or the Zulip web app.
Zulip: Deactivate User
Deactivate an account. The person is signed out everywhere and cannot log in, and their messages stay. This is reversible with Reactivate User. Supplying a notification comment EMAILS THE PERSON, so leave it blank for a silent offboarding. On a paid Zulip Cloud plan a deactivation also frees the seat, which changes billing.
Zulip: Deactivate User Group
Deactivate a user group. Zulip has no hard delete for groups, which is deliberate: a group may be named in channel permissions, and deactivating fails with a clear error while anything still depends on it.
Zulip: Delete Allowed Domain
Stop allowing an email domain to join. Existing members with addresses at that domain keep their accounts.
Zulip: Delete Custom Profile Field
Remove a custom profile field from the organization. EVERY MEMBER'S VALUE FOR IT IS DELETED WITH IT and there is no undo.
Zulip: Delete Draft
Delete one of the acting account's drafts.
Zulip: Delete Message
Permanently delete a message. There is no undelete and no trash. Deleting does not recall a notification email or mobile push the message already triggered, so a deleted message can still have been read. Message deletion is restricted by organization policy and returns an error when the acting account is not permitted.
Zulip: Delete Reminder
Cancel a reminder before it fires.
Zulip: Delete Saved Snippet
Delete one of the acting account's saved snippets.
Zulip: Delete Scheduled Message
Cancel a queued message so it is never delivered. This is the undo for Create Scheduled Message and the reason scheduling is safer than sending: before the delivery time there is still a way out.
Zulip: Delete Topic
Permanently delete every message in one topic of a channel. There is no undo. On a large topic the call may only get part way through, in which case complete comes back false and the node must be run again to finish, so treat a single success as incomplete until complete is true.
Zulip: Edit Draft
Replace a draft's contents. The whole draft object is sent, not a partial patch, so read the current draft first if you only mean to change one field.
Zulip: Edit Saved Snippet
Change a saved snippet's title or body. Only the fields you fill in are changed.
Zulip: Mute User
Mute someone for the acting account, hiding their messages and notifications. Personal and invisible to the person muted.
Zulip: Reactivate User
Restore a deactivated account. The person can log in again and their old subscriptions come back. On a paid Zulip Cloud plan this consumes a seat again.
Zulip: Remove Alert Words
Stop alerting on the given words. Returns the remaining list.
Zulip: Remove Attachment
Permanently delete an uploaded file. Any message linking to it keeps the link and the link stops working, so prefer deleting attachments whose message_ids array is empty.
Zulip: Remove Code Playground
Remove a registered code playground. Zulip ships no endpoint that lists playgrounds, so the id comes from the create response or from the organization settings screen.
Zulip: Remove Default Channel
Take a channel out of the set new members join automatically. Existing members stay subscribed; this only changes what happens to the next person who joins.
Zulip: Remove Linkifier
Delete a linkifier. Messages that were rendering as links stop doing so, everywhere and immediately.
Zulip: Remove Own Profile Data
Clear custom profile field values on the account holding the credential. Takes field ids rather than objects, which is the asymmetry to watch: setting takes id and value pairs, clearing takes bare ids.
Zulip: Remove Reaction
Remove a reaction the acting account previously added. It cannot remove anyone else's reaction; the API scopes this to the authenticated user.
Zulip: Report Message To Moderators
Flag a message for the organization's moderators. THIS REACHES REAL PEOPLE: it posts into the moderation request channel and notifies whoever moderates. Requires the organization to have a moderation request channel configured, and returns an error when it does not.
Zulip: Resend Email Invitation
Send an outstanding invitation email again and restart its expiry clock. THIS REACHES A REAL PERSON: it is another email to the same address, so a nagging automation on a short schedule is a way to send someone a great many emails.
Zulip: Revoke Email Invitation
Cancel an outstanding email invitation so the link inside it stops working. The email itself has already been delivered and cannot be recalled.
Zulip: Revoke Reusable Invitation Link
Disable a reusable join link. This is the containment action when a link has been shared more widely than intended, and it takes effect immediately. Note the separate path: a reusable link is not revoked through the email invitation endpoint even though both appear in the same list.
Zulip: Send Channel Message
Post a message to a Zulip channel and topic. THIS REACHES REAL PEOPLE: every subscriber sees it immediately and it can trigger their email and mobile notifications, which deleting the message afterwards does not recall. Zulip has no test mode and no idempotency key, so a retried run posts the message twice. Rehearse with Render Message Preview, which renders the same Markdown and sends nothing. This node is the channel half of POST /messages; the direct message half is a separate node so the recipient picker can be correct on both.
Zulip: Send Direct Message
Send a direct message to one or more people. THIS REACHES REAL PEOPLE and cannot be undone: deleting the message afterwards does not recall the notification it already sent. There is no idempotency key on this API, so a retried run sends twice. Listing more than one recipient creates a single group conversation among all of them rather than separate one to one messages.
Zulip: Send Invitations
Email invitations to join the organization. THIS REACHES REAL PEOPLE: every address listed gets an email immediately, and there is no idempotency key, so a retried run emails everyone a second time. Revoking an invitation afterwards does not unsend the email. Channel ids are required by the API, so decide what the new members will join before running it.
Zulip: Set Topic Visibility Policy
Mute, unmute or follow a topic for the acting account. This is the supported replacement for the retired muted topics endpoint. The policy is an integer rather than a word: 0 is inherit, 1 is muted, 2 is unmuted and 3 is followed.
Zulip: Subscribe To Channels
Subscribe people to channels. Two behaviours to know before using it. First, THIS CREATES CHANNELS THAT DO NOT EXIST rather than failing, so a typo in a channel name silently creates a channel. Second, subscribing other people notifies them, and leaving send_new_subscription_messages on posts a welcome message into each channel. Subscribing someone else requires permission and fails otherwise.
Zulip: Test Welcome Bot Message
Send yourself the welcome message a new member would receive, so the custom text can be checked before any invitation goes out. It reaches only the account holding the credential, which makes it the rehearsal step for Send Invitations.
Zulip: Unmute User
Stop muting someone for the acting account.
Zulip: Unsubscribe From Channels
Remove people from channels. Note that the parameters travel in a urlencoded BODY on this DELETE, which is Zulip's documented shape. Unsubscribing someone from a private channel can cost them access to its history permanently, which no automation can give back.
Zulip: Update Allowed Domain
Change whether an already allowed domain also covers its subdomains.
Zulip: Update Channel
Rename a channel, change its description, or change its privacy, folder and retention settings. Only the fields you fill in are changed. Making a public channel private does not retroactively hide what was already said in it unless history_public_to_subscribers is also changed, and changing retention can delete existing messages permanently.
Zulip: Update Channel Folder
Rename a channel folder, change its description, or archive it. Archiving a folder does not archive the channels inside it.
Zulip: Update Custom Profile Field
Change a custom profile field's label, hint or options. The field TYPE cannot be changed after creation, which is why it is absent here: a type change would invalidate every stored value.
Zulip: Update Linkifier
Change a linkifier. Both pattern and url_template are required by the API even when only one of them is changing, so read the current values with List Linkifiers first and send both.
Zulip: Update Message
Edit a message, move it to a different topic, or move it to a different channel. Moving is the operation to be careful with: propagate_mode decides whether one message moves or the whole rest of the topic follows it, and change_all on a busy topic rewrites the location of every message in it.
Zulip: Update Message Flags
Add or remove a flag on a list of messages for the acting account. Flags are per person, so this changes what the account holding the credential sees and nobody else. The read flag is the one automations use most, to mark a batch of messages handled.
Zulip: Update Message Flags For Narrow
Flag every message matching a narrow, one anchored batch at a time. This is the supported replacement for the retired mark all as read endpoints. The response reports processed_count and found_newest so a workflow can loop until the whole narrow is done rather than assuming one call covered it.
Zulip: Update One Subscription Property
Change a single per channel preference for the acting account. The simple form of Update Subscription Settings, for when only one thing needs to change.
Zulip: Update Own Profile Data
Set custom profile field values on the account holding the credential. Field ids come from List Custom Profile Fields, and the value format depends on the field type: plain text for a short text field, an ISO date for a date field, and a JSON encoded list of user ids for a person field.
Zulip: Update Own Status
Set the status text and emoji on the account holding the credential. Sending an empty status_text clears it, which is how a scheduled workflow puts a status up in the morning and takes it down again.
Zulip: Update Scheduled Message
Change a queued message before it is delivered: its text, its destination, or when it goes out. Only the fields you fill in are changed. Fails once the message has already been sent.
Zulip: Update Status For User
Set another person's status text and emoji. Administrator only, and it changes something other people read as that person's own words, so use it for offboarding cleanup rather than for routine automation.
Zulip: Update Subscription Settings
Change several per channel preferences for the acting account in one call: colour, muting, pinning and each notification channel. These are personal settings and affect nobody else.
Zulip: Update Subscriptions In Bulk
Subscribe and unsubscribe the acting account in one call, which is how a workflow reconciles a whole channel list without a race between two separate requests.
Zulip: Update User
Change a person's name, organization role or custom profile fields. Administrator only. Role is a number rather than a word: 100 owner, 200 administrator, 300 moderator, 400 member, 600 guest. Lowering someone to guest removes access to channels they are not explicitly subscribed to.
Zulip: Update User By Email
The same changes as Update User, addressed by email instead of user id, so a workflow driven by an HR or directory system does not need a lookup step first.
Zulip: Update User Group
Rename a user group or change its description. Only the fields you fill in are changed. System groups cannot be changed and return an error.
Zulip: Update User Group Members
Add and remove people from a group in one call. Removing someone can revoke channel access the group granted them, so this is a permissions change and not only a directory edit.
Zulip: Update User Group Subgroups
Nest groups inside a group, or unnest them. Zulip rejects a change that would create a cycle.
Zulip: Upload File
Upload a file to Zulip from a URL and get back the path to embed in a message. Zulip's own endpoint takes raw bytes, so this node downloads the URL you give it over https and forwards the bytes; the cap is 50 MB here and the organization's own upload limit applies on top. Embed the returned url in a message as a Markdown link to attach it.
Connecting Zulip takes one credential
You generate the key inside your own Zulip organization, and the first decision is whose key it is. A personal key is at Personal settings, then Account & privacy, in the Zulip web app. A bot's key is at Personal settings, then Bots, behind the manage bot control on the bot you want. Prefer the bot. A bot has its own name and avatar in the conversation, so a message an automation posts reads as coming from an automation, while a personal key makes every automated message look like it came from a colleague who did not type it. A bot also survives that colleague leaving. Whichever you choose, the account's own permissions apply: several nodes here are administrator only, and organization policy can forbid an action for everyone regardless of role. The third field is your site, which is your organization's Zulip address rather than a shared API host, because a Zulip API key is only valid against the organization that issued it.
Decide which account holds the connection, and create a bot for it if you can. In the Zulip web app go to Personal settings, then Bots, add a generic bot, give it the name and avatar you want people to see, and note that it is subject to the same organization permissions as anyone else.
Copy the API key. For a bot, open Personal settings, then Bots, and use the manage bot control in the Actions column, where the key is shown with a copy control. For a person, open Personal settings, then Account & privacy, click Manage your API key under the API key heading, confirm your password and choose Get API key. Regenerating a key invalidates any connection using the old one, so treat it like a password.
Note your site address. On Zulip Cloud that is your organization's subdomain, such as acme.zulipchat.com, and typing the bare name is enough. On a self hosted server it is the full https host. Do not include the api path. Plain http is refused rather than silently upgraded, because HTTP Basic credentials sent over plain http are readable by anyone on the network path.
In Mattering Automations, open Connectors, click Add Connector, choose Zulip and then Create new credential. Fill in the three fields: site, the account email address the key belongs to, and the key itself.
Click Test Connection. Mattering builds the base URL from your site value and calls the endpoint that returns the account the credential belongs to, which proves the site, the email and the key together in one request. A 401 usually means the key is wrong or the key belongs to a different organization than the site you entered, and the two look identical on the wire. A 403 means the credential is fine and that account is not allowed to do the thing, which is a different finding.
All 113 Zulip nodes appear in the canvas palette. Run Zulip: Get Own User first to confirm which account your automations will be acting as, then Zulip: List Channels to check the connection sees what you expect. Both are read only. The credential is stored encrypted and never appears in workflow logs.
Common uses for the Zulip MCP
Alerts from every other system, landing in the right topic
This is the workflow most people want first and it is genuinely simple here: any other connector or trigger in Mattering can end at Zulip: Send Channel Message, which posts to a named channel and topic. The topic is the part worth designing rather than defaulting. Zulip threads by topic rather than by channel, so a deploy notification going to a per release topic stays readable while the same volume dumped into one topic does not. The topic picker in this connector is dependent on the channel you pick, because topics are strings scoped to one channel rather than entities with ids of their own, so it populates only after a channel is chosen. Two cautions belong in the design rather than in a surprise: there is no idempotency key on this API, so a workflow that can retry needs its own guard, and Zulip: Render Message Preview will show you exactly how generated Markdown resolves before anybody sees it.
A daily digest a person approves before it goes out
Zulip: Get Messages reads a slice of history with a narrow filter for channel, topic, sender or search text, an AI step summarises it, and the summary lands in Zulip: Create Drafts rather than in a channel. A draft is private to the account that owns it until that person chooses to send it, which makes this the safest shape for anything an automation wrote. If you would rather it went out on its own schedule with a window to cancel, Zulip: Create Scheduled Message is the gentler send: the queued message is visible in Zulip and can be edited or deleted before its time, which a plain send never can be. Note how paging works here before you build a long lookback: Zulip: Get Messages is anchor based rather than offset based, so you name an anchor message, ask for a count before and after it, and read the found oldest flag to know when the history ran out.
Onboarding that puts a new hire in the right rooms
An HR system, a form or a Productivity task can drive the whole sequence. Zulip: Send Invitations emails an invitation and lets the person set their own password, which is why it is the right node for normal onboarding rather than Zulip: Create User, which is administrator only and takes a password you would then have to deliver securely yourself. Zulip: Subscribe To Channels adds them to the channels their team lives in, and Zulip: Update User Group Members puts them in the groups that drive mentions and permissions. Read the subscribe node's warning before you template channel names into it: subscribing to a channel that does not exist creates it rather than failing, so a typo silently produces a channel nobody meant to make. Zulip: Test Welcome Bot Message is the rehearsal, sending the welcome text to your own account so the copy can be checked before any invitation reaches a new colleague.
Offboarding, and the invitation links you forgot about
Zulip: Deactivate User signs somebody out everywhere and blocks further logins while leaving their messages in place, and it is reversible with Zulip: Reactivate User. Leave the notification comment blank for a silent offboarding, because supplying one emails the person. The part teams miss is the invitation surface: Zulip: List Invitations shows both pending email invitations and reusable join links, Zulip: Revoke Email Invitation cancels the first kind and Zulip: Revoke Reusable Invitation Link cancels the second. A reusable link is a credential in its own right, since anyone holding it can join the organization at the role it encodes until it expires or is revoked, so a periodic sweep that lists them and revokes anything stale is a small workflow with real value.
Moderation and cleanup that a person still signs off
Zulip: Report Message To Moderators posts into the organization's moderation request channel and notifies whoever moderates, so a classifier can escalate without any human watching a firehose. Keep the destructive half behind an approval step: Zulip: Delete Message is permanent with no undelete and no trash, and Zulip: Delete Topic removes every message in a topic and can only get part way through a large one, reporting an incomplete flag that means it has to be run again. Storage cleanup is the safer sibling. Zulip: List Attachments returns every file the acting account has uploaded along with the messages each one appears in, so a workflow can find orphaned uploads with an empty message list and clean those up with Zulip: Remove Attachment, which is the version of this that breaks nothing anybody is still reading.
Zulip plus the rest of your stack, in one workflow
The reason to run Zulip here rather than only inside an assistant's local configuration is that these nodes are steps, so they chain. A support ticket can open a channel with Zulip: Create Channel, subscribe the right people and post the context in one run. A monthly report can read Zulip: List Users and Zulip: List Channels into a Mattering database and open a Productivity task when something drifts. A file that arrives elsewhere can go into Zulip with Zulip: Upload File, which takes an https URL, downloads the bytes and returns the path to embed in a message. And Zulip: Get File Temporary URL goes the other way, turning an uploaded file's path into a short lived unauthenticated download link a downstream worker can fetch without ever holding a Zulip credential, which is convenient and is exactly why the node says to treat that link as sensitive.
Example: A weekly channel digest that nobody sends by accident
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a weekly schedule fires. This connector has no trigger nodes, because Zulip's real time surface is an event queue that long polls and holds a connection open until something happens, which is the wrong shape for a canvas step and the right shape for a trigger we have not built yet. Zulip workflows read on a schedule rather than listening for a push.
Zulip: Get Messages reads the week from the channel you care about, anchored on the newest message and asking for a count backwards, with a narrow filter naming the channel. Because paging is anchor based, a longer lookback is a loop that repeats until the found oldest flag comes back true rather than a page number that increments.
An AI step reads the thread and writes the digest: what was decided, what is still open, who is waiting on whom. Nothing has been written to Zulip at this point and nobody has been notified.
Zulip: Render Message Preview renders the draft text exactly as Zulip would, resolving mentions, channel links and emoji, so a bad mention or a broken link is caught before it can page anyone. Still nothing sent.
Zulip: Create Drafts stores the digest as a draft on the bot account, and a Mattering Productivity task is opened for the person who owns the channel, with the rendered text in it.
On approval, Zulip: Send Channel Message posts it to the channel and topic. That step is the only one in the run that reaches anybody, it cannot be undone once the notifications go out, and it is behind a person on purpose.
Zulip MCP questions, answered
What can this connector actually do in Zulip?
113 nodes: 40 read and 73 act. Reads cover channels, channel folders, topics, subscriptions and subscription status, messages, message search, edit history and read receipts, users, user presence and status, user groups and their members and subgroups, drafts, scheduled messages, reminders, invitations, attachments, custom profile fields, custom emoji, linkifiers, alert words, allowed domains, saved snippets and the server's own settings. Writes cover sending channel and direct messages, scheduling messages and reminders, editing and moving messages, reactions and message flags, creating, updating and archiving channels and channel folders, subscribing and unsubscribing people, creating, updating, deactivating and reactivating users, user groups and their membership, invitations and reusable join links, uploads, muting, and the organization settings around all of it. Not included, and worth knowing before you plan: there are no trigger nodes, because Zulip's event queue is a long polling surface that belongs to a trigger we have not built; the endpoints that mint or return API keys are deliberately absent; and raw image uploads for avatars and custom emoji, the two very large settings endpoints, organization deletion and data export, and the video call endpoints are all cut. Zulip: API Request reaches any of them as an advanced escape hatch.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP capable assistant, including Claude and ChatGPT, can connect to your workspace and work with Zulip through them. Matter, the assistant built into the platform, uses the same nodes natively. The same nodes are also steps on the automation canvas, so a workflow an assistant helps you design then runs on a schedule with nobody present. With a chat tool specifically, the sensible split is to hand an assistant the 40 read nodes freely and put the six that reach real people behind a condition or an approval step, because an assistant that can post to a channel can page everyone in it.
Does Zulip publish its own MCP server?
We are not going to give you a clean yes or no here, because the public evidence does not support one and we would rather say so than guess. Here is what is actually observable. A repository named zulipmcp sits in Zulip's own GitHub organization, and it is the only MCP repository there. Its README's install command and its licence badge link both point at a repository of the same name under a different organization, and GitHub records that other repository as a fork of the one in Zulip's organization rather than the other way round. Zulip's own website does not mention MCP or the Model Context Protocol anywhere, and the repository is not referenced in the API documentation navigation on zulip.com. Its README does not enumerate the tools it exposes. Read those facts yourself before relying on either interpretation, and be sceptical of any page, including this one, that resolves them confidently in either direction. What we can state without hedging is what this connector is: 113 typed nodes generated from Zulip's own OpenAPI description, usable over MCP and as steps on an automation canvas. That second half is the part that does not depend on any comparison. These nodes run on a schedule with nobody present, chain with every other connector in one workflow, hold the credential once in a shared workspace rather than in each person's local configuration, and carry destructive flags on the nodes that delete things and explicit warnings on the six that reach real people.
Why does the credential need three fields when other tools only need a key?
Because a Zulip API key does not identify you on its own, and there is no single API host to send it to. Zulip's documented authentication is HTTP Basic where the username is the account's email address and the password is the API key, so the email is not decoration, it is half the credential. And every Zulip organization is a separate realm on a separate hostname: a Zulip Cloud organization is its own subdomain and a self hosted organization is its own server. A key is issued by one realm and means nothing anywhere else, so the site has to travel with it. Putting the site on the credential rather than on each node is deliberate: a key is one to one with a realm forever, so a site field on every node would be the same value copied a hundred times and one of them eventually wrong. The practical consequence is that the two most common connection failures look identical. A 401 can mean the key is wrong, or it can mean the key is perfectly good and belongs to a different organization than the site you typed.
Why do some nodes say channel and some fields say stream?
Because Zulip is midway through renaming streams to channels and has not finished, and this connector reflects that rather than hiding it. The product word today is channel, and every node here uses it. The API has moved only partly: some paths use the new spelling while the lister for the same resource still uses the old one, and the identifier almost every endpoint asks for is still called stream_id. Configuration fields therefore keep the wire spelling. Renaming a field to look tidy would be a quiet lie about the request being sent, and it would break the first time you compared a workflow against Zulip's own API documentation, which still uses the old names in the same places. If Zulip finishes the rename, the field names change and the node names do not, which is the right way round, because a node name is the stable palette identifier and renaming one would orphan every workflow using it.
What happens if a workflow retries a message send?
It sends twice, and there is nothing on Zulip's side that will stop it. This API has no idempotency keys anywhere. The local id field on message sending is not one either: it is an echo field a client uses for its own optimistic rendering, and the server does not deduplicate on it. So a guard against duplicate sends has to live in your workflow, usually as a record of what has already been sent that a condition checks first. Three things make this easier to live with. Zulip: Render Message Preview lets you rehearse the exact rendered message without sending anything. Zulip: Create Drafts puts composed text somewhere only the acting account can see it. And Zulip: Create Scheduled Message queues a message that stays visible and cancellable in Zulip until its delivery time, which is the closest thing to an undo this API offers. Deleting a message after it has been sent is not an undo: it does not recall the notification email or the mobile push it already triggered, so a deleted message can still have been read.
Do I need a paid Zulip plan for this?
No. Zulip's own plan comparison lists REST API custom integrations, custom webhooks and admin controls for bots and integrations on the free Zulip Cloud plan, and a key is generated from a user's own settings with no plan step involved. Zulip is also free and open source software, licensed under Apache 2.0, that you can self host at no licence cost. Two free plan limits are worth knowing because they change what a workflow can do rather than whether it connects. Zulip documents 10,000 messages of search history on the free plan against unlimited search history on its paid plans, which is a limit on search rather than on the messages themselves, so a text search narrow can reach the end of it on a busy organization. And free plan file storage is documented as 5 GB total for the organization, where the paid plans are per user, which matters for any workflow that uploads. Everything else that will block you is permissions rather than billing. Several nodes here are administrator only, including creating users and most organization settings, and Zulip lets an organization set policies that forbid an action for everyone regardless of role, such as who may delete messages. Both surface as a 403 rather than a 401, which is the useful distinction: a 403 means your credential is fine and the account cannot do that.
How much history can one node read, and what are the rate limits?
Two separate answers, and the second is the one that shapes workflow design. On history, message reading is the only paginated endpoint on this API and it pages by anchor rather than by offset: you name an anchor message, ask for a number of messages before and after it, and read the found oldest and found newest flags to know when you have reached the end. Almost every other list endpoint is unpaginated and returns the whole collection in one response, which is fine for most organizations and is worth knowing before you point one at a very large one. On rate limits, Zulip documents a default configuration of 200 total API requests per minute per user, with separate and much lower limits on authentication attempts, and it states that the limits are configurable and can vary by server, so treat 200 as the documented default rather than a guarantee, especially on a self hosted organization. Every response carries the remaining count, the limit and a reset time in its headers, and a 429 carries a retry delay in the response body as well as in the headers, which a client reading only headers will miss. This connector does not auto paginate anywhere, deliberately: an unbounded number of requests should never hide behind one canvas step.
A node returned success but nothing happened. What is going on?
Check the node's output for the ignored parameters list, which is the specific failure this describes. Zulip can answer a request successfully while silently dropping parameters it did not recognise, and it names them in a list on the response rather than raising an error. This connector copies that list onto the node output with a hint instead of swallowing it, because the usual cause is a version gap: Zulip gates capability by an integer server feature level rather than by anything in the URL, so a self hosted organization a few releases behind will drop newer parameters exactly this way while reporting success. Run Zulip: Get Server Settings, which returns the server version and its feature level, needs no credential at all, and is the cheapest first call when a node behaves in a way the documentation does not describe. Zulip Cloud tracks the current release, so this is almost always a self hosted question.
Which nodes are dangerous, and how would I know?
The connector labels them rather than leaving you to find out. Six nodes deliver something a real person receives: sending a channel message, sending a direct message, scheduling a message, creating a reminder, sending invitations and resending an invitation email. Six more destroy data without reaching anybody: deleting a message, deleting a topic, archiving a channel, deactivating a user, deleting a custom profile field, which takes every member's value for it with it, and removing an attachment. Two more are dangerous in a way the HTTP method does not show, and both say so on the node. Zulip: Subscribe To Channels creates a channel that does not exist rather than failing, so a typo in a templated channel name silently makes a channel. And Zulip: Create Reusable Invitation Link returns a credential, because anyone holding that link can join your organization at the role it encodes until it expires or is revoked. Every one of those carries the warning in its own description on the canvas, so the caution arrives before the node runs rather than in a postmortem.
Put Zulip to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Zulip is a product of its respective owner; Mattering is an independent platform.