Zoom MCP Server
Enables intelligent monitoring and management of Zoom rooms, allowing users to query room status, resolve hierarchical locations, and retrieve detailed room configurations across multiple sites.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Zoom MCP Server list all offline Zoom rooms in the DEN1 building"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Zoom MCP Server
A FastMCP Model Context Protocol server that provides intelligent monitoring and management of Zoom rooms across multiple sites with smart location resolution.
๐ Features (New!)
5 Powerful Tools for comprehensive Zoom room management
Smart Location Resolution with fuzzy matching (e.g., "SF1", "DEN1", "Floor 3")
Denver Building Aliases - Special hardcoded mappings for room naming compatibility
Efficient API Usage - Single call for company-wide queries vs. multiple location-specific calls
OAuth 2.0 Authentication with automatic token refresh and file-based caching
Hierarchical Location Discovery - Understands campus โ building โ floor relationships
User-Friendly Confirmations - Clear messages explaining what was resolved
Related MCP server: Zoom API MCP Server
๐ ๏ธ Tools Available
test_zoom_connection
Test Zoom API authentication and connection status.
# Usage: Verify credentials are working
mcp call test_zoom_connection --params '{}' uv run src/server.pyget_zoom_sites
Get all Zoom locations with hierarchy and aliases.
# Usage: Understand available locations and relationships
mcp call get_zoom_sites --params '{}' uv run src/server.pyget_zoom_rooms
Get Zoom rooms with optional smart location filtering.
โก IMPORTANT: For maximum efficiency with company-wide queries (e.g., "find offline rooms anywhere"), omit location_query to make a single API call.
# Company-wide (EFFICIENT - single API call)
mcp call get_zoom_rooms --params '{}' uv run src/server.py
# Location-specific (multiple API calls)
mcp call get_zoom_rooms --params '{"location_query":"SF1"}' uv run src/server.py
mcp call get_zoom_rooms --params '{"location_query":"DEN1"}' uv run src/server.py
mcp call get_zoom_rooms --params '{"location_query":"Floor 3"}' uv run src/server.pyget_room_details
Get detailed information about a specific room.
# Usage: Deep dive into specific room configuration
mcp call get_room_details --params '{"room_id":"ROOM_ID_HERE"}' uv run src/server.pyresolve_location
Debug tool to test location resolution without fetching rooms.
# Usage: Debug how location queries get resolved
mcp call resolve_location --params '{"location_query":"DEN2"}' uv run src/server.py๐ Smart Location Resolution
The server understands various location query patterns:
Query Pattern | Example | What It Resolves |
Campus codes |
| Entire campus with all buildings/floors |
Building numbers |
| Specific building or hardcoded alias |
Floor numbers |
| All floors with that number across sites |
Partial names |
| Best fuzzy match |
Special Denver Building Aliases
Due to Zoom's location hierarchy vs. room naming patterns, Denver has special hardcoded mappings:
DEN1โ Denver Building 1 (Floor 3) โ Rooms:DEN-1-101,DEN-1-102, etc.DEN2โ Denver Building 2 (T3F3, T3F5, T3F6) โ Rooms:DEN-2-201,DEN-2-202, etc.
๐ง Installation & Setup
Prerequisites
Python 3.10+
UV package manager
Zoom Pro/Business account with API access
1. Clone Repository
git clone https://github.com/chadkunsman/zoom-mcp.git
cd zoom-mcp2. Install Dependencies
uv pip install -e .3. Zoom API Configuration
Create a Server-to-Server OAuth app in Zoom Marketplace
Add required scope:
room:read:adminGet your credentials: Account ID, Client ID, Client Secret
4. Configure Credentials
Create .env file:
ZOOM_ACCOUNT_ID=your_account_id_here
ZOOM_CLIENT_ID=your_client_id_here
ZOOM_CLIENT_SECRET=your_client_secret_here5. Test Installation
# Install MCPTools for testing
brew tap f/mcptools && brew install mcp
# Test the server
mcp tools uv run src/server.py
mcp call test_zoom_connection --params '{}' uv run src/server.py๐ MCP Client Configuration
For Claude Desktop and Similar MCP Clients
Add to your MCP client configuration:
Using Environment Variables (Recommended)
{
"mcpServers": {
"zoom-mcp": {
"command": "uv",
"args": [
"run",
"--directory",
"/path/to/zoom-mcp",
"src/server.py"
],
"env": {
"ZOOM_ACCOUNT_ID": "your_account_id_here",
"ZOOM_CLIENT_ID": "your_client_id_here",
"ZOOM_CLIENT_SECRET": "your_client_secret_here"
}
}
}
}Using Command-Line Arguments
{
"mcpServers": {
"zoom-mcp": {
"command": "uv",
"args": [
"run",
"--directory",
"/path/to/zoom-mcp",
"src/server.py",
"--zoom-account-id",
"your_account_id_here",
"--zoom-client-id",
"your_client_id_here",
"--zoom-client-secret",
"your_client_secret_here"
]
}
}
}๐ก Usage Examples
Find All Offline Rooms (Efficient)
"Are any Zoom rooms offline anywhere in the company?"
โ Uses get_zoom_rooms without location_query (single API call)
Check Specific Location
"Show me all rooms in San Francisco"
โ Uses get_zoom_rooms with location_query: "SF1"
Debug Location Resolution
"How would 'DEN2' be resolved?"
โ Uses resolve_location to see what locations match
Room Status by Building
"What's the status of Denver Building 1 rooms?"
โ Uses get_zoom_rooms with location_query: "DEN1"
๐๏ธ Architecture
zoom-mcp/
โโโ src/
โ โโโ server.py # Main MCP server with 5 tools
โ โโโ config/ # Configuration modules
โ โโโ settings.py # Environment & auth configuration
โ โโโ zoom_auth.py # OAuth token management
โ โโโ zoom_hierarchy.py # Location discovery & relationships
โ โโโ zoom_fuzzy.py # Smart location resolution
โโโ docs/ # Comprehensive documentation
โโโ test_server.py # Direct testing scriptKey Design Patterns
Import Inside Functions: Configuration modules imported inside tool functions to avoid timing issues
Multi-Level Token Caching: Memory cache + file persistence with 1-hour expiration and 5-minute buffer
Hierarchical Discovery: Automatic campus โ building โ floor relationship building
Hybrid Resolution: Hardcoded Denver aliases + dynamic fuzzy matching for other sites
๐งช Testing
MCPTools Testing
# List all tools
mcp tools uv run src/server.py
# Test authentication
mcp call test_zoom_connection --params '{}' uv run src/server.py
# Interactive testing
mcp shell uv run src/server.pyDirect Script Testing
python test_server.py๐ Documentation
Comprehensive documentation available in docs/:
Quick Start Guide - Setup and basic usage
Authentication Guide - OAuth implementation details
Testing Guide - MCPTools usage and examples
Best Practices - Zoom-specific patterns
Advanced Features - Deep dive into capabilities
๐ Security
Credentials stored in
.envfiles (not committed to git)Token caching with secure file permissions
Bearer token automatic refresh
Error messages don't expose sensitive information
๐ค Contributing
Fork the repository
Create a feature branch
Make your changes
Test with MCPTools
Submit a pull request
๐ License
This project is licensed under the MIT License.
๐ Troubleshooting
Common Issues
"Zoom credentials not configured"
Verify
.envfile exists with correct variablesCheck environment variable names match exactly
"Token request failed: 401"
Verify Zoom app credentials are correct
Ensure app has
room:read:adminscopeConfirm app is Server-to-Server OAuth type
"No location matches found"
Check spelling of location query
Use
get_zoom_sitesto see available locationsTest with
resolve_locationto debug fuzzy matching
Import timing issues
Configuration modules imported inside tool functions
Never import config at module level before
initialize_config()
Debug Commands
# Test connection
mcp call test_zoom_connection --params '{}' uv run src/server.py
# List all sites
mcp call get_zoom_sites --params '{}' uv run src/server.py
# Debug location resolution
mcp call resolve_location --params '{"location_query":"your_query"}' uv run src/server.pyBuilt with FastMCP and the Model Context Protocol.
Available Tools
5 toolsget_room_detailsA
Get detailed information about a specific Zoom room.
USE THIS when you have a specific room ID and need complete details about that single room.
Returns full room configuration, settings, and recent events.
Perfect for: "Tell me about room ABC123", "What are the details of this specific room?"
Inputs: room_id (required).
get_zoom_roomsA
Get Zoom rooms with optional location filtering.
IMPORTANT: For maximum efficiency when checking ALL rooms company-wide (e.g., "find offline rooms anywhere", "all rooms", "company-wide status"),
DO NOT provide location_query - this makes a single API call to get all rooms.
USE location_query ONLY for specific location filtering (e.g., 'SF1', 'DEN1', 'Floor 1', 'Denver Building 2').
This uses smart location resolution but makes multiple API calls per location.
Examples:
- Company-wide queries: omit location_query for single efficient API call
- Location-specific: use location_query='SF1' for San Francisco only
Inputs: location_query.
get_zoom_sitesA
Get all Zoom sites/locations with hierarchy and aliases.
USE THIS to understand available locations before using location-specific queries.
Shows campus โ building โ floor relationships and common aliases like 'SF1', 'DEN1', etc.
Perfect for: "What locations do we have?", "Show me all sites", "What are the building names?"
Inputs: no named parameters.
resolve_locationA
DEBUG TOOL: Test how location queries get resolved without fetching rooms.
USE THIS to understand what locations will be searched before running expensive room queries.
Shows which aliases match, what locations are found, and how many API calls would be made.
Perfect for: "How would 'DEN1' be resolved?", "What locations match 'Floor 1'?", debugging location queries.
Inputs: location_query (required).
test_zoom_connectionA
Test Zoom API connection and validate authentication credentials.
USE THIS FIRST to verify your Zoom credentials are working before using other tools.
Returns authentication status, account info, and token cache status.
Perfect for: "Is my connection working?", "Test Zoom authentication", troubleshooting setup.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogโฆ
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap. get_room_details targets a single room, get_zoom_rooms retrieves multiple rooms with optional filtering, get_zoom_sites lists locations, resolve_location is a debug tool for location resolution, and test_zoom_connection validates authentication. The descriptions explicitly differentiate use cases, preventing misselection.
All tools follow a consistent verb_noun pattern with snake_case naming (e.g., get_room_details, get_zoom_rooms, get_zoom_sites, resolve_location, test_zoom_connection). The verbs are descriptive and aligned with their functions, making the set predictable and readable.
With 5 tools, the server is well-scoped for managing Zoom rooms and locations. Each tool earns its place by covering essential operations: authentication testing, location resolution, site listing, room listing with filtering, and detailed room queries. This count is appropriate for the domain without being too thin or heavy.
The tool set covers core workflows for Zoom room management, including authentication, location hierarchy, and room queries. However, there are minor gaps such as the lack of update or delete operations for rooms (e.g., modifying room settings or removing rooms), which agents might need to work around. The surface is largely complete for monitoring and querying purposes.
Maintenance
Related MCP Connectors
Zoom Revenue Accelerator server for sales insights, conversations, and deal intelligence.
Zoom Meetings server for meeting search, recordings, transcripts, summaries, and meeting assets.
Zoom workspace server for meetings, chat, docs, recordings, and AI-generated collaboration content.
Zoom Chat server for channels, messages, contacts, files, and chat collaboration.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Zoom services through the Zoom API. Provides access to meeting management, user administration, and other Zoom platform features through natural language commands.-
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Zoom services through the Zoom API. Provides access to Zoom's functionality for meeting management, user operations, and platform features through natural language.-
- FlicenseNot gradedqualityDmaintenanceEnables network management through Cisco Catalyst Center, providing tools for monitoring device health, tracking client data, and managing network issues. It also supports compliance and lifecycle management by retrieving EoX summaries and detailed security advisory status.-
- AlicenseNot gradedqualityDmaintenanceEnables managing Zoom users, meetings, webinars, and recordings through 24 tools with support for server-to-server OAuth and static token authentication.8 npmMIT