Skip to content

Sales Enablement

Gong MCP connector

The Gong connector brings your recorded calls, transcripts, scorecards, coaching activity and CRM records into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can ask about conversations and pipeline activity inside their own Gong access.

  • How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Gong to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Gong once

  1. Open Connections, choose Add connection, and pick Gong.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Supply your own Gong app, then approve. Gong needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

gong
Gong
Autobound
Interseller
Lemlist
Outreach
Smartlead
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect Gong to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Gong to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Gong to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Gong to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Gong through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Sales

    Catch up on a call you missed

    Ask for the transcript and outcome of yesterday's discovery call with a prospect and get the key moments summarized before your follow-up.

  • Sales Enablement

    See which reps need coaching this week

    Pull scorecards and coaching activity across the team, spot who is behind on reviews, and plan sessions from real calls instead of guesswork.

  • Revenue Operations

    Report on call activity by period

    Build activity summaries by week or quarter for each rep, then compare talk time and call volume against what the pipeline needs.

  • Sales Management

    Check what an account has said lately

    Ask for every Gong call tied to an account, with outcomes and the people involved, before a renewal conversation or a forecast review.

  • Customer Success

    Log and organize customer calls

    Add a call to Gong after an onboarding session, link the right CRM records to it, and decide who on the team can see it.

  • Marketing

    Hear what prospects say about competitors

    Search recent call transcripts for competitor and pricing mentions, and turn what buyers actually said into messaging and content decisions.

Try asking

  • “Summarize this week's Gong calls for the EMEA team.”
  • “Which call outcomes came up most in October?”
  • “Pull the transcript for yesterday's renewal call with Acme.”

See all 61 Gong tools below

AI tools

Gong tools for your AI agents

61 tools are ready to call through Elaichi's MCP endpoint the moment you connect Gong, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Gong gets you

6 screens from the product, each doing one job for your Gong account.

The agent

Ask about Gong calls, get real answers.

Plain language questions run against live Gong calls, transcripts and scorecards.

  • calls
  • transcripts
  • scorecards
  • call outcomes

Ask Elaichi to work across your apps.

Summarize this week's Gong calls for the EMEA team.

Which call outcomes came up most in October?

Pull the transcript for yesterday's renewal call with Acme.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Gong here.

One org-wide MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

61 Gong tools ready without custom code.

Calls, transcripts, users, workspaces, scorecards and activity aggregates are covered on connect.

  • List all Gong users
  • Get single Gong user by ID
  • List all Gong workspaces
  • List all Gong calls
ElaichiTools
Tool Action Description
List all Gong users List List all of the company's users. When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:users:read'.
Get single Gong user by ID Get Retrieve a specific user. When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:users:read'.
List all Gong workspaces List List all company workspaces including their details.
List all Gong calls List List calls that took place during a specified date range. When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:calls:read:basic'.
Get single Gong call by ID Get Retrieve data for a specific call. When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:calls:read:basic'.

Toolboxes

Every team gets its own Gong toolbox.

Curate one toolbox for enablement, another for sales ops, each scoped separately.

  • Sales
  • Sales enablement
  • Sales operations
  • Revenue leadership
ElaichiToolboxes
Name Source template Tools Created

Sales toolbox

Gong · calls and call outcomes

Gong starter 18 Mar 4, 2026

Sales enablement toolbox

Gong · scorecards and coaching

9 Mar 2, 2026

Sales operations toolbox

Gong · users and workspaces

24 Feb 27, 2026

Revenue leadership toolbox

Gong · activity aggregates by period

Gong starter 6 Feb 19, 2026

Customer success toolbox

Gong · renewal call transcripts

31 Jan 30, 2026

Marketing toolbox

Gong · call transcripts and objections

12 Jan 22, 2026

Shared connections

Teammates use Gong without seeing a credential.

The connections table shows who connected each Gong account and its shared teams.

  • Sales EMEA
  • Sales AMER
  • Enablement
  • Revenue ops
ElaichiConnections
Connection Scope Status Access
GO

Gong (Sales EMEA)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
GO

Gong (Sales AMER)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
GO

Gong (Enablement)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
GO

Gong (Revenue ops)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
GO

Gong (Customer success)

Connected by Clara Nowak

Personal • Active Not shared
GO

Gong (Leadership)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Answer who read which Gong call.

Append-only log records when, who, what happened, type and resource touched.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Gong Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Gong Calls Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Gong Calls List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires, a Gong digest ships.

Six steps fetch calls, group them, draft a digest, wait for approval, post back.

Gong digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch calls

    Gong

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Gong

    Queued

Collections and dashboards

Gong call health, computed on a schedule.

Four metrics, fourteen days of calls created and a team breakdown, no model involved.

Gong health

Refreshed 4 minutes ago · every 15 minutes · from the calls collection

Live

Calls

1,284 ↓ 12%

Transcripts

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Calls created

Last 14 days

By team

Share of activity

Sales EMEA 34%

Sales AMER 27%

Enablement 21%

Revenue ops 18%

FAQ

Frequently asked questions

How do I connect Gong to Claude?

Connecting Gong takes two steps. First, register an OAuth application inside Gong and enter its client ID and secret once in Elaichi, then sign in to Gong with your own account when Elaichi asks. Second, in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Only the first person setting up Gong handles the client ID and secret, and nobody else on the team needs to see them.

Does Gong work with ChatGPT and Cursor as well as Claude?

Yes. Once Gong is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Gong once and every client you use picks it up.

What can an AI agent actually do with my Gong data?

With Gong connected, an agent can find calls by account, rep or date, read transcripts and call outcomes, and summarize what was said. It can pull activity summaries for a period, review scorecards and coaching, list users and workspaces, add a new call, manage who has access to a call, and create or look up the CRM records linked to calls. Because Gong offers many actions, short concrete asks like "summarize Friday's call with Acme" work better than long paragraphs.

Does connecting Gong give the AI access to every call in the workspace?

No. The AI works inside the Gong permission profile of the person who signed in, so it sees only the calls, workspaces and transcripts that person can already open in Gong. Elaichi can narrow that access further with restrictions, but it can never widen it beyond what Gong itself allows that person.

Can my team share one Gong connection?

Yes. One person sets up Gong in Elaichi and shares the connection with a team, so nobody else touches the client ID, the secret or any other credential. Each teammate still signs in to Elaichi as themselves, so every Gong call lookup or transcript request in the audit log carries their own name.

Can I stop an agent from deleting or changing things in Gong?

Yes. Restrictions on the Gong connector apply per action, so you can allow reading calls and transcripts while blocking the ability to create calls, change call access or add CRM records. A blocked action is never shown to Claude, ChatGPT or any other client, so no prompt can reach it.

What happens to a Gong connection when someone leaves?

When a person is offboarded in Elaichi, their access to Gong through every AI client ends immediately. If they had shared a Gong connection with the team, it keeps working for everyone else. Disconnecting Gong once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

Put Gong in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.