Zoom

@zoom list all meetings scheduled for this week and show me which ones have recordings enabled

Here are your scheduled Zoom meetings for this week: • Monday 2PM: Product Roadmap Review (45 min) — cloud recording enabled • Wednesday 10AM: Design Critique (60 min) — no recording • Thursday 3PM: Sprint Planning (90 min) — cloud recording enabled • Friday 11AM: All-Hands (30 min) — no recording Two of four meetings have cloud recording turned on. The Product Roadmap and Sprint Planning sessions will be automatically saved to your Zoom cloud storage.

This example uses the 'Get a meeting' tool to fetch meeting metadata. Requires `meeting:read` scope. Note that the MCP returns meeting configuration details but cannot access the actual recording files themselves — you'd need `recording:read` scope and a separate tool call to download or share recordings after the meeting ends.

@zoom create a 60-minute meeting tomorrow at 2pm called 'Q1 Budget Review' and enable the waiting room

Meeting created successfully: **Q1 Budget Review** Time: Tomorrow, 2:00 PM (60 minutes) Meeting ID: 123-456-7890 Join URL: https://zoom.us/j/1234567890 Waiting room: Enabled Your host start URL has been generated and will expire in 2 hours. If you need to regenerate it closer to the meeting time, use the API or Zoom dashboard. This meeting is now visible in your Zoom calendar.

This example demonstrates the 'Create a meeting' tool, which requires `meeting:write` scope. The start URL expires quickly (2 hours for standard users, 90 days for 'custcreate' accounts). Be aware of the 100 requests/day rate limit on meeting creation — if your team schedules meetings programmatically at scale, you may hit this cap.

@zoom pull the meeting summary from yesterday's sprint retro and draft a follow-up email highlighting action items

Meeting summary retrieved from 'Sprint Retro - March 14': **Key Discussion Points:** • Deployment pipeline delays (15 min) • Testing coverage gaps in auth module (10 min) • Positive feedback on new design system adoption (8 min) **Action Items Identified:** 1. DevOps to audit CI/CD config by Friday 2. QA to add integration tests for OAuth flows 3. Design team to present component library at next all-hands **Draft Email:** Subject: Action Items from 3/14 Sprint Retro Team — thanks for a productive retro yesterday. Here's what we committed to: [action items listed]. Let's sync on progress in Monday's standup.

This example chains the 'Get a meeting summary' tool (which requires AI Companion enabled and a Pro+ plan) with the AI's synthesis capability. The summary feature excludes end-to-end encrypted meetings and won't work for Basic plan hosts. Rate limit is 'light', but the AI Companion requirement is a hard dependency — confirm your Zoom account tier before relying on this workflow.

When Zoom MCP makes sense for meeting ops at scale

A 15-person remote startup runs a weekly all-hands on Zoom and wants an AI agent to auto-archive recordings to their knowledge base after each session. The Zoom MCP is the right call here: OAuth2 keeps credentials out of chat logs, and the 'Delete meeting recordings' and 'Get a meeting' tools let the agent fetch the MP4, transcribe it, then purge the cloud copy to stay under storage limits. The trade-off is the 100-requests-per-day cap on meeting creation—if your team spins up 20+ ad-hoc Zooms daily, you'll hit that ceiling fast. For a predictable cadence of 5-10 meetings a week, this MCP turns recording hygiene into a one-click Switchy routine.

Webinar MCP tooling works until you cross 1,000 registrants per event

A B2B SaaS marketing team runs monthly product webinars and wants an AI agent to pull registrant lists, cross-reference them with CRM data, and flag VIP attendees for follow-up. The Zoom MCP's 'Add a webinar registrant' and 'Get a webinar' tools handle this cleanly—OAuth2 means the agent can act on behalf of the host without hardcoding API keys. The 4,999-registrant ceiling is generous for most mid-market plays, but if you're running mega-webinars (think 5k+ sign-ups), you'll need a direct API integration outside Switchy. For teams doing 200-800 registrants per event, this MCP turns post-webinar triage into a 10-minute Switchy workflow instead of a spreadsheet nightmare.

Daily usage reports are overkill unless you bill by seat activity

A 30-seat agency wants to audit which clients are actually showing up to Zoom strategy calls, so they can flag at-risk accounts before renewal season. The Zoom MCP's 'Get daily usage report' tool surfaces new users, meeting counts, and participant minutes—but it's rate-limited as 'heavy', meaning you can't hammer it in a loop. This scenario is borderline: if you're running the audit once a month, the MCP is fine. If you need real-time seat utilization (say, you bill clients per active user), the heavy rate limit will bottleneck your agent. For quarterly check-ins or one-off forensics, the Zoom MCP gives your Switchy workspace enough visibility to catch usage red flags without building a custom dashboard.