Zoom MCP Server 31bb02c9

MCP开发工具

提供方 chadkunsman

开发工具 未标注 无需鉴权 社区 / 第三方

Enables intelligent monitoring and management of Zoom rooms across multiple sites using smart location resolution and hierarchical discovery. It provides tools for checking room status, retrieving location hierarchies, and accessing detailed room configurations through the Zoom API.

一句话选型结论

按资料字段整理

Zoom MCP Server 31bb02c9 属于开发工具类 MCP 服务器,传输方式未标注,无需鉴权,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权无需鉴权 部署方式支持远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

未标注 无需鉴权
上游未给出传输方式
  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Zoom MCP Server 31bb02c9当前 未标注 未标注 支持远程部署 无 2026-05-17
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方chadkunsman上游标注的维护方 chadkunsman
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型支持远程部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

8.5 KB
来自项目仓库与上游目录的原文,未做删改

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

🛠️ Tools Available

test_zoom_connection

Test Zoom API authentication and connection status.```bash

Usage: Verify credentials are working

mcp call test_zoom_connection --params '{}' uv run src/server.py


### `get_zoom_sites`
Get all Zoom locations with hierarchy and aliases.```bash
# Usage: Understand available locations and relationships
mcp call get_zoom_sites --params '{}' uv run src/server.py

get_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.```bash

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.py


### `get_room_details`
Get detailed information about a specific room.```bash
# Usage: Deep dive into specific room configuration
mcp call get_room_details --params '{"room_id":"ROOM_ID_HERE"}' uv run src/server.py

resolve_location

Debug tool to test location resolution without fetching rooms.```bash

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 | `SF1`, `NYC`, `DEN` | Entire campus with all buildings/floors |
| Building numbers | `Building 1`, `DEN1` | Specific building or hardcoded alias |
| Floor numbers | `Floor 1`, `3F` | All floors with that number across sites |
| Partial names | `Denver`, `Francisco` | 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```bash
git clone https://github.com/chadkunsman/zoom-mcp.git
cd zoom-mcp

2. Install Dependencies```bash

uv pip install -e .


### 3. Zoom API Configuration

1. Create a **Server-to-Server OAuth** app in Zoom Marketplace
2. Add required scope: `room:read:admin`
3. Get your credentials: Account ID, Client ID, Client Secret

### 4. Configure Credentials

Create `.env` file:```bash
ZOOM_ACCOUNT_ID=your_account_id_here
ZOOM_CLIENT_ID=your_client_id_here
ZOOM_CLIENT_SECRET=your_client_secret_here

5. Test Installation```bash

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)```json
{
  "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```json

{
"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 script

Key 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```bash

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.py


### Direct Script Testing```bash
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 .env files (not committed to git)
  • Token caching with secure file permissions
  • Bearer token automatic refresh
  • Error messages don't expose sensitive information

🤝 Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Test with MCPTools
  5. Submit a pull request

📄 License

This project is licensed under the MIT License.

🆘 Troubleshooting

Common Issues

  1. "Zoom credentials not configured"
    - Verify .env file exists with correct variables
    - Check environment variable names match exactly

  2. "Token request failed: 401"
    - Verify Zoom app credentials are correct
    - Ensure app has room:read:admin scope
    - Confirm app is Server-to-Server OAuth type

  3. "No location matches found"
    - Check spelling of location query
    - Use get_zoom_sites to see available locations
    - Test with resolve_location to debug fuzzy matching

  4. Import timing issues
    - Configuration modules imported inside tool functions
    - Never import config at module level before initialize_config()

Debug Commands```bash

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.py
```


Built with FastMCP and the Model Context Protocol.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Zoom MCP Server 31bb02c9 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Zoom MCP Server 31bb02c9 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Zoom MCP Server 31bb02c9 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Zoom MCP Server 31bb02c9 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Zoom MCP Server 31bb02c9 能提供哪些能力?

资料显示能力标签包括 开发工具、命令行工具、自动化。具体工具清单以官方文档为准。

Zoom MCP Server 31bb02c9 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

Zoom MCP Server 31bb02c9 是本地还是远程?

它是远程端点,连服务地址即可。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。