Zoom MCP Server
Deploy and configure the Zoom MCP server with authentication, use cases, security notes, and India-ready hosting guidance.
Quick Answer / TL;DR
The Zoom MCP server exposes Zoom capabilities to AI clients through scoped tools, resources, and JSON-RPC calls, using Zoom Server-to-Server OAuth for authentication.
Key Takeaways
- Authentication: Zoom Server-to-Server OAuth.
- Category: Productivity.
- Best first use case: Automate webinar schedules.
- Use environment variables and least-privilege scopes for production.
Integration overview
Generate zoom invitation links, search meeting summaries, and retrieve participant details under AI instructions.
Use this connector when an AI assistant such as Claude, Cursor, or a custom agent needs a governed path into Zoom. Keep the server focused on the approved workflows instead of exposing a whole account or admin surface.
For Indian teams, deploy the connector near the users and the data source, then add request IDs, redaction, and audit logs before connecting production data.
| Field | Value |
|---|---|
| Connector | Zoom MCP Server |
| Category | Productivity |
| Authentication | Zoom Server-to-Server OAuth |
| Production route | /servers/zoom-mcp-server/ |
Features and use cases
Zoom is most useful when the agent has a narrow job to complete and the server can validate every argument before execution.
Start with read-only or low-risk tools. Add write operations only after approval prompts, scoped credentials, and logging are working.
| Capability | Recommended guardrail |
|---|---|
| Meeting creation | Allow with scoped read access |
| Invite link generation | Allow with scoped read access |
| Transcript search | Allow with scoped read access |
| Registrant tracking | Allow with scoped read access |
Local and hosted configuration
Configure Zoom with credentials stored in environment variables. Do not hardcode tokens in prompts, repositories, screenshots, or browser-visible code.
The local configuration pattern works for a single developer. Hosted deployments should add TLS, bearer-token authentication, health checks, and monitoring.
{
"mcpServers": {
"zoom": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-zoom"],
"env": {
"ZOOM_TOKEN": "${ZOOM_TOKEN}"
}
}
}
}Security and permissions
Protect Zoom Server-to-Server OAuth credentials with least privilege, rotation, and separate environments for development, staging, and production.
Review every tool output for sensitive data before letting it enter model context. For regulated Indian workflows, add DPDP-aware redaction and retention controls.
{
"server": "zoom-mcp-server",
"auth": "Zoom Server-to-Server OAuth",
"policy": {
"leastPrivilege": true,
"redactSecrets": true,
"requireApprovalForWrites": true,
"auditToolCalls": true
}
}Zoom MCP Server FAQs
Direct answers for developers, operators, and Indian teams evaluating MCP.