Connect Zoom to Claude Code

Schedule and manage Zoom meetings, and read recordings, participants and users. Add Toolspoke to Claude Code once and it can use 10 Zoom actions. Your Zoom credential stays in Toolspoke, and you choose which actions Claude Code may call.

Set it up in Claude Code

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to Claude Code

    Run it in your project, then /mcp to sign in

    claude mcp add --transport http toolspoke https://toolspoke.com/mcp

    The sign-in opens in your browser, and Toolspoke asks you to approve it.

  2. Install Zoom and connect it

    Add Zoom to a project in your Toolspoke workspace.

    Server-to-server OAuth. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

    Account ID
    Zoom App Marketplace → Develop → Build App → Server-to-Server OAuth → your app → App Credentials. It names the Zoom account the token is minted for.
    Client ID
    Shown beside the Account ID on the app's App Credentials page.
    Client secret
    App Credentials → Client Secret. Add the scopes separately under the app's Scopes tab: user:read:admin covers the user reads, meeting:read:admin and meeting:write:admin the meetings, recording:read:admin the recordings.
  3. Choose what Claude Code may do

    All 10 actions start on. Switch off any of the 3 actions that change something in Zoom, and Claude Code gets a refusal if it tries.

What you can ask Claude Code for

A few of the Zoom actions that only read, so they are safe to try first.

  • List the users on the Zoom account, with each one's id, email, name, type and status
  • Fetch one user's record: id, email, display name, licence type, personal meeting id, timezone and department
  • List one host's meetings
  • List one host's cloud recordings

What Claude Code can do in Zoom

7 actions read, 2 write and one deletes or permanently changes something.

Reads

  • List users

    List the users on the Zoom account, with each one's id, email, name, type and status. Call it first when you do not know which host to act on, and to find out whether the connection reaches anything at all, a failure here usually means the app is missing the user:read:admin scope rather than that the credentials are wrong. Only active users are returned unless status says otherwise. Page with next_page_token, which expires after fifteen minutes.

  • Get user

    Fetch one user's record: id, email, display name, licence type, personal meeting id, timezone and department. Use it to resolve an email address to the user id that the meeting operations take, or to confirm what licence a host has before scheduling something their plan does not allow.

  • List meetings

    List one host's meetings. `type` decides which: scheduled (the default) returns unexpired past, live and upcoming scheduled meetings, live returns only what is running now, upcoming returns future meetings including live ones, and previous_meetings returns meetings whose end time has passed. Two limits are Zoom's rather than this connector's: instant meetings never appear here at all, and upcoming, upcoming_meetings and previous_meetings return at most six months of data. The `id` returned is what get_meeting, update_meeting and delete_meeting take.

  • Get meeting

    Fetch one meeting in full: topic, agenda, start time, duration, timezone, join URL, passcode, recurrence and every setting. IMPORTANT: a Zoom meeting id can be more than ten digits, so pass it as a string here, a numeric id truncated by a caller's own integer handling addresses a different meeting or none at all. Use occurrence_id to read a single occurrence of a recurring meeting.

  • List recordings

    List one host's cloud recordings. IMPORTANT: the from/to window can span at most one month, and Zoom does not tell you when you ask for more, it silently answers with a shorter range. Leaving both out means today and tomorrow, not everything, which is the other half of the same surprise. Trashed recordings are a separate listing reached with trash, and Zoom ignores from and to entirely for those. Requires a Pro plan or higher and the recording:read:admin scope. The array comes back under `meetings`, each with its recording_files.

  • Get recording

    Fetch the recording files for one meeting: video, audio, chat, transcript and closed captions, each with its size, type and Zoom download URL. This connector returns the URLs and never downloads the media itself. `meeting_id` accepts a meeting id, which returns the latest instance, or a meeting UUID, which returns exactly that one, and a UUID that starts with a slash or contains a double slash must be double URL-encoded before it is passed here, which is Zoom's own requirement rather than this connector's. Set include_fields to download_access_token when the URLs need to be usable without a Zoom session, and ttl to say for how many seconds, up to 604800.

  • List past participants

    List who attended a meeting that has already finished, with each person's name, email, join and leave times and duration. `meeting_id` takes a meeting id, which reports on the latest instance, or a meeting UUID for one specific instance, and a UUID beginning with a slash or containing a double slash must be double URL-encoded, which is Zoom's own requirement. Requires a Pro plan or higher, and Zoom keeps this data for fifteen months. A meeting with only one participant is omitted entirely unless the account has the "Show one person meetings and webinars on Dashboard and Reports" setting enabled, which is the usual reason this comes back empty for a meeting that certainly happened.

Writes

  • Create meeting

    Schedule a meeting for one host. Zoom rate-limits this to 100 meetings per day per host. `start_time` is either yyyy-MM-ddTHH:mm:ssZ in GMT, or yyyy-MM-ddTHH:mm:ss alongside a `timezone`. `type` defaults to 2, a plain scheduled meeting; pass 8 with the recurrence arguments for a recurring meeting at a fixed time, and note that Zoom rejects recurrence on any other type. Waiting room and join-before-host contradict each other, turning the waiting room on disables join-before-host, whatever this call says. Returns the meeting including its id, join URL and passcode.

  • Update meeting

    Change an existing meeting: retime it, rename it, rewrite the agenda or change its settings. Pass only what you want changed; everything omitted is left alone. A write rather than a destructive act, the change is as reversible as making it, but note that moving a meeting is visible to everyone holding the invitation. Zoom answers 204 with no body, so read the result back with get_meeting if you need to confirm it. Naming an occurrence_id restricts the edit to one instance of a recurring meeting, and Zoom then accepts only agenda, start_time, duration and a handful of settings.

Deletes or permanently changes

  • Delete meeting

    Delete a meeting. There is no Zoom API that restores one: the join link stops working for everyone holding it, and any registration attached to it goes with it. That is why this is classified destructive and cannot be reached by a read-only or write grant. Both notification flags default to false, so nobody is mailed unless the caller asks, set cancel_meeting_reminder to notify registrants that the meeting is off, and schedule_for_reminder to notify the host and any alternative hosts. Pass occurrence_id to cancel a single occurrence rather than the whole series. Zoom answers 204 with no body.

Zoom in Claude Code: questions

Does Claude Code see my Zoom credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Can I stop Claude Code from changing things in Zoom?

Yes. Each of the 10 actions can be switched off for a project. Turn off the 3 that change something and Claude Code can only read.

Will 10 actions crowd Claude Code's context?

No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Zoom action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Can I add it once for every project?

Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.

What does it cost?

Tool calls are free on every plan, and a Zoom call does not run in a sandbox, so it bills nothing.

Try Zoom in Claude Code

Free to start, and tool calls cost nothing on any plan.