Integrations/GongLast updated
Integration

Gong MCP and AI integration that searches your calls and answers next to your CRM

Coworker's Gong AI integration searches your Gong call transcripts and reads call details, including topics, trackers, speakers and Gong's own call brief, then answers next to your CRM, Slack and support data. Through Coworker MCP, the same Gong data works in Claude, ChatGPT and Cursor. People only see calls they hosted or attended, or that Gong shares with them.

How Gong context reaches your AI tools

Coworker brings Gong together with the rest of your tools in OM2, its organizational memory, then answers in Coworker's own apps, or in Claude, ChatGPT and Cursor through Coworker MCP.

Use cases

What revenue teams do with Gong AI and Coworker

Coworker searches your Gong calls and answers next to your CRM, support tickets, Jira and Slack.

Sales leaders

What buyers are saying

Ask which calls this month mentioned a competitor and get the transcripts searched, with quotes from each call.

Account executives

Prep in one question

Get the topics, highlights and speakers from the last three calls with an account, next to the CRM record.

Enablement

Scorecards and libraries

Read your scorecard templates and the answered scorecards you are part of, and list the calls in a Gong library folder.

Product

Call evidence for a request

Search calls for a feature or a pain point, see which customers raised it and what they said, then share it in Slack or a doc.

Sales ops

Gong kept in sync

Agents schedule a meeting in Gong, log a call record, or push account, opportunity and contact details into Gong's CRM data.

More for revenue teams: Coworker for sales teams, and our guide to enterprise MCP.

Setup

Live in minutes

1

An admin connects Gong

An admin connects Gong once for the workspace and chooses who can use it.

2

People see their own calls

Each person sees the calls they hosted or attended, transcripts follow Gong's sharing settings, and private calls stay private.

3

Decide what needs approval

Changes in Gong need the person's own Gong seat. Tick Require approval for Gong on an agent and each change waits for someone to approve it.

Powered by the Coworker Platform / OM2

Every model needs the right context.

Gong's MCP server can only see what lives in Gong. OM2 connects your calls to the support tickets, Jira issues, Slack threads, and docs around them in one permission-aware knowledge graph, so Claude, ChatGPT, or Cursor starts every task with your customers, projects, and decisions already loaded.

customer14s ago

Mosaic Financial

Series B fintech · $3.1M ARR · 47 seats

24linked
12sources
0.8ssynth
SOC 2 Type II auditPriya NambiarEnterprise onboardingCustomer Success#mosaic-impl
LiveOnboarding kickoff call with Priyavia Gong
Security and governance

Enterprise-grade security, from day one

SOC 2 Type II

Audited annually, report on request

Hosted locally

Your memory stays in your region. Open-source models run in the US.

Isolated per company

In our cloud or your VPC

Never trains on your data

No model provider, closed or open source

Your permissions, enforced

The access already set in Salesforce, Slack, Jira and Drive

Also included

GDPRCASA Tier 2Node-level permissions at query timeEvery fact traceable to its sourceSSO and SAMLAES-256 at rest, TLS 1.2+ in transitRegional data residency

FAQ

Frequently asked questions

Coworker is a context layer for enterprise AI. It connects 50+ work tools, builds a permission-aware company graph called OM2, and runs agents that act across those tools, inside Coworker or in Claude, ChatGPT and Cursor through Coworker MCP.

Gong's own MCP server is a good fit if you only need Gong in Claude, ChatGPT or Microsoft Copilot: it offers three tools to ask about an account, ask about a deal and generate a brief. Coworker MCP adds Gong transcript search and call details in the same connection as Salesforce, Slack, Jira and the rest of Coworker's 50+ connectors.

Gong's AI features work on your calls inside Gong, and Gong can pull outside data into them over MCP. If your reps live in Gong, they are a strong fit. Coworker is for questions that need calls next to support tickets, Jira, Slack and docs through 50+ connectors. See Coworker vs Gong.

Call transcripts, searchable by keyword, attendee and date, and call details: participants, topics, trackers, points of interest, Gong's brief, outline and highlights, and per-speaker stats. It also reads scorecards and library folders. Gong is one of the sources Coworker's organizational memory draws on.

Ask in plain English and Coworker picks the search terms, then matches them across transcripts, call titles, attendees and summaries, filtered by attendee and date.

Each person sees the calls they hosted or attended, and the scorecards they reviewed or were reviewed on. Transcript search follows each call's sharing setting in Gong, and private calls are never shown.

People with a Gong seat can have their agents schedule meetings in Gong, log call records, and add or update accounts, opportunities and contacts. Recordings, scorecards and deal boards stay exactly as they are.

Yes. An agent can run on a schedule or when someone asks in Slack. For example, a Friday digest of competitor mentions from the week's calls, posted to Slack.

Coworker does. OM2, Coworker's organizational memory, is a knowledge graph built from the work tools a company connects, such as Gong calls, Salesforce, Slack, Jira and Google Drive. Coworker agents answer and act from that graph, and every stored fact keeps the access controls of the tool it came from.

Sources for Gong's AI, as of October 14, 2026: Gong AI agents, Gong MCP server, Gong MCP client.

Connect Gong in minutes

Connect your Gong data and watch agents go to work in minutes.