Skip to main content
Glama
chadkunsman

Zoom MCP Server

by chadkunsman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ZOOM_CLIENT_IDYesThe Client ID for your Zoom Server-to-Server OAuth app.
ZOOM_ACCOUNT_IDYesThe Account ID for your Zoom Server-to-Server OAuth app.
ZOOM_CLIENT_SECRETYesThe Client Secret for your Zoom Server-to-Server OAuth app.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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?"
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
get_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?"
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.
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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.6/5.0

Scored across 5 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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

ActivityInactive
ResponsivenessNo issues

Resources