Vendor: gong.io · entry id 03-gong · source 03-conversation-intel.md line 11
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://help.gong.io/docs/about-gong-mcp ; announcement: https://www.gong.io/press/gong-introduces-model-context-protocol-mcp-support-to-unify-enterprise-ai-agents-from-hubspot-microsoft-salesforce-and-others ; community example: https://github.com/cedricziel/gong-mcp
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.
This list came from a repo the vendor does not own. Those are that author's tools for the vendor's API, not the vendor's own published surface, and the two must not be read as the same thing.
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:
enterprise-only in practice. Gong's own help doc says the API is "Available on: Any Gong plan," but there is no self-serve signup at all - every purchase runs through sales with a mandatory annual platform fee (commonly $25,000-$50,000+/yr for mid-market/enterprise, $5,000 minimum) and multi-year contracts. A solo operator cannot get an API key without becoming a paying enterprise customer first.
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:
No GitHub organisation could be tied to gong.io with evidence on 2026-09-08.
Recorded by the harvest: github candidates were seen but none passed the evidence rules.
6 candidate accounts seen and rejected by the evidence rules: cedricziel, Honeyfy, Gongoliers, Gongosoft, Gongju-Unity-Bootcamp. A name match alone is never accepted; the account has to point at the vendor domain.
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://help.gong.io/docs/about-gong-mcp, https://help.gong.io/docs/receive-access-to-the-api, https://www.gong.io/press/gong-introduces-model-context-protocol-mcp-support-to-unify-enterprise-ai-agents-from-hubspot-microsoft-salesforce-and-others, https://www.claap.io/blog/gong-api, https://github.com/cedricziel/gong-mcp
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.