原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

Zoom Phone MCP

作者:servosity版本 0.1.6i★ 84 (整个仓库的星标)i在你的电脑上运行代码仓库 ↗
注册名称io.github.Servosity/zoom-phone-mcp

安装方法

能做什么

Zoom Phone admin API plus E911, call routing and desk phone audits across client accounts

作者提供的原文

  • 连接方式 在你的电脑上运行
  • 账号或密钥 需要 ZOOM_PHONE_ACCOUNT_ID, ZOOM_PHONE_CLIENT_ID, ZOOM_PHONE_CLIENT_SECRET, PRINTING_PRESS_CLIENT_PROFILE, ZOOM_PHONE_MCP_HTTP_TOKEN
  • 分类 聊天与邮件

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分12/100

质量: 基础检查通过 2/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 2/3 项检查 · 在你的电脑上运行

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude,但需要先准备

不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

  1. 下载开发者的安装文件

    下载作者的 .mcpb 文件

    .mcpb 文件直接来自开发者,我们没有修改

  2. 双击文件,然后在电脑版 Claude 应用中点击 Install

  3. 试一试

    用 Zoom Phone MCP 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Zoom Phone MCP,或回答中出现 Zoom Phone MCP 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

ChatGPT 暂时无法连接 Zoom Phone MCP

Zoom Phone MCP 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器

你可以改用这些方式

A · 使用能连接 Zoom Phone MCP 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

B · 聊天与邮件 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 Zoom Phone MCP

开发者只提供了电脑版 Claude 应用的安装文件

你可以改用这些方式

A · 使用能连接 Zoom Phone MCP 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

Cursor 暂时无法连接 Zoom Phone MCP

开发者只提供了电脑版 Claude 应用的安装文件

你可以改用这些方式

A · 使用能连接 Zoom Phone MCP 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

VS Code 暂时无法连接 Zoom Phone MCP

开发者只提供了电脑版 Claude 应用的安装文件

你可以改用这些方式

A · 使用能连接 Zoom Phone MCP 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Zoom Phone MCP 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

需要你填写的值

  • ZOOM_PHONE_ACCOUNT_ID 机密 必填 env
    为 Zoom MCP 服务器设置 ZOOM_PHONE_ACCOUNT_ID 凭据。
    查看英文原文Set the ZOOM_PHONE_ACCOUNT_ID credential for the Zoom MCP server.
  • ZOOM_PHONE_CLIENT_ID 机密 必填 env
    为 Zoom MCP 服务器设置 ZOOM_PHONE_CLIENT_ID 凭据。
    查看英文原文Set the ZOOM_PHONE_CLIENT_ID credential for the Zoom MCP server.
  • ZOOM_PHONE_CLIENT_SECRET 机密 必填 env
    Set the ZOOM_PHONE_CLIENT_SECRET credential for the Zoom MCP server.
  • ZOOM_PHONE_BASE_URL env
    Zoom Phone API 的基础 URL。请保留预先填写的默认值。
    查看英文原文Base URL for the Zoom Phone API. Leave the prefilled default.
  • ZOOM_PHONE_TOKEN_URL env
    Server-to-Server OAuth 交换请求所提交的令牌端点。保留预先填写的默认值。
    查看英文原文Token endpoint the Server-to-Server OAuth exchange posts to. Leave the prefilled default.
  • ZOOM_PHONE_OAUTH_SCOPE env
    可选。留空:Zoom Server-to-Server OAuth 令牌会携带添加到应用中的权限范围。
    查看英文原文Optional. Leave blank: a Zoom Server-to-Server OAuth token carries the scopes added to the app.
  • PRINTING_PRESS_CLIENT_PROFILE 机密 必填 env
    Only for tenant-gated multi-client deployments: binds the MCP server to an existing Printing Press client profile. It does not select a Zoom account. Leave blank for a single-tenant install.
  • ZOOM_PHONE_MCP_READ_ONLY env
    可选。设置为恰好为 1 时,将拒绝所有写入操作以及任何返回机密信息的读取操作。留空则保持所有工具可用。
    查看英文原文Optional. Set to exactly 1 to refuse every write and every secret-returning read. Leave blank to keep every tool available.
  • ZOOM_PHONE_NO_LOCAL_DATA env
    Optional. Set to 1 to keep no local copy of API responses: reads go to the API and the response cache is off. The audits that read the local mirror then report nothing assessed. Leave blank to keep t…
  • ZOOM_PHONE_MCP_UPLOAD_ROOT env
    Optional. A folder MCP file uploads (audio library files) may be read from by path. Leave blank: uploads then take base64 file content and the server reads no local path.
  • ZOOM_PHONE_USER_AGENT env
    覆盖 CLI 在 Zoom 请求中发送的 User-Agent。留空则使用内置的 User-Agent。
    查看英文原文Overrides the User-Agent the CLI sends on Zoom requests. Leave blank to use the built-in User-Agent.
  • ZOOM_PHONE_MCP_HTTP_TOKEN 机密 必填 env
    仅在使用 --transport http 运行 MCP 服务器时需要。调用方必须发送匹配的 Authorization: Bearer 请求头。默认的本地 stdio 传输不需要此项。
    查看英文原文Required only when running the MCP server with --transport http. Callers must send a matching Authorization: Bearer header. Not needed for the default local stdio transport.

说明为自动翻译,变量名保持原样;不确定时请查看原文。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

GitHub 星标i
84 (整个仓库的星标)
该仓库包含多个 MCP 条目,星标在排名中只计算一次
每周下载量i
不在 npm/PyPI 上
许可证i
未注明许可证
连接方式
在你的电脑上运行
最新版本i
0.1.6
发布到注册中心i
2026年11月14日
代码最后更新i
2026年11月19日
作者
servosity
软件包
mcpb: …/zoom-phone-mcp.mcpb
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

在你的电脑上运行,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 Servosity 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于昨天

  • ! 注意

    有许可证

    GitHub 无法识别许可证类型;请打开文件自行查看

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

已公开的漏洞(OSV.dev)

未检查:只能检查标明版本的 npm 和 PyPI 包

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/servosity-zoom-phone-mcp.svg)](https://mcp.popnx.com/en/servers/servosity-zoom-phone-mcp)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“聊天与邮件”中的其他服务器比较i

  • 星标数多于此分类中其他 2038 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 2038 个服务器的 83% 更新
  • 基础检查结果等于或优于此分类中其他 2038 个服务器的 49%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Zoom Phone MCP 安全吗?

它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:ZOOM_PHONE_ACCOUNT_ID, ZOOM_PHONE_CLIENT_ID, ZOOM_PHONE_CLIENT_SECRET, PRINTING_PRESS_CLIENT_PROFILE, ZOOM_PHONE_MCP_HTTP_TOKEN

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于昨天,最新版本(0.1.6)于6天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。

有什么可以替代它?

同一分类中有:emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

emailmd

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

作者:anypost广泛使用↓ 5432/周★ 13956天前更新

电脑或云端✓ 服务方 · emailmd.dev

Infobip MCP

Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.

作者:infobip起步阶段★ 3613个月前更新

在云端运行✓ 服务方 · infobip.com

kernelCAD

CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.

作者:w1ne起步阶段★ 3524天前更新

在云端运行✓ 服务方 · kernelcad.com
与相似项目对比
本项
Zoom Phone MCP
emailmdKite Discord Bot Buildere2a — email for AI agentsInfobip MCPkernelCAD
运行位置需要安装在电脑上云端或安装在电脑上都可以在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥是否否否否否
可在 Claude 中按 + 添加否否否否是否
基础检查2/35/54/44/44/44/4
许可证NOASSERTIONMITAGPL-3.0Apache-2.0MITMIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Zoom Phone + AI - for ChatGPT, Claude, GitHub Copilot, Microsoft 365 Copilot, Gemini, and any agent that speaks MCP

Unofficial. Community-built Claude Code Skill and MCP server for the Zoom

Phone API. Not affiliated with, endorsed by, or sponsored by Zoom Communications, Inc.

▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.

Every Zoom Phone admin operation plus E911, routing and footprint audits, across every client account. Works with the AI you already use - ChatGPT (Plus/Pro+), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Microsoft 365 Copilot / Copilot Studio and Google Gemini via the remote path. Free, open source, runs on your laptop. Built for MSP owners. No code required.

Works with your agent

The six agents MSP owners actually use (self-serve, works today):

Your AI agentHow to install the Zoom Phone skill
Claude DesktopRun installer, then Settings > Extensions to register zoom-phone-mcp (no JSON editing).
ChatGPT (paid plans)Run installer, host zoom-phone-mcp over HTTPS with ZOOM_PHONE_MCP_HTTP_TOKEN set, then register it as a Developer Mode connector if your connector settings can send the bearer token.
Codex CLIPaste the install prompt below.
Claude CodePaste the install prompt below.
Claude CoworkPaste the install prompt below.
GitHub Copilot (VS Code)Run installer, add zoom-phone-mcp to mcp.json under the servers key, then pick Agent mode.

For ChatGPT, run zoom-phone-mcp --transport http with ZOOM_PHONE_MCP_HTTP_TOKEN set, on an HTTPS host; every request sends that token. See mcp-install.md.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: these are the remote / enterprise path, not the local binary you just installed.

AgentWhat it takes
Microsoft 365 Copilot / Copilot StudioNot self-serve. Host zoom-phone-mcp over HTTPS with ZOOM_PHONE_MCP_HTTP_TOKEN set, then wire it into Copilot Studio (Tools > Add a tool > Model Context Protocol > Server URL) or a declarative agent, if it can send the bearer token. Needs a Copilot Studio license + tenant admin. See mcp-install.md.
Google GeminiGemini CLI is local - same as Claude Code. The Gemini app is remote - same HTTPS path as ChatGPT. See mcp-install.md.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).

Run more than one agent? Install across all 51+ supported agents in one command: npx skills add Servosity/msp-skills@latest (requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Download Zoom Phone MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Zoom Phone release on the releases page.)

Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:

/plugin marketplace add Servosity/msp-skills

/plugin install zoom-phone@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the Zoom Phone Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/zoom-phone/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/zoom-phone/install.ps1 | iex. Then authenticate per the README and run zoom-phone-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/zoom-phone/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/zoom-phone/install.sh)

The installer drops both zoom-phone-cli (the CLI) and zoom-phone-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

zoom-phone-cli --version
Upgrade to the latest version

The installer always fetches the current release - re-run it to upgrade:

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/zoom-phone/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/zoom-phone/install.ps1 | iex

Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update zoom-phone@msp-skills.

Add to Claude Desktop, GitHub Copilot, Gemini CLI, Microsoft 365 Copilot, or another MCP client

After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the remote Microsoft 365 Copilot / Copilot Studio path. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.

Install for Hermes

From the Hermes CLI:

hermes skills install servosity/msp-skills/skills/zoom-phone --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/zoom-phone --force

Hermes speaks MCP natively, so it can also use the zoom-phone-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the zoom-phone skill from https://github.com/servosity/msp-skills/tree/main/skills/zoom-phone. The skill defines how its required CLI (zoom-phone-cli) can be installed via the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

Create a Server-to-Server OAuth app in each client's Zoom App Marketplace (Develop > Build App > Server-to-Server OAuth), add the phone admin scopes you need, and copy its Account ID, Client ID and Client Secret.

macOS / Linux:

ZOOM_PHONE_ACCOUNT_ID=<account-id> ZOOM_PHONE_CLIENT_ID=<client-id> ZOOM_PHONE_CLIENT_SECRET=<client-secret> zoom-phone-cli doctor

Windows (PowerShell):

$env:ZOOM_PHONE_ACCOUNT_ID="<account-id>"; $env:ZOOM_PHONE_CLIENT_ID="<client-id>"; $env:ZOOM_PHONE_CLIENT_SECRET="<client-secret>"; zoom-phone-cli doctor

Managing several clients? Save one profile per client Zoom account (the secret is read from stdin, never from the command line), then run any read across all of them:

printf '%s' "$ACME_SECRET" | zoom-phone-cli accounts connect acme --account-id <account-id> --client-id <client-id> --client-secret-stdin

zoom-phone-cli fleet -- e911 audit

doctor checks config, paths, and API reachability, and reports whether credentials are loaded - it does not validate them. Run a read command to confirm the credential actually works end-to-end.

What this skill does

Question your MSP keeps askingCommand
Which users, common areas and sites have a missing or unverified 911 address?zoom-phone-cli e911 audit --agent
Where does a call to the main number ring, in business and closed hours?zoom-phone-cli routing trace +14155550123 --agent
Which IVR keys point at nothing, and which queues have nobody to answer?zoom-phone-cli routing audit --agent
Which numbers are unassigned, pending, or held by an inactive user?zoom-phone-cli numbers inventory --agent
Which desk phones are offline, unassigned or on drifted firmware?zoom-phone-cli devices health --agent
Which external callers missed us this week and are still waiting?zoom-phone-cli callbacks --since 7d --agent
What does Jane hold, and what is the plan to remove it?zoom-phone-cli offboard jane@example.com --agent
Run the E911 audit for every client accountzoom-phone-cli fleet -- e911 audit

e911 audit, numbers inventory and devices health read the local mirror: run zoom-phone-cli sync --full first (each command names the exact resources it needs when they are missing). routing, callbacks and the group memberships in footprint and offboard read live data.

Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.

What makes this different

Most Zoom integrations and MCP servers proxy each question into a live API call. That's fine for one record. It dies at scale, when you're asking "which users across all 30 client accounts have no verified 911 address".

This skill syncs Zoom into a local SQLite mirror with full-text search. Aggregate questions become one local SQL join: instant, offline, and the AI sees the answer, not the raw data. Compound commands like e911 audit, devices health and footprint join users, sites, common areas, emergency addresses, numbers and desk phones - work a stateless API wrapper can't do. fleet runs the same read across every client account and returns one table with an account column.

The pain this closes

Every client is a separate Zoom account with its own portal, and the questions that matter cross pages the portal keeps apart. Zoom's own emergency services best practices note that in the United States the RAY BAUM's Act requires a dispatchable address with every emergency call, and that each user and device should have a default address. Checking that, finding dead IVR keys, and offboarding a user by hand means clicking through every tenant.

  • zoom-phone-cli e911 audit - every missing or unverified emergency address, in one list.
  • zoom-phone-cli routing audit - dead IVR targets and call queues with nobody to answer.
  • zoom-phone-cli offboard jane@example.com - the ordered removal plan; --apply runs it after a live re-check.
  • zoom-phone-cli fleet -- e911 audit - the same answer for every client account.

See pain-point.md for the longer narrative.

Frequently asked questions

Does this work with ChatGPT?

Yes, on **Plus, Pro, Team,

只显示了开头部分;其余内容请在仓库中阅读