Who can use this: Tech admin
Available on: Any Gong plan
The Gong MCP client allows Gong AI agents to connect to external MCP servers and use external data in Gong AI workflows.
How the Gong MCP client works
The Gong MCP client allows Gong AI agents to retrieve data from external MCP servers as part of AI workflows.
When a Gong AI feature, such as AI Briefer, needs external data, Gong sends a request to the configured MCP server. The MCP server exposes tools that return structured data or perform actions. Gong then uses the returned data to generate AI outputs.
For example, an AI Briefer section can call an external MCP server to retrieve customer support tickets, implementation updates, or CRM information and include those insights directly in the generated brief.
Connecting Gong to external data sources
Gong supports two options for connecting to external data sources using MCP connections.
Supported transport methods and protocols
The Gong MCP client supports MCP servers that use the following transport methods:
SSE (Server-Sent Events)
Streamable HTTP
The Gong MCP client supports MCP servers that use this communication protocol:
JSON-RPC 2.0
Authentication methods
The MCP client supports the following authentication methods for connecting to external MCP servers.
OAuth 2.0 with dynamic client registration
The preferred method for automatic registration is OAuth 2.0 with dynamic client registration.
Gong retrieves the OAuth configuration by querying the /.well-known/oauth-authorization-server endpoint and then registers itself as a client.
The authorization server must expose a valid registration_endpoint and must also support one of the following token endpoint authentication methods. Gong selects an authentication method using this order of preference:
client_secret_basic
none
client_secret_post
OAuth 2.0 with pre-configured credentials
OAuth 2.0 with pre-configured credentials is used when Gong has already been registered as an application in the third-party provider portal.
Provide the client_id and client_secret generated by the external provider. Gong uses these credentials to initiate the authorization code grant or client credentials flow.
When registering Gong in the third-party provider portal, add the following Gong redirect URI to the provider allowlist:
https://app.gong.io/mcp/callback
Without this redirect URI, the OAuth handshake fails and the provider blocks the connection.
No authentication
Use no authentication for MCP servers that do not require authentication, such as internal tools or development environments.
Authorization scopes
The MCP client supports two authorization scopes.
Company-wide access: Company-wide access uses a single shared token managed by a tech admin. All users access the external system using the same organization-level identity.
User-specific access: User-specific access requires additive authorization. A tech admin must first authorize the connector for the organization, and each user must then authorize their own account.
This model is used when the external system enforces user-level permissions.