原型 · 预览版：收录官方注册中心里的全部服务器，每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚
新手模式 关
配色跟随系统浅色深色
语言ไทยEnglish中文日本語한국어EspañolDeutsch
☰ 菜单设置
新手模式 关
配色跟随系统浅色深色
语言ไทยEnglish中文日本語한국어EspañolDeutsch

Zoom Team Chat

作者：zoom版本 1.0.1i★ –i在云端运行
注册名称io.github.zoom/zoom-team-chat

安装

概览

作者提供的说明（英文原文）

Zoom Chat server for channels, messages, contacts, files, and chat collaboration.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在云端运行
  • 传输方式: Streamable HTTP
  • 分类: 聊天与邮件

安装

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

安装之前

你需要

你用的是哪个应用？

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude：

  1. 打开 Settings → Connectors
  2. 点击 Add custom connector
  3. 粘贴下面的地址，然后点击 Add
  4. 如果要求登录，请登录作者的服务
SettingsConnectors1+ Add2https://…3
https://mcp.zoom.us/mcp/chat/streamable

在终端中运行这条命令

claude mcp add --transport http zoom-team-chat https://mcp.zoom.us/mcp/chat/streamable

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "zoom-team-chat": {
      "url": "https://mcp.zoom.us/mcp/chat/streamable"
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "zoom-team-chat": {
      "type": "http",
      "url": "https://mcp.zoom.us/mcp/chat/streamable"
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

ChatGPT 只能连接互联网上的服务器：

  1. 打开网页版 ChatGPT → Settings → Connectors (Apps)
  2. 点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
  3. 粘贴下面的地址，起个名字，然后保存
  4. 如果要求登录，请登录作者的服务
SettingsConnectors1+ Create2https://…3
https://mcp.zoom.us/mcp/chat/streamable

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上，无需账户。

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

它能做什么

我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。

基础检查i

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

  • ✓ 通过

    作者与仓库一致

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

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    端点有响应

    尚未检查；我们会轮流检查各个端点

  • … 尚未检查

    使用 OAuth 登录

    尚未检查；我们会轮流检查各个端点

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查；我们会在检查端点时读取工具列表

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

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

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

常见问题

Zoom Team Chat 安全吗？

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

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

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

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.0.1）于4个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Vexa, emailmd, MCP WhatsApp Cloud

替代选择

同一分类中其他作者的服务器，按星标数排序。

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

Vexa

作者：Vexa-ai

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

在云端运行★ 2,949Apache-2.02个月前更新
安装

emailmd

作者：anypost

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

电脑或云端★ 1,385MIT31天前更新
安装

MCP WhatsApp Cloud

作者：codespar

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

在你的电脑上运行★ 277MIT5个月前更新
安装

作者的 README

打开 README

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

MCP Registry

This project provides Zoom's registry of MCP servers at registry.modelcontextprotocol.io. It contains the published registry metadata for remote MCP servers. It does not contain the server implementations themselves.

Registry Servers

io.github.zoom/zoom-workspace
  • Registry metadata: zoom-workspace/server.json
  • Remote URL: https://mcp.zoom.us/mcp/zoom/streamable

Zoom Workspace exposes Zoom meetings, Team Chat, and Zoom Docs to MCP clients. It supports natural-language retrieval of AI-generated summaries, transcripts, recordings, shared documents, and meeting assets, along with recording-specific resources such as playback links and next steps. It can retrieve Zoom Docs content, list cloud recordings, and create follow-up Zoom Docs from Markdown. This server is intended for workflows such as locating where a topic was discussed, generating agendas, capturing notes, identifying action items, and creating follow-up documents from existing Zoom collaboration data.

io.github.zoom/zoom-docs
  • Registry metadata: zoom-docs/server.json
  • Remote URL: https://mcp.zoom.us/mcp/docs/streamable

Zoom Docs provides a focused MCP surface for working with Zoom documents and notes. It currently supports creating new Zoom Docs from Markdown content and retrieving existing Zoom Docs or notes in Markdown form. The server is designed for structured document generation and readback flows used by AI agents and developer tooling, without exposing broader document lifecycle operations such as update or delete.

io.github.zoom/zoom-whiteboard
  • Registry metadata: zoom-whiteboard/server.json
  • Remote URL: https://mcp.zoom.us/mcp/whiteboard/streamable

Zoom Whiteboard provides MCP tools for creating new editable whiteboards and diagrams from prompts and for locating existing boards in a user's account. It is intended for workshop planning, visual collaboration, and diagram-generation use cases, including simple flowcharts and more technical diagram types. The server only exposes boards the authenticated user can access.

io.github.zoom/zoom-revenue-accelerator
  • Registry metadata: zoom-revenue-accelerator/server.json
  • Remote URL: https://mcp.zoom.us/mcp/revenue_accelerator/streamable

Zoom Revenue Accelerator provides a focused MCP surface for sales insights, conversations, and deal intelligence. It is intended for workflows such as reviewing customer interactions, preparing follow-up notes, and finding context from revenue-related conversations and activity.

io.github.zoom/zoom-team-chat
  • Registry metadata: zoom-team-chat/server.json
  • Remote URL: https://mcp.zoom.us/mcp/chat/streamable

Zoom Chat provides a focused MCP surface for chat channels, messages, contacts, files, and collaboration context. It is intended for workflows such as locating chat history, preparing summaries, and generating follow-ups from chat activity. The registry name remains io.github.zoom/zoom-team-chat for continuity with the existing published entry.

io.github.zoom/zoom-meetings
  • Registry metadata: zoom-meetings/server.json
  • Remote URL: https://mcp.zoom.us/mcp/meeting/streamable

Zoom Meetings provides a focused MCP surface for meeting search, recordings, transcripts, summaries, and meeting assets. It is intended for workflows such as locating meeting context, reviewing recordings, and preparing follow-ups from meeting content.

io.github.zoom/zoom-tasks
  • Registry metadata: zoom-tasks/server.json
  • Remote URL: https://mcp.zoom.us/mcp/tasks/streamable

Zoom Tasks provides a focused MCP surface for creating, updating, assigning, and synchronizing tasks. It is intended for workflows such as managing task details, reviewing comments and steps, and coordinating work across collaborators.

Registry Notes

  • Namespace: io.github.zoom/*
  • Transport: streamable-http
  • Current metadata versions in this repository: 1.0.2 for Workspace, Docs, and Whiteboard; 1.0.1 for Revenue Accelerator and Team Chat; 1.0.0 for Meetings and Tasks

Registry API Records

  • Search listing: https://registry.modelcontextprotocol.io/v0.1/servers?search=zoom&limit=100
  • Workspace latest version: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-workspace/versions/latest
  • Docs latest version: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-docs/versions/latest
  • Whiteboard latest version: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-whiteboard/versions/latest
  • Revenue Accelerator latest version: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-revenue-accelerator/versions/latest
  • Team Chat latest version: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-team-chat/versions/latest
  • Meetings latest version: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-meetings/versions/latest
  • Tasks latest version: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zoom%2Fzoom-tasks/versions/latest

Publishing Workflow

The MCP Registry entries in this repository are published with mcp-publisher.

For the Zoom-specific step-by-step publishing history and lessons learned, see RUNBOOK.md.

Prerequisites
  • Install mcp-publisher
  • Authenticate with GitHub using an account that has access to the target GitHub organization
  • Ensure the GitHub organization membership associated with the namespace is public
Publish a New Version
  1. Update the relevant server.json.
  2. Increment the version field before publishing an update.
  3. Change into the corresponding server directory.
  4. Refresh or establish a login session if needed:
   mcp-publisher login github
  1. Publish the entry:
   mcp-publisher publish
  1. Verify the published record using the registry API URLs listed above.

Example:

cd zoom-workspace

mcp-publisher publish

To publish the two newer entries:

cd ~/temp/mcp-registry-publish/zoom-revenue-accelerator

mcp-publisher publish

cd ~/temp/mcp-registry-publish/zoom-team-chat mcp-publisher publish

To publish the Meetings and Tasks entries:

cd ~/temp/mcp-registry-publish/zoom-meetings

mcp-publisher publish

cd ~/temp/mcp-registry-publish/zoom-tasks mcp-publisher publish

Maintenance

Published entries can be updated by modifying the corresponding server.json, incrementing the version, and republishing from that server's directory with mcp-publisher publish.

问 PopNx