Gong is included for two first-party agent roles: a hosted read-only MCP server that synthesizes account, deal, and contact insights for external AI clients, and a Gong MCP client that connects Gong agents to approved external servers.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
AI-synthesized account and deal context from eligible calls and emails through ask_account and ask_deal, plus contact briefs through generate_brief; private calls and raw transcripts, messages, and activity lists are excluded.
Generate synthesized account, deal, or contact insight for specified entities and date ranges from eligible Gong calls and emails. The server returns generated insight rather than raw conversation or activity records.
No Gong MCP write was verified; the documented MCP surface is read-only. Use a separately authorized API or the native UI for mutations and do not attribute those writes to MCP.
OAuth 2.0 Authorization Code with PKCE uses a manually configured client ID and secret because Dynamic Client Registration is unsupported. Personal access follows the authorizing user's Gong permissions; shared access uses one organization-wide token.
Private calls are excluded, personal mode follows user permissions, shared mode centralizes access under one organization token, and every request consumes credits based on data volume. Repeated identical requests consume credits again.
Three synthesis tools only; no raw transcripts/messages/activity lists; private calls excluded; no creates, updates, or deletes in Gong or CRM; no Dynamic Client Registration; assigned-seat dependency; credit usage per request and per open-ended brief section.
Agent access
Support: Official MCP server + 3rd Party MCP services
Read scope: ask_account and ask_deal synthesize eligible call and email context for an entity and period; generate_brief synthesizes contact context. None returns raw transcripts, messages, or activity lists.
Write scope: No MCP writes verified; the documented surface is read-only.
Authentication: Manually registered OAuth 2.0 Authorization Code with PKCE; Dynamic Client Registration is not supported. Administrators configure a client ID and secret for the external MCP client.
Approval boundary: The Gong server has no write approval boundary because its three tools are read-only. For retrieval, BYO-UI should confirm entity, date range, access mode, and broad brief sections because shared mode changes the identity boundary and each request consumes credits.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Gong ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
three read-only tools, synthesis outputs, exclusions, OAuth PKCE, personal/shared permissions, seats, and credits
Tool catalog, output boundary, OAuth registration, access modes, seats, and credit behavior reviewed 2026-07-22
First-party API reference or API overview recorded for this platform.
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party MCP documentation or product announcement recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
MCP credit consumption
MCP credit consumption reviewed from live first-party material on 2026-07-22.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
