REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Zoom Workflows server for deploying, running, and monitoring Workflow Builder automations.
Pick the AI app you use, then copy the settings.
Passed 5/5 checks · What you ask goes through the maker’s server (mcp.zoom.us) · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
Zoom Workflows MCP Serverhttps://mcp.zoom.us/mcp/workflow/streamableClick Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
+ConnectorsZoom Workflows MCP Server
Use Zoom Workflows MCP Server and tell me what you can do for me, then show me one thing✓ If Claude says it is using Zoom Workflows MCP Server or shows a Zoom Workflows MCP Server tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT, depending on your plan
Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only
Plugins+Add custom MCP server
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
Zoom Workflows MCP Serverhttps://mcp.zoom.us/mcp/workflow/streamableStart a new chat and pick Zoom Workflows MCP Server from your plugins before typing
Use Zoom Workflows MCP Server and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using Zoom Workflows MCP Server or shows a Zoom Workflows MCP Server tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user zoom-workflows https://mcp.zoom.us/mcp/workflow/streamableYou should see Zoom Workflows MCP Server listed as connected
Use Zoom Workflows MCP Server and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Zoom Workflows MCP Server or shows a Zoom Workflows MCP Server tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Use Zoom Workflows MCP Server and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Zoom Workflows MCP Server or shows a Zoom Workflows MCP Server tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Use Zoom Workflows MCP Server and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Zoom Workflows MCP Server or shows a Zoom Workflows MCP Server tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://mcp.zoom.us/mcp/workflow/streamableJSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user zoom-workflows https://mcp.zoom.us/mcp/workflow/streamableCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"zoom-workflows": {
"url": "https://mcp.zoom.us/mcp/workflow/streamable"
}
}
}VS Code (mcp.json)
{
"servers": {
"zoom-workflows": {
"type": "http",
"url": "https://mcp.zoom.us/mcp/workflow/streamable"
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 13, 2026
The registry name was verified with the GitHub account zoom, which owns the repo
Code last changed today
Uses MIT
Responded in 82 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed today, and the latest version (1.0.0) reached the registry today.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
A powerful toolkit for coding, providing semantic retrieval and editing capabilities.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
This project provides Zoom's registry of MCP servers at registry.modelcontextprotocol.io. It contains the published registry metadata for remote MCP servers. It does not contain the server implementations themselves.
io.github.zoom/zoom-workspacehttps://mcp.zoom.us/mcp/zoom/streamableZoom Workspace exposes Zoom meetings, Team Chat, and Zoom Docs to MCP clients. It supports natural-language retrieval of AI-generated summaries, transcripts, recordings, shared documents, and meeting assets, along with recording-specific resources such as playback links and next steps. It can retrieve Zoom Docs content, list cloud recordings, and create follow-up Zoom Docs from Markdown. This server is intended for workflows such as locating where a topic was discussed, generating agendas, capturing notes, identifying action items, and creating follow-up documents from existing Zoom collaboration data.
io.github.zoom/zoom-docshttps://mcp.zoom.us/mcp/docs/streamableZoom Docs provides a focused MCP surface for working with Zoom documents and notes. It currently supports creating new Zoom Docs from Markdown content and retrieving existing Zoom Docs or notes in Markdown form. The server is designed for structured document generation and readback flows used by AI agents and developer tooling, without exposing broader document lifecycle operations such as update or delete.
io.github.zoom/zoom-whiteboardhttps://mcp.zoom.us/mcp/whiteboard/streamableZoom Whiteboard provides MCP tools for creating new editable whiteboards and diagrams from prompts and for locating existing boards in a user's account. It is intended for workshop planning, visual collaboration, and diagram-generation use cases, including simple flowcharts and more technical diagram types. The server only exposes boards the authenticated user can access.
io.github.zoom/zoom-revenue-acceleratorhttps://mcp.zoom.us/mcp/revenue_accelerator/streamableZoom Revenue Accelerator provides a focused MCP surface for sales insights, conversations, and deal intelligence. It is intended for workflows such as reviewing customer interactions, preparing follow-up notes, and finding context from revenue-related conversations and activity.
io.github.zoom/zoom-team-chathttps://mcp.zoom.us/mcp/chat/streamableZoom Chat provides a focused MCP surface for chat channels, messages, contacts, files, and collaboration context. It is intended for workflows such as locating chat history, preparing summaries, and generating follow-ups from chat activity. The registry name remains io.github.zoom/zoom-team-chat for continuity with the existing published entry.
io.github.zoom/zoom-meetingshttps://mcp.zoom.us/mcp/meeting/streamableZoom Meetings provides a focused MCP surface for meeting search, recordings, transcripts, summaries, and meeting assets. It is intended for workflows such as locating meeting context, reviewing recordings, and preparing follow-ups from meeting content.
io.github.zoom/zoom-taskshttps://mcp.zoom.us/mcp/tasks/streamableZoom Tasks provides a focused MCP surface for creating, updating, assigning, and synchronizing tasks. It is intended for workflows such as managing task details, reviewing comments and steps, and coordinating work across collaborators.
io.github.zoom/zoom-adminhttps://mcp.zoom.us/mcp/admin/streamableZoom Admin provides MCP tools for viewing and updating account-wide settings (meeting, recording, security, chat, telephony), listing users and groups, and retrieving user settings and permissions.
io.github.zoom/zoom-canvashttps://mcp.zoom.us/mcp/canvas/streamableZoom Canvas provides MCP tools for creating, editing, and sharing Zoom documents with Markdown support, including block-level edits, comments, data tables, and collaborator and access management.
io.github.zoom/zoom-phonehttps://mcp.zoom.us/mcp/phone/streamableZoom Phone provides administrative MCP tools for sites, users, calling plans, phone numbers, call queues, auto receptionists, shared line groups, common areas, monitoring groups, emergency addresses, and push-to-talk.
io.github.zoom/zoom-productivityhttps://mcp.zoom.us/mcp/productivity/streamableZoom Productivity provides MCP tools for creating and managing Zoom Sheets content, including spreadsheets, sheets, and cell reads and edits.
io.github.zoom/zoom-roomshttps://mcp.zoom.us/mcp/rooms/streamableZoom Rooms provides MCP tools for listing and managing rooms, devices, locations, and tags, and for reading account, room, and location profiles and settings.
io.github.zoom/zoom-workflowshttps://mcp.zoom.us/mcp/workflow/streamableZoom Workflows provides lifecycle management for user-owned Workflow Builder automations: inspect node contracts, deploy or undeploy workflows, run them asynchronously, and monitor or resume executions.
io.github.zoom/zoom-workspaceshttps://mcp.zoom.us/mcp/workspace/streamableZoom Workspaces provides MCP tools for workspace reservation and management, including listing workspaces, locations, and assets, and creating, updating, or deleting reservations. It is separate from io.github.zoom/zoom-workspace, which is the general Zoom MCP server.
io.github.zoom/*streamable-http1.0.2 for Workspace, Docs, and Whiteboard; 1.0.1 for Revenue Accelerator, Team Chat, and Meetings; 1.0.0 for Tasks, Admin, Canvas, Phone, Productivity, Rooms, Workflows, and Workspaceshttps://registry.modelcontextprotocol.io/v0.1/servers?search=zoom&limit=100https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-workspace/versions/latesthttps://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-docs/versions/latesthttps://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-whiteboard/versions/latesthttps://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-revenue-accelerator/versions/latesthttps://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-team-chat/versions/latesthttps://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-meetings/versions/latesthttps://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-tasks/versions/latesthttps://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-admin/versions/latesthttps://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-canvas/versions/latesthttps://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-phone/versions/latesthttps://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-productivity/versions/latesthttps://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-rooms/versions/latesthttps://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-workflows/versions/latesthttps://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-workspaces/versions/latestThe MCP Registry entries in this repository are published with mcp-publisher.
For the Zoom-specific step-by-step publishing history and lessons learned, see RUNBOOK.md.
mcp-publisherPublishing under io.github.zoom/* requires proof of GitHub org ownership, which the interactive mcp-publisher login github flow cannot provide. The workflow at .github/workflows/publish.yml publishes with GitHub OIDC instead, so no personal token is needed.
main that change any zoom-*/server.json, and manually from the Actions tab (Run workflow, with an optional dry_run).name@version is not already in the registry, so bump version in any server.json you change.description is longer than 100 characters.From the CLI: gh workflow run publish.yml -f dry_run=true (or false to publish), then gh run watch.
server.json.version field before publishing an update. mcp-publisher login github
mcp-publisher publish
Example:
cd zoom-workspace
mcp-publisher publish
To publish the two newer entries:
cd ~/temp/mcp-registry-publish/zoom-revenue-accelerator
mcp-publisher publish
cd ~/temp/mcp-registry-publish/zoom-team-chat mcp-publisher publish
To publish every entry that is new or changed (see RUNBOOK.md for the full list and a loop):
cd ~/temp/mcp-registry-publish/zoom-meetings # 1.0.1 update
mcp-publisher publish
cd ~/temp/mcp-registry-publish/zoom-admin # new, 1.0.0 mcp-publisher publish
Published entries can be updated by modifying the corresponding server.json, incrementing the version, and republishing from that server's directory with mcp-publisher publish.