Productivity · Remote MCP server
Zoom Workspace
Zoom workspace server for meetings, chat, docs, recordings, and AI-generated collaboration content.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.zoom/zoom-workspace- Version
- 1.0.2
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-05-19
- Updated
- 2026-05-19
- Publisher
- zoom (GitHub) · 7 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/zoom) · how
- Listed under
- Zoom MCP servers
- Repository
- github.com/zoom/mcp-registry
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.zoom.us/mcp/zoom/streamable | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Zoom Workspace
Zoom Workspace is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.zoom.us/mcp/zoom/streamable, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from zoom (GitHub)
| Server | Runs |
|---|---|
| Zoom DocsZoom Docs server for creating and retrieving Zoom documents and notes in Markdown. | Remote · HTTPLive check: sign-in required |
| Zoom MeetingsZoom Meetings server for meeting search, recordings, transcripts, summaries, and meeting assets. | Remote · HTTPLive check: sign-in required |
| Zoom Revenue AcceleratorZoom Revenue Accelerator server for sales insights, conversations, and deal intelligence. | Remote · HTTPLive check: sign-in required |
| Zoom TasksZoom Tasks server for creating, updating, assigning, and synchronizing task workflows. | Remote · HTTPLive check: sign-in required |
| Zoom Team ChatZoom Chat server for channels, messages, contacts, files, and chat collaboration. | Remote · HTTPLive check: sign-in required |
| Zoom WhiteboardZoom Whiteboard server for creating boards and diagrams and locating existing boards. | Remote · HTTPLive check: sign-in required |
More productivity servers
| Server | Runs |
|---|---|
| ZOOQ - LinkedIn Data for AI AgentsLive LinkedIn data for AI agents: profiles, companies, jobs, posts, email finding. No account risk. | Remote · HTTPLive check: ✓ handshake |
| Zooza MCP ServerMCP server for Zooza - class scheduling, attendance, and booking for activity businesses. | Remote · HTTPLive check: ✓ handshake |
| Zotero BridgeMCP Server for Zotero SQLite Database - collection, tagging, PDF reading and more. | Local · stdio |
| ZsignE-signature API for AI agents: send contracts, sign PDF documents, track and download signed files. | Remote · HTTPLive check: sign-in required |