Zoom MCP Server

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?"

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

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?"

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.

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.