emailmd
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Zoom Phone admin API plus E911, call routing and desk phone audits across client accounts
作者提供的原文
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 12/100 |
质量: 基础检查通过 2/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 2/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
用 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 的应用
B · 聊天与邮件 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
Claude Code 暂时无法连接 Zoom Phone MCP
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Zoom Phone MCP 的应用
Cursor 暂时无法连接 Zoom Phone MCP
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Zoom Phone MCP 的应用
VS Code 暂时无法连接 Zoom Phone MCP
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Zoom Phone MCP 的应用
ZOOM_PHONE_ACCOUNT_ID 机密 必填 envZOOM_PHONE_CLIENT_ID 机密 必填 envZOOM_PHONE_CLIENT_SECRET 机密 必填 envZOOM_PHONE_BASE_URL envZOOM_PHONE_TOKEN_URL envZOOM_PHONE_OAUTH_SCOPE envPRINTING_PRESS_CLIENT_PROFILE 机密 必填 envZOOM_PHONE_MCP_READ_ONLY envZOOM_PHONE_NO_LOCAL_DATA envZOOM_PHONE_MCP_UPLOAD_ROOT envZOOM_PHONE_USER_AGENT envZOOM_PHONE_MCP_HTTP_TOKEN 机密 必填 env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过 GitHub 账户 Servosity 验证,该账户拥有此仓库
代码最后更新于昨天
GitHub 无法识别许可证类型;请打开文件自行查看
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/servosity-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
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Build and fix Discord bots from a chat. Kite hosts them 24/7, with no code to deploy.
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.
CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.
| 本项 Zoom Phone MCP | emailmd | Kite Discord Bot Builder | e2a — email for AI agents | Infobip MCP | kernelCAD | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 是 | 否 |
| 基础检查 | 2/3 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | NOASSERTION | MIT | AGPL-3.0 | Apache-2.0 | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the Zoom Phone skill |
|---|---|
| Claude Desktop | Run 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 CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste 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.
Big install base, but an honest heads-up: these are the remote / enterprise path, not the local binary you just installed.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not 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 Gemini | Gemini 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.mddirectly *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.
.mcpbDownload 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
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, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/zoom-phone/install.ps1 | iex. Then authenticate per the README and runzoom-phone-cli --helpto explore.
The same prompt works in any agent that can run shell.
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
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.
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.
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.
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 theopenclaw:frontmatter block.
OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.
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.
| Question your MSP keeps asking | Command |
|---|---|
| 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 account | zoom-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.
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.
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.
Yes, on **Plus, Pro, Team,