> ## Documentation Index
> Fetch the complete documentation index at: https://docs.peacock.support/llms.txt
> Use this file to discover all available pages before exploring further.

# What is Zoom MCP Server? Features and how it works

> Zoom MCP Server bridges Claude Desktop and the Zoom API, letting you manage meetings, users, and recordings with natural language commands.

Zoom MCP Server is a [Model Context Protocol (MCP)](https://modelcontextprotocol.io) server that bridges Claude Desktop and the Zoom API. Instead of navigating the Zoom UI to schedule, update, or review meetings, you type a plain English request in Claude and the server handles the API call on your behalf. The server runs locally on your machine, communicates with Claude Desktop over stdio, and sends authenticated requests directly to the Zoom REST API.

## What you can do

Zoom MCP Server exposes nine tools across three categories: meeting management, user management, and recordings. Each tool maps to a Zoom API operation and is called automatically by Claude when it interprets your request.

<CardGroup cols={2}>
  <Card title="Meeting management" icon="calendar">
    Create, view, update, and delete meetings. List scheduled, live, upcoming, or previous meetings. Manage recurring occurrences individually.

    Tools: `list_meetings`, `get_meeting`, `create_meeting`, `update_meeting`, `delete_meeting`
  </Card>

  <Card title="User management" icon="users">
    List users in your Zoom account by status, or fetch profile details for a specific user by ID or email address.

    Tools: `list_users`, `get_user`
  </Card>

  <Card title="Participants" icon="person-chalkboard">
    Retrieve the participant list for any past meeting by meeting ID.

    Tool: `get_meeting_participants`
  </Card>

  <Card title="Recordings" icon="video">
    Access cloud recordings for a meeting by its ID or UUID.

    Tool: `get_meeting_recordings`
  </Card>
</CardGroup>

## How it fits together

When you send a message to Claude, Claude Desktop uses the MCP protocol to call the appropriate tool in the server. The server reads your Zoom access token from the local `.env` file, makes the corresponding API request to `https://api.zoom.us/v2`, and returns the result to Claude. Claude then formats and presents the data to you in plain language.

The server also monitors your access token while it runs. It displays expiration status every 60 seconds and automatically refreshes the token when it is within 5 minutes of expiring, so your session stays active without any manual intervention.

<Note>
  All API calls are made directly from your machine to Zoom. Your credentials are stored locally in a `.env` file and are never transmitted anywhere other than the Zoom API.
</Note>

## Next steps

Ready to get set up? Start with the prerequisites, then follow the quickstart to have the server running in a few minutes.

<CardGroup cols={2}>
  <Card title="Prerequisites" icon="list-check" href="/prerequisites">
    Check what you need before you begin: Node.js, a Zoom OAuth app, and Claude Desktop.
  </Card>

  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Step-by-step instructions to clone, configure, and start the server.
  </Card>
</CardGroup>