io.github.zoom/zoom-workspaces
Zoom Workspaces MCP Server
Is the Zoom Workspaces MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-13.
Zoom Workspaces server for workspace reservations, locations, assets, and calendar events.
needs auth probed 2026-11-14 · unchanged since 2026-11-13 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":{"code":-32003,"message":"Access token is required"},"id":0,"jsonrpc":"2.0"}- Endpoint
- https://mcp.zoom.us/mcp/workspace/streamable (streamable-http)
- Host
- mcp.zoom.us
- Getting access
- OAuth without dynamic client registration. Ask the publisher for a client id first; with it, a client can run the consent.
Authorization server zoom.us, PKCE S256, grants authorization_code, refresh_token, client_credentials, urn:ietf:params:oauth:grant-type:jwt-bearer.
Scopes workspace:write:reservation workspace:update:reservation workspace:read:meeting workspace:read:workspace workspace:delete:reservation workspace:read:list_workspaces workspace:read:list_reservations workspace:read:asset zoom_rooms:read:list_locations workspace:read:contacts.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/zoom/mcp-registry
- Website
- https://developers.zoom.us/docs/mcp/zoom-workspaces-mcp-server/
- Registry
- active, updated 2026-11-13 · registry entry
Compare this server with others.
More servers
Other registry entries on mcp.zoom.us.
- io.github.zoom/zoom-team-chat · needs auth
- io.github.zoom/zoom-whiteboard · needs auth
- Zoom Workflows MCP Server io.github.zoom/zoom-workflows · needs auth
- io.github.zoom/zoom-workspace · needs auth
Servers that mention workspaces.
- Filepad ai.filepad/filepad · server error
- ai.plori/plori · needs auth
- Kanera app.kanera/mcp · needs auth
- Priorify app.priorify/priorify · needs auth
- ai.smithery/smithery-ai-slack · not found
- Trilo chat.trilo/mcp · needs auth
- AcornReply com.acornreply/server · needs auth
- agent-talk com.basenull/agent-talk · needs your URL
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.