Skip to main content
Glama
README.md
# Zoom API MCP Server

    A comprehensive Model Context Protocol (MCP) server for interacting with the Zoom API.

    ## Features

    - Complete coverage of Zoom API endpoints
    - OAuth 2.0 authentication
    - Structured tools with proper validation
    - API documentation resources
    - Error handling and response formatting

    ## Getting Started

    ### Prerequisites

    - Node.js 16+
    - Zoom API credentials (Client ID, Client Secret, Account ID)

    ### Installation

    1. Clone the repository
    2. Install dependencies:
       ```
       npm install
       ```
    3. Create a `.env` file with your Zoom API credentials:
       ```
       ZOOM_CLIENT_ID=your_client_id
       ZOOM_CLIENT_SECRET=your_client_secret
       ZOOM_ACCOUNT_ID=your_account_id
       ```

    ### Running the Server

    ```
    npm run dev
    ```

    ### Testing with MCP Inspector

    ```
    npm run inspect
    ```

    ## API Categories

    - **Meetings**: Create, read, update, and delete meetings
    - **Users**: Manage users in your Zoom account
    - **Webinars**: Create and manage webinars
    - **Account**: Manage account settings and profile
    - **Chat**: Manage Zoom Chat channels and messages
    - **Phone**: Manage Zoom Phone users and numbers
    - **Contacts**: Manage contacts
    - **Recordings**: Access and manage cloud recordings
    - **Reports**: Generate various reports
    - **Webhooks**: Set up event notifications
    - **Zoom Rooms**: Manage Zoom Rooms

    ## Resources

    Access API documentation through resources:

    ```
    zoom-api://overview
    zoom-api://meetings
    zoom-api://users
    ```

    ## Authentication

    The server handles OAuth 2.0 authentication automatically using the Server-to-Server OAuth app credentials.

TDQS

C2/5.0

Scored across 54 tools

Disambiguation5/5

Every tool has a clearly distinct purpose based on resource type and action. Tools are organized by resource (meeting, user, webinar, channel, etc.) and operation (create, get, list, update, delete), with no ambiguous overlaps. The consistent pattern makes it easy to distinguish between tools like get_meeting, list_meetings, and delete_meeting.

Naming Consistency5/5

All tools follow a consistent verb_noun naming pattern with snake_case throughout. Verbs (create, get, list, update, delete, send, search) are used predictably, and nouns clearly identify the resource type. There are no deviations in naming conventions across the entire set.

Tool Count2/5

With 54 tools, this is an extremely large set that feels heavy and overwhelming for a single server. While Zoom's API is comprehensive, this many tools suggests poor scoping or a direct mapping of API endpoints without consolidation, making it difficult for agents to navigate efficiently.

Completeness5/5

The tool set provides comprehensive CRUD/lifecycle coverage across all major Zoom resources (meetings, webinars, users, channels, webhooks, recordings, etc.). It includes create, get, list, update, and delete operations consistently, plus specialized actions like sending messages and generating reports, leaving no obvious gaps for the domain.

Maintenance

ActivityInactive
ResponsivenessNo issues