Gong (Preview)

Gong brings deep revenue insights into your Copilot workflows, helping teams ask questions, generate briefs, and surface risks, objections, next steps, and stakeholder context from Gong AI OS data.

This connector is available in the following products and regions:

Service	Class	Regions
Copilot Studio	Premium	All Power Automate regions except the following: - US Government (GCC) - US Government (GCC High) - China Cloud operated by 21Vianet - US Department of Defense (DoD)
Logic Apps	Standard	All Logic Apps regions except the following: - Azure Government regions - Azure China regions - US Department of Defense (DoD)
Power Apps	Premium	All Power Apps regions except the following: - US Government (GCC) - US Government (GCC High) - China Cloud operated by 21Vianet - US Department of Defense (DoD)
Power Automate	Premium	All Power Automate regions except the following: - US Government (GCC) - US Government (GCC High) - China Cloud operated by 21Vianet - US Department of Defense (DoD)

Contact
Name	Gong Support
URL	https://help.gong.io
Email	support@gong.io

Connector Metadata
Publisher	Gong.io Inc
Website	https://www.gong.io
Privacy policy	https://www.gong.io/privacy-policy
Categories	Sales and CRM;Productivity

Gong

Overview

The Gong MCP server allows external AI agents, including Microsoft 365 Copilot, to access Gong's specialized revenue intelligence directly. It acts as a secure, standardized bridge that lets AI-powered experiences query Gong's analyzed call and messaging data, retrieve synthesized insights about CRM accounts, deals, and contacts, and generate structured briefing documents, all without requiring users to leave their current workflow.

The server exposes three read-only tools via the Model Context Protocol (MCP). Every tool analyzes Gong activities (calls and messages) tied to CRM entities and returns AI-synthesized insights. No tool returns raw transcripts, message bodies, or activity lists. No tool modifies data or triggers workflows.

Prerequisites

Before setting up the Gong MCP server connector, ensure you have:

A Gong workspace with an active subscription that includes AI features (Credits and Gen AI enabled).
A Technical Administrator account in Gong with permissions to create integrations.
A CRM system connected to Gong (Salesforce, HubSpot, or Microsoft Dynamics) with synced accounts, deals, and contacts.
OAuth 2.0 credentials (Client ID and Client Secret) generated from the Gong integration settings page.

Supported Authentication

The Gong MCP server uses OAuth 2.0 (Authorization Code flow) as its authentication method.

Authorization endpoint: https://app.gong.io/oauth2/authorize Token endpoint: https://app.gong.io/oauth2/generate-mcp-token

Two access scopes are supported:

Company scope (Shared access): A Technical Administrator authenticates once. The token is stored at the company level and used for all organizational requests.
User scope (Personal access): Requires additive authorization. The admin enables the connector for the organization first, then each individual user must also authorize with their own credentials to ensure personalized, permission-aware data access.

When configuring the connector in Copilot Studio or M365 Copilot, provide the Client ID and Client Secret from your Gong integration settings. The MCP client will handle the OAuth flow automatically.

Redirect URI for M365 Copilot plugins: For Copilot Studio, the redirect URI is generated during the MCP connection setup. Copy it from the Copilot Studio configuration screen and add it to your Gong integration's redirect URI allowlist.

Connection Details

MCP Server URL: https://mcp.gong.io
Transport: Streamable HTTP
Protocol: JSON-RPC 2.0 (as specified by the MCP protocol)

Supported Tools

The Gong MCP server exposes three tools. All tools are read-only and return synthesized insights only.

1. ask_account

Purpose: Answer a free-text, natural-language question about a single CRM account by analyzing the Gong activities linked to that account within a specified time window.

When to use:

When you need summaries, insights, or themes about a single CRM account.
To understand account progress, deal blockers, objections, risks, stakeholders, or next steps.
To extract high-level context from calls and messages linked to one CRM account.

Parameters:

crmAccount (string, required) — The CRM account name (e.g. 'Cisco Systems Inc') or direct CRM account ID (e.g. '0015g00000ABCDeQAL'). Name lookup uses exact matching.
question (string, required) — A natural-language question about the account.
workspace (string, optional) — The Gong workspace name (e.g. 'Sales') or numeric workspace ID (e.g. '1234567890'). Required only when the organization has more than one workspace.
fromDateTime (string ISO 8601, optional) — Inclusive start of the activity window (e.g. 2026-01-01T00:00:00Z). Provide both fromDateTime and toDateTime together, or omit both to default to the last 30 days.
toDateTime (string ISO 8601, optional) — Inclusive end of the activity window. Must be later than fromDateTime. Provide both together, or omit both to default to the last 30 days.

Example questions:

"What are the top objections raised by this account in the past 30 days?"
"Who are the key stakeholders and what are their goals?"
"What blockers are delaying the deal close?"
"Summarize the main themes from calls in August."

Limitations:

Does not return raw transcripts, message bodies, or activity lists.
Cannot be used for analytics across multiple accounts or workspace-level reporting.
Does not modify data or trigger workflows.
Does not support pagination or streaming.

2. ask_deal

Purpose: Answer a free-text, natural-language question about a single CRM deal or opportunity by analyzing the Gong activities linked to that deal within a specified time window.

When to use:

When you need summaries, insights, or themes about a single CRM deal or opportunity.
To understand deal progress, objections, risks, stakeholders, or next steps.
To extract high-level context from calls and messages linked to one CRM deal.

Parameters:

crmDeal (string, required) — The CRM deal or opportunity name (e.g. 'Acme Corp - Enterprise Q4') or direct CRM opportunity ID (e.g. '006EXAMPLE00001'). Name lookup uses exact matching.
question (string, required) — A natural-language question about the deal.
workspace (string, optional) — The Gong workspace name (e.g. 'Sales') or numeric workspace ID (e.g. '1234567890'). Required only when the organization has more than one workspace.
fromDateTime (string ISO 8601, optional) — Inclusive start of the activity window (e.g. 2026-01-01T00:00:00Z). Provide both fromDateTime and toDateTime together, or omit both to default to the last 30 days.
toDateTime (string ISO 8601, optional) — Inclusive end of the activity window. Must be later than fromDateTime. Provide both together, or omit both to default to the last 30 days.

Example questions:

"What objections has the prospect raised during recent calls?"
"Who are the key decision makers and what are their concerns?"
"What are the main blockers preventing deal closure?"
"Summarize the main themes from calls in the last 30 days."

Limitations:

Does not return raw transcripts, message bodies, or activity lists.
Cannot be used for analytics across multiple deals or workspace-level reporting.
Does not modify data or trigger workflows.
Does not support pagination or streaming.

3. generate_brief

Purpose: Create a comprehensive, structured brief about a CRM entity (account, deal, or contact) by analyzing Gong activities within a specified time period. Unlike the ask tools that answer specific questions, this tool generates summaries organized into multiple predefined categories such as key themes, stakeholders, risks, and next steps.

When to use:

When you need a comprehensive overview of an entity's recent activities.
To generate structured summaries for account or deal reviews, handovers, or executive briefings.
When you want insights across multiple categories rather than answers to a single specific question.

Parameters:

briefName (string, required) — The exact name of a published brief configured in the Gong workspace (e.g. 'Business Goals', 'Key Players'). This is a lookup key, not a free-text label.
entityType (string, required) — The CRM entity type: ACCOUNT, DEAL, or CONTACT.
crmEntity (string, required) — The entity name or ID. For ACCOUNT and DEAL, provide the name as it appears in the CRM (e.g. 'Acme Inc') or its CRM ID. For CONTACT, provide the direct CRM contact ID.
workspace (string, optional) — The Gong workspace name (e.g. 'Sales') or numeric workspace ID (e.g. '1234567890'). Required only when the organization has more than one workspace.
periodType (string, optional) — Predefined time period: LAST_7DAYS, LAST_30DAYS, LAST_90DAYS (default), or CUSTOM_RANGE.
fromDateTime (string ISO 8601, conditional) — Required when periodType is CUSTOM_RANGE.
toDateTime (string ISO 8601, conditional) — Required when periodType is CUSTOM_RANGE.

Supported entity types: ACCOUNT, DEAL, CONTACT

Supported period types: CUSTOM_RANGE, LAST_7DAYS, LAST_30DAYS, LAST_90DAYS

Limitations:

Does not return raw transcripts, message bodies, or activity lists.
Cannot be used for analytics across multiple entities or workspace-level reporting.
Does not modify data or trigger workflows.
Not intended for targeted single-question scenarios (use ask tools instead).

Known Limitations

All tools are read-only. The Gong MCP server does not support write operations of any kind.
Tool responses contain AI-synthesized insights, not deterministic data. Results are probabilistic and should not be used for exact numerical reporting.
Activities must exist within the specified time window for results to be generated. If no matching calls or messages exist for the given entity and date range, the tool will return an empty or minimal response.
Each tool invocation is single-shot. There is no support for pagination, streaming, or follow-up queries within a single tool call.
The server requires an active CRM integration in Gong. Accounts, deals, and contacts must be synced from the CRM to Gong for tools to find matching activities.

Support

Publisher: Gong.io Ltd.
Support page: https://help.gong.io/
Privacy policy: https://www.gong.io/privacy-policy
Terms of service: https://www.gong.io/terms-of-service
Contact: https://www.gong.io/contact-us

Actions

Gong	Gong brings deep revenue insights into your Copilot workflows, helping teams ask questions, generate briefs, and surface risks, objections, next steps, and stakeholder context from Gong AI OS data.

Gong

Operation ID:: InvokeServer

Gong brings deep revenue insights into your Copilot workflows, helping teams ask questions, generate briefs, and surface risks, objections, next steps, and stakeholder context from Gong AI OS data.