
MCP Server for Zoom (No Auth)
A MCP server for accessing Zoom recordings and transcripts without requiring direct authentication from the end user.
What is MCP Server for Zoom (No Auth)?
MCP Server for Zoom (No Auth) is a Model Control Protocol server that allows users to access Zoom recordings and transcripts without requiring direct authentication from the end user. It simplifies the interaction with the Zoom API by managing OAuth flows internally.
How to use MCP Server for Zoom (No Auth)?
To use the MCP Server, clone the repository, install the required dependencies, and start the server. You can then use various tools provided by the server to interact with Zoom recordings and transcripts.
Key features of MCP Server for Zoom (No Auth)?
- 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
Use cases of MCP Server for Zoom (No Auth)?
- Accessing and managing Zoom cloud recordings without user authentication.
- Automating the retrieval of meeting transcripts for analysis.
- Integrating Zoom recording functionalities into other applications without user intervention.
FAQ from MCP Server for Zoom (No Auth)?
- Do I need to authenticate to use this server?
No, this server is designed to operate without requiring direct user authentication.
- How do I obtain OAuth credentials?
You need to create a Zoom OAuth app in the Zoom Marketplace and configure the required scopes for recordings access.
- Can I run this server in a headless environment?
Yes, the server is designed to run in a headless environment without storing any credentials.
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:
git clone https://github.com/peakmojo/mcp-server-zoom-noauth.git
cd mcp-server-zoom-noauth
- Install the required dependencies:
pip install -r requirements.txt
Docker
Building the Docker Image
# Build the Docker image
docker build -t mcp-server-zoom-noauth .
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):
docker buildx create --use
- Build and push the image for multiple platforms:
docker buildx build --platform linux/amd64,linux/arm64 -t buryhuang/mcp-server-zoom-noauth:latest --push .
- Verify the image is available for the specified platforms:
docker buildx imagetools inspect buryhuang/mcp-server-zoom-noauth:latest
Usage
Starting the server
python -m src.mcp_server_zoom_noauth.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
{
"zoom_refresh_token": "your_refresh_token",
"zoom_client_id": "your_client_id",
"zoom_client_secret": "your_client_secret"
}
Listing recordings
{
"zoom_access_token": "your_access_token",
"from_date": "2023-01-01",
"to_date": "2023-01-31",
"page_size": 30,
"page_number": 1
}
Getting recording details
{
"zoom_access_token": "your_access_token",
"meeting_id": "meeting_id_here"
}
Getting meeting transcript
{
"zoom_access_token": "your_access_token",
"meeting_id": "meeting_id_here"
}
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.