Gong MCP connector
The Gong connector brings your recorded calls, transcripts, scorecards, coaching activity and CRM records into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can ask about conversations and pipeline activity inside their own Gong access.
- Connects over OAuth
- Free 14-day trial
- No credit card
Summarize this week's Gong calls for the EMEA team.
Working in Gong with Elaichi
-
List all Gong users
-
Get single Gong user by ID
-
List all Gong workspaces
How to connect Gong to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Gong MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Gong MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Gong MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Gong MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Gong MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Gong to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
What teams do with Gong through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Gong is logged.
-
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.”
What connecting Gong gets you
6 screens from Elaichi, each doing one job for your Gong account.
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, Cursor or Microsoft Copilot
The agent
Ask about Gong calls, get real answers.
Plain language questions run against live Gong calls, transcripts and scorecards.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Gong here.
One org-wide MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
61 Gong tools ready without custom code.
Calls, transcripts, users, workspaces, scorecards and activity aggregates are covered on connect.
Toolboxes
Every team gets its own Gong toolbox.
Curate one toolbox for enablement, another for sales ops, each scoped separately.
Shared connections
Teammates use Gong without seeing a credential.
The connections table shows who connected each Gong account and its shared teams.
Audit log
Answer who read which Gong call.
Append-only log records when, who, what happened, type and resource touched.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Gong digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch calls
Gong
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Gong
Queued
Automations
A schedule fires, a Gong digest ships.
Six steps fetch calls, group them, draft a digest, wait for approval, post back.
Gong health
Refreshed 4 minutes ago · every 15 minutes · from the calls collection
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%
Collections and dashboards
Gong call health, computed on a schedule.
Four metrics, fourteen days of calls created and a team breakdown, no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Gong
All three can connect Gong to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Gong tools | Allow or restrict single Gong tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Gong call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
No tools match your search.
Questions, answered
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, Microsoft Copilot, 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 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 restricting the ability to create calls, change call access or add CRM records. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot and every other client at the same time.
Does the Gong MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Gong is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Gong?
Yes. Both let Claude, ChatGPT or Cursor use Gong. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Gong call.
How is Elaichi different from Composio for Gong?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Gong: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Gong in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot