remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
Integrations
Enables access to Zoom API functionality without requiring direct user authentication, providing tools to list cloud recordings, get detailed recording information, and access meeting transcripts.
MCP Server for Zoom (No Auth)
This project is a Model Control Protocol (MCP) server for accessing Zoom API functionality without requiring direct authentication from the end user. It handles the OAuth flows and provides a set of tools for interacting with Zoom recordings and transcripts.
Features
- OAuth credential management through tool arguments (no local auth flow)
- List user's cloud recordings with pagination
- Get detailed information about specific meeting recordings
- Access meeting transcripts
Installation
- Clone the repository:
- Install the required dependencies:
Docker
Building the Docker Image
Cross-Platform Publishing
To publish the Docker image for multiple platforms, you can use the docker buildx command:
- Create a new builder instance (if you haven't already):
- Build and push the image for multiple platforms:
- Verify the image is available for the specified platforms:
Usage
Starting the server
Available Tools
The server provides the following tools:
- zoom_refresh_token - Refresh an OAuth token using a refresh token
- zoom_list_recordings - Get a list of user's cloud recordings
- zoom_get_recording_details - Get detailed information about a specific meeting recording
- zoom_get_meeting_transcript - Get transcript for a specific meeting recording
Tool Usage Examples
Refreshing a token
Listing recordings
Getting recording details
Getting meeting transcript
OAuth Credential Handling
This server is designed to be completely "noauth" from its perspective:
- No local authentication flow is needed
- No credentials are stored on the server
- All credentials are passed through tool arguments
- The server can run in a headless environment
To use the tools, you'll need to obtain OAuth credentials from Zoom:
- Create a Zoom OAuth app in the Zoom Marketplace
- Configure the required scopes for recordings access
- Obtain access and refresh tokens through the OAuth flow
- Pass these tokens as arguments when calling the tools
Zoom API Reference
This project uses the Zoom API v2. For more information, refer to the Zoom API documentation.
License
You must be authenticated.
A MCP server for accessing Zoom recordings and transcripts without requiring direct authentication from the end user.