Vendor: zoom.com · entry id 03-zoom-revenue-accelerator · source 03-conversation-intel.md line 315
The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established by hand on 2026-08-24. On 2026-09-04 the recorded URL served a documentation page, not an MCP endpoint. That is where to read about the server, not where to connect to it. An agent needs the second.
mcp_status, verbatim from the file:
official
mcp_url, verbatim from the file:
https://news.zoom.com/zoom-revenue-accelerator-mcp-connector/ ; https://github.com/zoom/zoom-plugin/blob/main/CONNECTORS.md
A tool below is one the server NAMES. Nobody has called it. That is the same two tier honesty rule the rest of the directory runs on: a named tool is research, and BENCH-TESTED stays the only claim that anybody ran anything.
141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. Every name across every server is on the tools index.
No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence.
api_gate, verbatim from the file:
unknown/enterprise-leaning. Zoom Revenue Accelerator ships as an add-on to Zoom's paid meeting plans; explicit self-serve pricing for a single-seat/solo API user was not found in this research.
949 of 1252 entries carry an unknown gate. Unknown is a legal answer and it ships as unknown rather than as a guess.
No documentation URL recorded.
727 of 1252 entries are in the same position. Blank is legal and it is published as blank.
Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.
The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.
A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:
github.com/zoom tied to the vendor by rule 1, the directory already classed this repo first-party and its owner is an Organization, confidence strong
The five most recently pushed, on 2026-09-08:
| Repository | Kind | Description | Stars | Pushed | Latest release |
|---|---|---|---|---|---|
| rtms-samples | docs or examples | RTMS sample apps | 27 | 2026-09-05 | |
| zoomapps-advancedsample-react | docs or examples | This repository contains an Advanced Zoom Apps Sample. It should serve as a starting point for you to build and test... | 64 | 2026-09-04 | |
| zoom-plugin-claude | plugin or integration | Claude plugin for planning, building, and debugging Zoom integrations across REST APIs, SDKs, webhooks, bots, and MCP... | 7 | 2026-09-03 | |
| skills | other | Skills for building with Zoom SDKs, APIs, MCP servers, and integrations across web, mobile, desktop, and server... | 74 | 2026-09-03 | feb-2026 |
| videosdk-reactnative-quickstart | docs or examples | This is a sample application that demonstrates how to use the Zoom Video SDK in a React Native application. | 10 | 2026-09-02 |
Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.
A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.
Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.
5 source URLs. Raw sources field, verbatim:
https://news.zoom.com/zoom-revenue-accelerator-mcp-connector/, https://github.com/zoom/zoom-plugin/blob/main/CONNECTORS.md, https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0082725, https://developers.zoom.us/docs/api/rest/reference/iq/methods/, https://developers.zoom.us/docs/api/iq/
Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.