Zoom Workspace MCP Server

Zoom hosts its own remote MCP server at mcp.zoom.us, so there is nothing to install and no local process to babysit — you point an MCP client at a streamable HTTP endpoint, authorise it against your Zoom account, and the assistant can reach the meeting history you already have.

The Workspace server is the unified one. Its verified tool set covers search_meetings for semantic search over meeting content rather than titles, search_zoom for cross-product search across Team Chat messages, Zoom Canvas and My Notes, get_meeting_assets and get_recording_resource for pulling the transcript, AI Companion summary and recording tied to a specific meeting, recordings_list for browsing cloud recordings, plus create_new_file_with_markdown, get_file_content, hub_create_file_from_content and hub_get_file_content for reading and writing Canvas and Zoom Hub documents.

Zoom also publishes narrower servers on the same host if you would rather scope access tightly: Meetings (/mcp/meeting/streamable), Team Chat (/mcp/chat/streamable), Docs/Canvas (/mcp/docs/streamable), Tasks (/mcp/tasks/streamable), Whiteboard (/mcp/whiteboard/streamable) and Revenue Accelerator (/mcp/revenue_accelerator/streamable).

Setup is not one-click. Authentication is user-level OAuth 2.0 with PKCE, and the token has to come from a General (user-managed) app you create in the Zoom App Marketplace — grant it only the scopes the tools you plan to call actually need, then point your client at the endpoint with a bearer token. Individual tools and product areas carry their own Zoom licence requirements, so a tool can appear in tools/list and still refuse to run on a plan that does not include the underlying product.

Worth it for the obvious reason: meeting transcripts and summaries are where a lot of a company's decisions actually live, and this is the supported way to let an agent read them.