Cursor plugin that connects agents to Zoom through Zoom's official hosted Model Context Protocol servers.
Search meetings and recordings, pull summaries and transcripts, and work with Zoom Docs from chat.
- Open Cursor Settings → Plugins.
- Search for Zoom.
- Click Install, then set the Client ID and the Client Secret it requires, or a Public Client ID (below), and complete the Zoom sign-in prompt.
Or run /add-plugin zoom in chat.
{
"mcpServers": {
"zoom": {
"type": "http",
"url": "https://mcp.zoom.us/mcp/zoom/streamable",
"auth": {
"CLIENT_ID": "${CLIENT_ID}",
"CLIENT_SECRET": "${CLIENT_SECRET:-}"
}
}
}
}Zoom's MCP servers only support manual client registration — Dynamic Client Registration and Client ID Metadata Documents are not accepted — so an administrator has to register Cursor as a Zoom app before anyone can connect.
- A Zoom admin or developer logs into the Zoom App Marketplace and creates a General app under Develop → Build app.
- Add the scopes listed for each tool in Zoom's MCP server docs. Meeting search and recordings need
ai_companion:read:searchfor cross-Zoom search. - Under Basic Information → OAuth Information, register both redirect URIs:
- Desktop:
http://127.0.0.1:8787/callback - Web and Cloud Agents:
https://www.cursor.com/agents/mcp/oauth/callback
- Desktop:
- Under Basic Information → App Credentials, copy the Client ID and Client Secret. A Client Secret is required along with the Client ID. To sign in without a secret instead, turn on Use Public Client OAuth and copy the Public Client ID.
- In Dashboard → Plugins → Configure, set Zoom Client ID or Public Client ID and Zoom Client Secret to the values you copied. Leave the secret blank only with the Public Client ID.
- Complete the Zoom OAuth login when Cursor prompts.
If you regenerate the Client Secret in Zoom, enter the new one in Cursor too. Desktop sign-ins through the loopback redirect need the Public Client ID: Zoom accepts http://127.0.0.1:8787/callback only for a public client, and rejects localhost outright.
Each member needs a license for the Zoom products they want to reach. On a team marketplace an admin sets the credentials once for everyone; each member still completes their own Zoom OAuth login, so tool calls run with that member's Zoom permissions.
Zoom splits tools across product-specific servers. This plugin ships the main zoom server, which covers meeting search, cross-Zoom search, recordings, summaries, meeting assets, and the main-server Zoom Docs tools. To reach the others, add them to mcp.json with the same auth block:
| Server | URL |
|---|---|
| Zoom Docs | https://mcp.zoom.us/mcp/docs/streamable |
| Whiteboard | https://mcp.zoom.us/mcp/whiteboard/streamable |
| Team Chat | https://mcp.zoom.us/mcp/team_chat/streamable |
Zoom also exposes SSE variants at the same paths with /sse instead of /streamable.
- Zoom MCP overview: https://developers.zoom.us/docs/mcp/servers/
- Connecting MCP clients: https://developers.zoom.us/docs/mcp/servers/connect-to-zoom-mcp-servers/
MIT