Zoom Workspaces MCP server
Commit 13. Nov. 2026Ermöglicht es einem AI-Client, Workspace-Reservierungen, Standorte und Assets zu verwalten.
Auch bekannt als zoom/mcp-registry, zoom-workspaces
- Stars
- 3
- Tools
- —
- Downloads, 30 Tage
- —
- Neueste Version
- 1.0.0
- Letzter Commit
- 13. Nov. 2026
- Lizenz
- MIT
Was ist Zoom Workspaces MCP?
Ermöglicht es einem AI-Client, Workspace-Reservierungen, Standorte und Assets zu verwalten.
Zusammenfassung generiert aus dem README des Projekts
Über Zoom Workspaces MCP server
Dieser Server ermöglicht es dir, physische Büroressourcen über einen AI-Client zu verwalten. Er bietet spezialisierte Tools für die Handhabung von Workspace-Reservierungen, sodass Nutzer mit ihrer physischen Arbeitsumgebung über natürliche Sprache interagieren können. Dies unterscheidet sich vom allgemeinen Zoom MCP server, da der Fokus hier spezifisch auf der Logistik von Räumlichkeiten und Equipment liegt.
Nutzer können den Server verwenden, um verfügbare Workspaces, Standorte und spezifische Assets aufzulisten. Das Toolset umfasst die Möglichkeit, Reservierungen zu erstellen, zu aktualisieren oder zu löschen, was die Koordination von Büropräsenz oder Equipment-Bedarf erleichtert. Der Server arbeitet als Remote-Service via streamable-http Transportmethode und verbindet deinen AI-Agent direkt mit deinen Zoom Workspace-Managementdaten.
Was du damit machen kannst
- 1Verfügbare Büroflächen prüfenFrag die AI, um alle verfügbaren Workspaces und Standorte innerhalb der Organisation aufzulisten.
- 2Einen Workspace buchenGib der AI den Befehl, eine neue Reservierung für einen bestimmten Workspace oder ein Asset vorzunehmen.
- 3Bestehende Reservierungen ändernLass die AI die Details einer bereits geplanten Workspace-Buchung aktualisieren.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du Zoom Workspaces MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenZoom Workspaces MCP in Claude Code installieren
$ claude mcp add --transport http zoom-workspaces https://mcp.zoom.us/mcp/workspace/streamableZoom Workspaces MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"zoom-workspaces": {
"url": "https://mcp.zoom.us/mcp/workspace/streamable"
}
}
}Zoom Workspaces MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"zoom-workspaces": {
"type": "http",
"url": "https://mcp.zoom.us/mcp/workspace/streamable"
}
}
}Zoom Workspaces MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"zoom-workspaces","type":"http","url":"https://mcp.zoom.us/mcp/workspace/streamable"}'Zoom Workspaces MCP in Codex installieren
$ codex mcp add zoom-workspaces --url https://mcp.zoom.us/mcp/workspace/streamableZoom Workspaces MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.zoom-workspaces] url = "https://mcp.zoom.us/mcp/workspace/streamable"
Zoom Workspaces MCP in Gemini CLI installieren
$ gemini mcp add -s user --transport http zoom-workspaces https://mcp.zoom.us/mcp/workspace/streamableZoom Workspaces MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"zoom-workspaces": {
"url": "https://mcp.zoom.us/mcp/workspace/streamable",
"type": "http"
}
}
}Automatisierte Checks
Geluften am 14. Nov. 2026Vollständiger Bericht →Noch nicht verifiziert. Ein Server benötigt einen Score von 80, keine kritischen Befunde und genug Daten für unsere Prüfung. Wie die Checks funktionieren · Was du für mehr Punkte verbessern kannst
- Source Repository verknüpft und erreichbarzoom/mcp-registry is public and reachablegithub.com/zoom/mcp-registry ↗Bestanden
- Paket nennt dieses Repository als QuelleNicht geprüft
- Build-Provenienz (Sigstore-Attestierung)Nicht geprüft
- Open Source Lizenz (OSI)MITspdx.org/licenses/MIT.html ↗Bestanden
- Commit oder Release im letzten JahrLast commit or release 2026-11-13github.com/zoom/mcp-registry ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNicht geprüft
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenNicht geprüft
- Keine versteckten Anweisungen an das Modell0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNicht geprüft
- Remote-Endpoint beantwortet den MCP-HandshakeHTTPS endpoint answered 401 (sign-in required)Bestanden
README
Auf GitHub ansehenMCP Registry
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.
Registry Servers
io.github.zoom/zoom-workspace
- Registry metadata: zoom-workspace/server.json
- Remote URL:
https://mcp.zoom.us/mcp/zoom/streamable
Zoom 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-docs
- Registry metadata: zoom-docs/server.json
- Remote URL:
https://mcp.zoom.us/mcp/docs/streamable
Zoom 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-whiteboard
- Registry metadata: zoom-whiteboard/server.json
- Remote URL:
https://mcp.zoom.us/mcp/whiteboard/streamable
Zoom 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-accelerator
- Registry metadata: zoom-revenue-accelerator/server.json
- Remote URL:
https://mcp.zoom.us/mcp/revenue_accelerator/streamable
Zoom 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-chat
- Registry metadata: zoom-team-chat/server.json
- Remote URL:
https://mcp.zoom.us/mcp/chat/streamable
Zoom 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-meetings
- Registry metadata: zoom-meetings/server.json
- Remote URL:
https://mcp.zoom.us/mcp/meeting/streamable
Zoom 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-tasks
- Registry metadata: zoom-tasks/server.json
- Remote URL:
https://mcp.zoom.us/mcp/tasks/streamable
Zoom 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-admin
- Registry metadata: zoom-admin/server.json
- Remote URL:
https://mcp.zoom.us/mcp/admin/streamable
Zoom 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-canvas
- Registry metadata: zoom-canvas/server.json
- Remote URL:
https://mcp.zoom.us/mcp/canvas/streamable
Zoom 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-phone
- Registry metadata: zoom-phone/server.json
- Remote URL:
https://mcp.zoom.us/mcp/phone/streamable
Zoom 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-productivity
- Registry metadata: zoom-productivity/server.json
- Remote URL:
https://mcp.zoom.us/mcp/productivity/streamable
Zoom Productivity provides MCP tools for creating and managing Zoom Sheets content, including spreadsheets, sheets, and cell reads and edits.
io.github.zoom/zoom-rooms
- Registry metadata: zoom-rooms/server.json
- Remote URL:
https://mcp.zoom.us/mcp/rooms/streamable
Zoom 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-workflows
- Registry metadata: zoom-workflows/server.json
- Remote URL:
https://mcp.zoom.us/mcp/workflow/streamable
Zoom 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-workspaces
- Registry metadata: zoom-workspaces/server.json
- Remote URL:
https://mcp.zoom.us/mcp/workspace/streamable
Zoom 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.
Registry Notes
- Namespace:
io.github.zoom/* - Transport:
streamable-http - Current metadata versions in this repository:
1.0.2for Workspace, Docs, and Whiteboard;1.0.1for Revenue Accelerator, Team Chat, and Meetings;1.0.0for Tasks, Admin, Canvas, Phone, Productivity, Rooms, Workflows, and Workspaces
Registry API Records
- Search listing:
https://registry.modelcontextprotocol.io/v0.1/servers?search=zoom&limit=100 - Workspace latest version:
https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-workspace/versions/latest - Docs latest version:
https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-docs/versions/latest - Whiteboard latest version:
https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-whiteboard/versions/latest - Revenue Accelerator latest version:
https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-revenue-accelerator/versions/latest - Team Chat latest version:
https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-team-chat/versions/latest - Meetings latest version:
https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-meetings/versions/latest - Tasks latest version:
https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-tasks/versions/latest - Admin latest version:
https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-admin/versions/latest - Canvas latest version:
https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-canvas/versions/latest - Phone latest version:
https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-phone/versions/latest - Productivity latest version:
https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-productivity/versions/latest - Rooms latest version:
https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-rooms/versions/latest - Workflows latest version:
https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-workflows/versions/latest - Workspaces latest version:
https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-workspaces/versions/latest
Publishing Workflow
The 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.
Prerequisites
- Install
mcp-publisher - Authenticate with GitHub using an account that has access to the target GitHub organization
- Ensure the GitHub organization membership associated with the namespace is public
Publish With GitHub Actions (Recommended)
Publishing 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.
- It runs on pushes to
mainthat change anyzoom-*/server.json, and manually from the Actions tab (Run workflow, with an optionaldry_run). - It publishes only entries whose
name@versionis not already in the registry, so bumpversionin anyserver.jsonyou change. - It fails if a
descriptionis longer than 100 characters.
From the CLI: gh workflow run publish.yml -f dry_run=true (or false to publish), then gh run watch.
Publish A New Version Manually
-
Update the relevant
server.json. -
Increment the
versionfield 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
Maintenance
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.
Zoom Workspaces MCP Fragen
Wie füge ich Zoom Workspaces MCP zu Claude Code hinzu?
Führe claude mcp add --transport http zoom-workspaces https://mcp.zoom.us/mcp/workspace/streamable in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich Zoom Workspaces MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Was kann ich mit Zoom Workspaces machen?
Du kannst Workspaces, Standorte und Assets auflisten sowie die Reservierungsverwaltung übernehmen, einschließlich Erstellen, Aktualisieren oder Löschen von Reservierungen.
Ist Zoom Workspaces dasselbe wie der allgemeine Zoom MCP server?
Nein, es ist ein separater Server von io.github.zoom/zoom-workspace, der als allgemeiner Zoom MCP server dient.