Zoom MCP Server E11174d6

MCP办公协作

提供方 AlexPortSwigger

办公协作 stdio · 本地进程 OAuth 授权 社区 / 第三方 Claude DesktopClaude
查看接入方式

一个零配置的Zoom团队聊天和会议记录只读服务器,支持聊天记录查询、会议摘要获取和本地搜索功能。

一句话选型结论

按资料字段整理

Zoom MCP Server E11174d6 属于办公协作类 MCP 服务器,stdio · 本地进程,OAuth 授权,可直接接入 Claude Desktop、Claude,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类办公协作 传输方式stdio · 本地进程 鉴权OAuth 授权 部署方式本地部署
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 22 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

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

能力标签

支持客户端

适用场景

团队协作Python本地部署会议管理聊天记录搜索功能零配置

安装与配置

stdio · 本地进程 OAuth 授权
客户端在本机拉起子进程,数据不出本机
python3 -m venv .venv

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Python,再按安装命令拉取依赖。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

    连接成功后客户端会列出约 22 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
日程与消息

查日程、发消息、约会议。

表单与审批

填表单、走审批流。

团队协作

同步任务、汇总进展。

选择建议

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

值得选的地方

  • 资料标注 22 个工具,覆盖面较广,能满足多种调用。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在办公协作场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Zoom MCP Server E11174d6当前 22 stdio · 本地进程 本地部署 有 2026-05-17
CowAgent 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Karakeep MCP 未标注 未标注 未标注 无 2026-05-17
agentscope 未标注 stdio · 本地进程 本地部署 有 2026-04-11
note-gen 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Everywhere 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

办公协作
字段来自项目仓库与公开索引,中文说明由本站标注
提供方AlexPortSwigger上游标注的维护方 AlexPortSwigger
分类办公协作本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Python本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

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

Zoom MCP Server v2.2

Read-only MCP server for Zoom Team Chat and meeting transcripts. Zero-config — no client secret to enter, no setup script. Distributed as a .mcpb bundle.

What this connector lets Claude do

Use case Tool route
"What's been said in #channel today?" zoom_message_history(channel, from_date, to_date)
"Summarise #channel this week" zoom_message_history over the date range, then Claude summarises
"What did say in #channel?" zoom_message_history for the channel, filter by sender in the result
"Catch me up on my DMs with " zoom_message_history(contact=)
"Find anything about across chat (today)" zoom_search_messages(query, channel_filter?) — fast Zoom-native search
"Find mentioned weeks ago / recommendations from " zoom_search_history(query, from_date, sender_filter?) — deep client-side search, no 24h cap
"What channels am I in?" zoom_chat_channels (use starred_only=true for the active ones)
"Who's in #channel?" zoom_chat_channel_members
"What meetings do I have today?" zoom_meeting_list(type=upcoming)
"Summary of meeting X" zoom_meeting_summary_get(meeting_id)
"Recent meeting summaries" zoom_meeting_list then zoom_meeting_summary_get per meeting
"Transcript of meeting X" zoom_meeting_transcript(meeting_id)

Default date window

zoom_message_history and zoom_search_messages default from_date to 7 days ago when no dates are supplied (anchored at to_date if that one alone is given). Pass explicit from_date/to_date for any other range. Note that zoom_search_messages is still capped server-side by Zoom to ~24h regardless of what's passed (see below).

Two-tier search

Zoom's native keyword search (/chat/users/me/messages?search_type=message) is fast but server-side capped to ~24 hours of history regardless of from_date/to_date. To search older content (which the Zoom UI search clearly indexes), v2.2.8 added zoom_search_history: it reads each channel/DM's full history via browse mode and filters keywords client-side. Slower (a few seconds per scan) but unbounded in time. Recommended pattern:

  1. Try zoom_search_messages first (fast, indexed).
  2. If it returns 0 hits and you expect older matches, fall back to zoom_search_history with a wider date range and any sender_filter you can use to narrow.

The MCPB launches an OAuth browser flow on first install (PKCE, no client secret needed). Tokens are Fernet-encrypted on disk; transcripts and chat bodies are never persisted; the SQLite metadata cache stores names and IDs only.

Endpoint status (verified live 2026-05-10 via scripts/live_audit.py)

15 PASS / 1 FAIL / 6 SKIP (skips are tools we can't exercise without specific test data, e.g. a recorded meeting transcript or a chat file ID):

Tool Status Live evidence
zoom_auth_whoami ✅ Returned profile
zoom_chat_channels ✅ 1,548 channels
zoom_chat_channel_members ✅ 78 members in #Devs
zoom_chat_contacts ✅ 209 contacts
zoom_chat_shared_spaces ✅ 0 spaces (legitimate empty)
zoom_message_history ✅ 5 messages from #Devs today
zoom_message_get / zoom_message_thread / zoom_message_pinned ✅ Returned real data
zoom_message_bookmarks ✅ 1 bookmark
zoom_search_messages ✅ 6 hits for "the"
zoom_meeting_list ✅ 10 previous meetings
zoom_meeting_recordings ✅ 0 recordings (legitimate empty for this user)
zoom_meeting_get ✅ Returned meeting topic + manifest
zoom_meeting_summary_get ✅ Endpoint reachable (404 for meetings without AI summaries is correct behaviour)
zoom_chat_shared_space_get, zoom_message_file, zoom_meeting_transcript, zoom_auth_login/logout/resolve ⏭ skip Need specific test data we don't have (a recorded meeting transcript, a chat file ID, a shared space) or are interactive/destructive

When a tool fails with a missing-scope error you'll see a single-line message like HTTP 400 (Zoom code 4711): Zoom OAuth app missing scope. Required: [meeting:read:list_summaries:admin]. Fix: a Zoom Marketplace admin must add the missing scope(s)… — the message names exactly what to add and where.

Why no zoom_meeting_summary_list

The corresponding Zoom REST endpoint (GET /meetings/meeting_summaries) demands meeting:read:list_summaries:admin, a :admin scope exposed only to Server-to-Server OAuth apps, not the User-managed PKCE app this connector ships. Rather than expose a tool that always 4711s, v2.2.6 drops it.

Workaround that's just as good for the "show me recent summaries" workflow: Claude calls zoom_meeting_list → picks meetings → calls zoom_meeting_summary_get per meeting. zoom_meeting_summary_get works fine on the non-:admin meeting:read:summary scope.

When a tool fails with a missing-scope error you'll see a single-line message like HTTP 400 (Zoom code 4711): Zoom OAuth app missing scope. Required: [meeting:read:list_meetings]. Fix: a Zoom Marketplace admin must add the missing scope(s)… — the message names exactly what to add and where.

Tools removed in v2.2.5

These three tools' Zoom REST URLs do not exist publicly — verified against Zoom's published AI Companion OpenAPI spec (one endpoint, archive only) and exhaustive URL probing:

  • zoom_search_ai, zoom_search_ask — the ai_companion:read:search/:ask scopes are advertised by Zoom but no REST URL accepts them. The only AI Companion REST endpoint that exists is GET /v2/aic/users/{userId}/conversation_archive (admin-only compliance archive download).
  • zoom_message_mentions — /chat/channels/{id}/mention_groups returns code 2300 ("endpoint not recognized") for every URL variant tested.

If Zoom ships these endpoints in future, re-adding the tools is a one-line change in server/endpoints.py.

Install (zero config)

  1. Download zoom-mcp-.mcpb
  2. Double-click to install in Claude Desktop (no prompts, nothing to enter)
  3. The connector launches the browser OAuth flow on first run — log in to Zoom, click Allow
  4. Browser auto-closes; Claude tells you you're authenticated
  5. Done

The MCPB has the PortSwigger Zoom dev app's public client ID baked in, and uses PKCE (RFC 7636) — no client secret anywhere, and no environment variables required.

What's available (22 tools)

Each tool has standard MCP annotations, so Claude Desktop's connector-permissions screen groups them into:

  • Read-only (20 tools) — every Zoom API call we expose
  • Write (1 tool) — zoom_auth_login (saves OAuth tokens locally)
  • Destructive (1 tool) — zoom_auth_logout (wipes local tokens, cache, in-memory state)

Tool names share group prefixes (zoom_auth_*, zoom_chat_*, zoom_meeting_*, zoom_message_*, zoom_search_*):

zoom_auth_* — zoom_auth_login, zoom_auth_logout, zoom_auth_resolve, zoom_auth_whoami

zoom_chat_* — zoom_chat_channels (with starred_only), zoom_chat_channel_members, zoom_chat_contacts, zoom_chat_shared_spaces, zoom_chat_shared_space_get

zoom_meeting_* — zoom_meeting_list, zoom_meeting_get, zoom_meeting_recordings, zoom_meeting_transcript, zoom_meeting_summary_get

zoom_message_* — zoom_message_history (auto-paginated channel/DM history with reactions + attachment metadata inline), zoom_message_thread, zoom_message_get, zoom_message_file, zoom_message_pinned, zoom_message_bookmarks

zoom_search_* — zoom_search_messages (fast Zoom-native search, 24h cap), zoom_search_history (deep client-side search, no time cap)

How auth works```

Claude → Browser → zoom.us/oauth/authorize?code_challenge=… → user clicks Allow
↓
http://localhost:53682/oauth/callback ← MCPB local listener
↓
zoom.us/oauth/token (code + verifier; NO secret)
↓
Tokens encrypted at rest in:
macOS: ~/Library/Application Support/zoom-mcp/
Linux: ${XDG_DATA_HOME:-~/.local/share}/zoom-mcp/
Windows: %APPDATA%\zoom-mcp\


PKCE `code_verifier` never leaves the machine. State value verified on the OAuth callback for CSRF protection.

The browser flow is launched automatically on connector startup if there's no valid session yet (`maybe_auth_on_startup` in `server/main.py`). On subsequent launches with a refresh token, auth is silent.

## OAuth scopes the dev app must have configured

Required (after the connector v2.2.6 changes):```
# Profile / contacts
user:read:user
contact:read:list_contacts

# Team Chat (read-only)
team_chat:read:channel
team_chat:read:user_channel
team_chat:read:list_user_channels
team_chat:read:list_members
team_chat:read:list_user_messages
team_chat:read:user_message
team_chat:read:thread_message
team_chat:read:message_emoji
team_chat:read:list_pinned_messages
team_chat:read:list_bookmarks
team_chat:read:file
team_chat:read:chat_control
team_chat:read:list_contacts
team_chat:read:contact
team_chat:read:shared_space
team_chat:read:list_shared_spaces
team_chat:read:list_shared_space_channels
team_chat:read:list_shared_space_members

# Meetings + recordings
meeting:read:meeting
meeting:read:list_meetings        ← needed for zoom_meeting_list
meeting:read:summary              ← needed for zoom_meeting_summary_get
cloud_recording:read:list_user_recordings
cloud_recording:read:list_recording_files
cloud_recording:read:recording
cloud_recording:read:meeting_transcript
cloud_recording:read:content

After adding scopes in marketplace.zoom.us, users must zoom_auth_logout then zoom_auth_login to get a refreshed token with the new scopes.

> Scope name pitfalls (verified live):
> - There is no meeting:read:list_meetings:admin, no meeting:read:list_summaries:admin, no meeting:read:summary:admin in the Zoom Marketplace catalogue — Zoom's 4711 error message suggests :admin variants but only the non-admin names actually exist for end-user OAuth apps.
> - meeting_summary:read:summary (note the underscore) appeared in the older README but is not what Zoom checks — the right name is meeting:read:summary.

Security & data handling

  • TLS 1.2+ enforced on all Zoom traffic
  • PKCE — no client_secret ever distributed or stored
  • OAuth tokens Fernet-encrypted at rest (mode 0600)
  • SQLite metadata cache stores channel/contact/meeting names and IDs only — no message bodies or transcript content on disk
  • Logs scrub bearer tokens, refresh tokens, message bodies, transcript text, search queries, and email addresses
  • zoom_auth_logout wipes everything

Forking

To use this with a different Zoom app:

  1. Create a Zoom Marketplace app, enable Use Public Client OAuth, copy the Public Client ID
  2. Set OAuth redirect to http://localhost:53682/oauth/callback (dev app) or your HTTPS callback (production)
  3. Edit server/main.py → change DEFAULT_CLIENT_ID and DEFAULT_REDIRECT_URI, OR pass them via mcp_config.env in manifest.json
  4. Rebuild: ./scripts/build_mcpb.sh --all

Troubleshooting

Problem Fix
Browser says "this site can't be reached" at localhost:53682 after Zoom auth v2.2.7+ binds dual-stack on 127.0.0.1 and ::1 to fix this. If still broken, check ~/Library/Logs/zoom-mcp/zoom-mcp.log for the bind line. The auth URL is also logged so you can paste it into a browser manually.
"All candidate OAuth ports busy: [53682]" Find what's holding it: lsof -nP -iTCP:53682 -sTCP:LISTEN. Kill or move the conflicting service (gcloud SDK uses this port too — gcloud auth revoke if it's that).
Auth window closed without authorising Re-run zoom_auth_login
Tokens expired and refresh fails zoom_auth_logout, then zoom_auth_login
Browser doesn't pop up at all The auth URL is logged at INFO level — copy it from ~/Library/Logs/zoom-mcp/zoom-mcp.log and paste manually.
Connection timeout / firewall blocks Python macOS System Settings → Network → Firewall → allow incoming connections to your Python binary. Or disable firewall briefly to test.
HTTP 400 (Zoom code 4711) on a tool Zoom OAuth app missing a scope. The error message names exactly which one. Add it in marketplace.zoom.us, then zoom_auth_logout + zoom_auth_login.
zoom_search_messages returns 0 hits when you expect matches Zoom caps search windows to ~24h server-side. For older content, use zoom_message_history with a date range instead.

Development```bash

git clone https://github.com/AlexPortSwigger/zoom-mcp-server.git
cd zoom-mcp-server
python3 -m venv .venv
.venv/bin/pip install -e ".[dev]"

.venv/bin/pytest # 109 tests
./scripts/dev-run.sh # run from source
./scripts/build_mcpb.sh # build .mcpb for host platform
./scripts/build_mcpb.sh --all # build .mcpb for all 4 platforms
python3 scripts/diag_endpoints.py # live-probe endpoints (uses local tokens)
```

License

MIT

常见问题

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

在客户端按下面的安装命令接入:python3 -m venv .venv。装完在客户端配置里引用同一个包或端点。

Zoom MCP Server E11174d6 怎么在 Claude Desktop、Claude 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Zoom MCP Server E11174d6 收费吗?

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

Zoom MCP Server E11174d6 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Zoom MCP Server E11174d6 支持哪些客户端?

资料标注支持 Claude Desktop、Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Zoom MCP Server E11174d6 能提供哪些能力?

资料显示约 22 个工具;能力标签包括 团队协作、Python、Claude。具体工具清单以官方文档为准。

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

运行时为 Python;属于本地进程,需要在本机装好运行环境。

Zoom MCP Server E11174d6 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

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

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