# 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.

Source: https://elaichi.ai/connectors/gong/

## Facts

| | |
| --- | --- |
| Application | Gong |
| Category | Sales Enablement |
| AI tools | 61 |
| Authentication | Connects over OAuth |
| Needs your own OAuth app | Yes |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. 61 tools is past the 30-tool threshold, so clients use `search_tools` and `execute_tool` |

## What you can ask once Gong is connected

- 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.

## Connect Gong in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Gong.
2. Optionally set Share with, 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.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Gong tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Connect Gong to Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
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

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

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

## Connect Gong to any MCP client

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

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

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Gong tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Gong through Elaichi

### Catch up on a call you missed

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

### See which reps need coaching this week

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

### Report on call activity by period

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

### Check what an account has said lately

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

### Log and organize customer calls

Customer Success. 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.

### Hear what prospects say about competitors

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

## 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.

## All 61 Gong tools

Every tool below is callable through https://api.elaichi.ai/mcp once Gong is connected, subject to the toolbox it is in and the restrictions on the caller.

- **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'.
- **Create a Gong call** (Create). When using this endpoint, either provide a downloadMediaUrl or use the returned callId in a follow-up request to /v2/calls/{id}/media to upload the media file.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:calls:create'.
- **Create a Gong activity aggregate by period** (Create). Retrieve aggregated activity statistics for Gong team members grouped by a specified time period. Returns one record per user per period with counts of calls, listens, comments, and other tracked actions. Requires from_date, to_date, and aggregation_period.
- **List all Gong activity aggregates** (List). Lists the activity of multiple users within the Gong system during a defined period. Given the period, this endpoint returns multiple records, one for each user, with an applicable activity during the period. Each record includes statistics about the user's activity.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:stats:user-actions'.
- **List all Gong activity scorecards** (List). Retrieve all the answers for the scorecards that were reviewed during a specified date range, for calls that took place during a specified date range, for specific scorecards or for specific reviewed users.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:stats:scorecards'.
- **List all Gong all permission profiles** (List). Returns a list of all permission profiles.

The listing is in the alphabetical order of the profile names.
- **Create a Gong assign cool off override** (Create). Use this endpoint to assign a number of prospects to a flow regardless of the cool off status. Prospects can be contacts or leads in your CRM.

Generate a list of comma separated CRM Ids of the prospects you want to add to a flow. The flowInstanceOwnerEmail parameter is the email address of the Gong user who set up the flow instance and owns the flow to-dos.

You can assign up to 100 prospects to a flow in a single request.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:flows:write'.
- **List all Gong call outcomes** (List). List available call outcomes defined in Gong, used to categorize the result of a call (e.g., "Connected", "No Answer").
- **Create a Gong calls extensive** (Create). Lists detailed call data for calls that took place during a specified date range, have specified call IDs, or were hosted by specified users. Requires scope 'api:calls:read:extensive'. Clients requesting media download URLs should also have scope 'api:calls:read:media-url'.
- **Create a Gong calls transcript** (Create). Returns transcripts for calls that took place during the specified date period. If call IDs are specified, only transcripts for calls with those IDs that took place during the time period are returned.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:calls:read:transcript'.
- **Delete a Gong calls users accese by ID** (Delete). Remove individual user access from calls in Gong. Only revokes access previously granted via the API; access granted through other means (e.g., sharing) remains unchanged. Returns a success response. Requires a request body specifying the call ids and user ids to revoke.
- **Create a Gong calls users accese** (Create). Returns a list of users who have received individual access to calls through the API. Does not cover users who have access for other reasons (e.g., sharing recipients or permission profiles). Requires scope 'api:call-user-access:read'.
- **Update a Gong calls users accese by ID** (Update). Give individual users access to calls.

If a user already has access (perhaps the call was shared with them, or they have access through their permission profiles) the request will have no effect.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:call-user-access:write'.
- **List all Gong coachings** (List). List all of the coaching metrics of a manager.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:coaching:read'.
- **Update a Gong content shared by ID** (Update). Report a content-share engagement event in Gong, recording when a user shares content (e.g., a contract) with external participants. The event appears in Gong's activity timeline. Returns a registration response on success. Requires a ContentSharedEvent request body.
- **Update a Gong content viewed by ID** (Update). Report a content-viewed engagement event in Gong, recording when an external participant (e.g., a prospect) views a piece of content such as a contract. The event appears in Gong's activity timeline. Returns a registration response on success.
- **List all Gong CRM entities** (List). List Gong CRM entities by id for development-phase verification that uploaded objects were processed correctly. Returns a JSON object keyed by CRM id with entity field values, or null when an id is not found. Required: integrationId, objectType, objectsCrmIds. Max 100 objects per request.
- **Create a Gong CRM entity** (Create). Insert, update, or delete a CRM entity (ACCOUNT, CONTACT, DEAL, LEAD, BUSINESS_USER, or STAGE) in Gong by uploading an LDJSON file. Processing is asynchronous; a 201 response confirms upload and returns a request id pollable via the request-status endpoint. Required: integration_id, object_type, client_request_id, and data_file.
- **List all Gong CRM entity schemas** (List). List CRM entity schema fields in Gong for a given object type. Returns field definitions including name, label, type, and isDeleted. Required: integration_id, object_type (ACCOUNT, CONTACT, DEAL, or LEAD; case-sensitive).
- **Create a Gong CRM entity schema** (Create). Upload or update the field schema for a Gong CRM entity type (Account, Contact, Deal, or Lead). Returns a schema update response on success. Required: integration_id, object_type, and a JSON array of field definitions in the request body. All existing fields must be included in each update; omitting a field causes an error.
- **Update a Gong CRM integration by ID** (Update). Creates your CRM integration with Gong. Returns an integrationId, which should be used in requests to the CRM API to enable correct association of CRM data. Multiple CRM integrations are not supported. To create a new integration, delete the old one first (DELETE /v2/crm/integrations). When accessed using a bearer token, this endpoint requires the 'api:crm:integration:register' scope.
- **List all Gong CRM integrations** (List). Retrieve the Generic CRM integration details configured via PUT /v2/crm/integrations. Only one integration can exist at a time.
- **Delete a Gong CRM integration by ID** (Delete). Asynchronously deletes a CRM integration and all its associated CRM objects (Accounts, Contacts, Deals, Leads, and Users). Use the clientRequestId to check the status of the delete request via the /request-status endpoint. A status of DONE indicates successful deletion (may take up to 24 hours). When accessed using a bearer token, this endpoint requires the 'api:crm:integration:delete' scope.
- **List all Gong CRM request status** (List). Get the status of an asynchronous Gong CRM request (entity upload or integration deletion). Returns the current status (PENDING, IN_PROGRESS, DONE, or FAILED) and any processing errors. Required: integration_id, client_request_id.
- **Update a Gong customer engagement action by ID** (Update). Push a custom engagement action event into Gong to display on the activity timeline when external participants engage with content (e.g., a contract is signed). Returns a confirmation response on success. Duplicate events return a 409 conflict.
- **List all Gong data privacy data for email addreses** (List). Shows the elements in the Gong system that reference the given email address. Given an emails address, this endpoint returns details of all calls and email messages that reference this address, and any leads or contacts with this email address.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:data-privacy:read'.
- **List all Gong data privacy data for phone numbers** (List). Shows the elements in the Gong system that reference the given phone number. Given a phone number, this endpoint returns details of any leads or contacts with this phone number and their associated calls and email messages.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:data-privacy:read'.
- **Create a Gong data privacy erase data for email addrese** (Create). Delete all Gong data associated with a given email address, including calls, email messages, leads, and contacts that reference it. Deletion is asynchronous and may take several hours. Required: emailAddress.
- **Create a Gong data privacy erase data for phone number** (Create). Delete all Gong leads, contacts, associated emails, and calls matching a given phone number. Deletion is asynchronous and may take several hours. Required: phoneNumber (must start with + followed by country code).
- **Create a Gong digital interaction** (Create). When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:digital-interactions:write'.
- **List all Gong entities ask entities** (List). Returns the answer to a question about a specified entity. The answer is generated from calls or emails associated with the entity within the specified time period. A maximum of 60 calls and 500 emails are used to answer the question. A call to this API consumes Gong credits according to the number of emails and calls used to generate the answer.
Supported entities are Accounts, Deals, Contacts, or Leads that exist in your CRM.
The response includes:

The answer
Details of emails and calls used to generate the answer

Required authorization scope: 'api:ai-ask:read'. Get AI-generated answers to natural language questions about entities (Accounts, Deals, Contacts, Leads).
- **List all Gong entities get briefs** (List). Get a brief for an account, deal, contact, or lead that exists in your CRM. Briefs are set up in the Gong Agent Studio and you must provide the name of the brief you want to generate. A call to this API consumes Gong credits according to the number of emails and calls used to generate the brief.
The brief is generated from calls or emails associated with the entity within the specified time period.
The response includes:

The brief
Details of emails and calls used to generate the brief

Required authorization scope: 'api:ai-briefer:read'. Get AI-generated briefs for entities (Accounts, Deals, Contacts, Leads) using briefs configured in Gong.
- **List all Gong flows** (List). List Gong Engage flows including company, personal, and shared flows for a given user. Returns flow objects with id, name, and visibility type. Required: flowOwnerEmail.
- **List all Gong flows folders** (List). Engage flow folders have the following visibility types:

Company: visible to everyone in the company, can only be edited by users with edit permissions.

Personal: reps can set up their own flow folders which are only available to them.

Shared: reps can share a flow folder with other reps. Those reps can then add flows to the flow folder.

This endpoint returns all company flow folders, together with personal flow folders and flow folders shared with the user specified in the flowEmailOwner parameter.

When accessed through a Bearer token authorization method, use the 'api:flows:read' scope.
- **Create a Gong flows prospect** (Create). Get the Gong Engage flows assigned to the given crmProspectsIds.

When querying by crmProspectsIds, only open (Pending/Running/Paused) flows are returned.

Alternatively this endpoint can be used to get the flows assigned to prospects by the given flowInstanceIds.

When querying by flowInstanceIds, all flows including finished ones are returned.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:flows:read'.
- **Create a Gong integration setting** (Create). When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:integration-settings:write'.
- **Create a Gong integration status** (Create). When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:meetings:integration:status'.
- **List all Gong library folder contents** (List). Given a folder id, this endpoint retrieves a list of calls in it.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:library:read'.
- **List all Gong library folders** (List). Use this endpoint to retrieve a list of public library folders. We do not allow retrieval of either private or archived folders.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:library:read'.
- **List all Gong logs** (List). List log entries that took place during a specified time range.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:logs:read'.
- **Update a Gong media by ID** (Update). Adds a call media, recorded by a telephony system (PBX) or other media recording facility. Gong accepts call recordings in various audio and video file formats, including WAV, MP3, MP4, MKV and FLAC. If uploading a dual-channel (stereo) file separated by speaker, make sure to specify which channel correspondsto the company team member (rep) in the parties/mediaChannelId parameter of the Add New Call operation.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:calls:create'.
- **Delete a Gong meeting by ID** (Delete). When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:meetings:user:delete'.
- **Update a Gong meeting by ID** (Update). When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:meetings:user:update'.
- **Create a Gong meeting** (Create). When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:meetings:user:create'.
- **List all Gong permission profile users** (List). Returns a list of all users whose access is controlled by the given permission profile.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:users:read'.
- **Create a Gong prospects assign** (Create). Use this endpoint to assign a number of prospects to a flow. Prospects can be contacts or leads in your CRM.

Generate a list of comma separated CRM Ids of the prospects you want to add to a flow. The flowInstanceOwnerEmail parameter is the email address of the Gong user who set up the flow instance and owns the flow to-dos.

You can assign up to 100 prospects to a flow in a single request.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:flows:write'.
- **Create a Gong prospects bulk assignment** (Create). Use this endpoint to asynchronously submit a bulk assignment of prospects to a flow. Prospects can be contacts or leads in your CRM.

You can assign up to 50 prospects to a flow in a single request.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:flows:write'.
- **Get single Gong prospects bulk assignment by ID** (Get). Use this endpoint to get the results of a bulk assignment of prospects to a flow.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:flows:read'.
- **Create a Gong prospects unassign flows by CRM ID** (Create). This endpoint lets you remove a specific prospect from the flows they are assigned to.

To remove the prospect from all flows they are assigned to, send the crmProspectId only.

If you want to remove the prospect from a specific flow, get the flow id from the /v2/flows/prospects endpoint and include the crmProspectId and flowId in the request.

The Ids of the flows the prospect was successfully removed from are returned in the response.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:flows:write'.
- **Create a Gong prospects unassign flows by instance ID** (Create). Unassign prospects from Gong flows by flow instance id. Returns the flow instance ids from which prospects were successfully removed. Requires a list of flow instance ids (up to 200 per request).
- **Get single Gong settings history by ID** (Get). Retrieve a specific user's settings history.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:users:read'.
- **List all Gong settings scorecards** (List). Retrieve all scorecards within the Gong system.
- **List all Gong settings trackers** (List). Retrieves details of all keyword trackers in the system or in a given workspace.

When accessed through a Bearer token authorization method, this endpoint requires the 'api:settings:trackers:read' scope.
- **List all Gong stats interactions** (List). Returns interaction stats for users based on calls that have Whisper turned on.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:stats:interaction'.
- **Create a Gong task** (Create). Retrieves a list of Engage tasks assigned to a specific user. Supports filters for task type, action, and status. Results include detailed metadata such as ownership, creation/due dates, associated contacts, flows, accounts, and opportunities. Requires scope 'api:tasks:read'.
- **Update a Gong task by ID** (Update). Use this endpoint to update the status or due date of an existing Engage task.
The task status can be changed to OPEN, DONE, or DISMISSED.
This is useful for managing task workflows such as marking tasks complete or rescheduling them based on user actions or system events.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:tasks:write'.
- **Create a Gong users extensive** (Create). List multiple Users.

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:users:read'.