Listed from the MCP registry; nobody on Odel publishes it.
Is this yours? Claim itZoom Productivity server for creating and managing Zoom Sheets, Paper, and Slides content.
One address for any MCP client. You sign in at zoom.us once, after adding it.
Not assessed yet.
Odel charges nothing per call. The publisher may charge for its own service.
| Access to | Read | Change |
|---|---|---|
| Sheets |
From the sign-in at zoom.us, as the endpoint publishes it. You approve it there.
Odel could not list its tools without signing in.
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.
Update the relevant server.json.
Increment the version field before publishing an update.
Change into the corresponding server directory.
Refresh or establish a login session if needed:
mcp-publisher login github
Publish the entry:
mcp-publisher publish
Verify the published record using the registry API URLs listed above.
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.