Zoom MCP Server
Generate zoom invitation links, search meeting summaries, and retrieve participant details under AI instructions.
Quick Answer / TL;DR
The Zoom MCP server establishes a secure, local or remote JSON-RPC 2.0 communication tunnel, allowing AI models (like Claude or Cursor) to automatically discover and execute capabilities (tools, prompts, and resources) within the Zoom ecosystem with extremely low latency.
Key Takeaways
- Automate webinar schedules
- Extract meeting audio transcripts
- Manage attendance records
Core Integration Concept
Connecting the model to Zoom bypasses complex setup. The LLM can auto-discover what endpoints are active, what input variables are expected, and how answers will be delivered.
Verified Use Cases
Setup Overview
Connection Setup Checklist
- Prepare Credentials: Obtain your Zoom Server-to-Server OAuth credentials directly from your Zoom settings.
- Update Config: Add the executable tool command structure directly to your Claude config file.
- Restart & Confirm: Reload the desktop model client to complete the connection handshake sequence.
Sample Connection Schema
{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "execute_zoom",
"arguments": {
"query": "status_check"
}
},
"id": 1
}Security Considerations
To guarantee perfect data isolation, safeguard the Zoom Server-to-Server OAuth credentials. Always run integrations in sandboxed contexts to block unsolicited access.
Best Practices
- Configure exact resource boundaries for the Meeting creation feature.
- Configure exact resource boundaries for the Invite link generation feature.
- Configure exact resource boundaries for the Transcript search feature.
- Configure exact resource boundaries for the Registrant tracking feature.
Required Auth Keys
Zoom Server-to-Server OAuth
Deploy Zoom Server
Deploy this Zoom integration to our global edge container cluster. Zero DevOps, instant SSE.
Related Connectors
Zoom - FAQ
Contextual information and technical support details regarding Model Context Protocol integration