io.github.zoom/zoom-revenue-accelerator
Zoom Revenue Accelerator server for sales insights, conversations, and deal intelligence.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport http zoom-revenue-accelerator 'https://mcp.zoom.us/mcp/revenue_accelerator/streamable'
{
"mcpServers": {
"zoom-revenue-accelerator": {
"type": "http",
"url": "https://mcp.zoom.us/mcp/revenue_accelerator/streamable"
}
}
}
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
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.2for Workspace, Docs, and Whiteboard;1.0.1for Revenue Accelerator and Team Chat;1.0.0for 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
- Update the relevant
server.json. - Increment the
versionfield before publishing an update. - Change into the corresponding server directory.
- Refresh or establish a login session if needed:
mcp-publisher login github - Publish the entry:
mcp-publisher publish - 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.
Questions fréquentes
Qu'est-ce que io.github.zoom/zoom-revenue-accelerator ?
Zoom Revenue Accelerator server for sales insights, conversations, and deal intelligence.
Comment installer io.github.zoom/zoom-revenue-accelerator ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http zoom-revenue-accelerator 'https://mcp.zoom.us/mcp/revenue_accelerator/streamable'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour io.github.zoom/zoom-revenue-accelerator ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
io.github.zoom/zoom-revenue-accelerator est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient io.github.zoom/zoom-revenue-accelerator ?
Il est publié par zoom. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.