Claude connector guide

Gong MCP: how to connect Gong to Claude

Gong has an official MCP server for Claude, on any Gong plan. A Gong tech admin creates an MCP server integration in Gong’s Admin center. Then each rep adds Gong in Claude as a custom connector at https://mcp.gong.io/mcp and signs in. It’s read-only: Claude can ask about one account or deal, or generate a brief. Gong isn’t in Claude’s directory.

Updated . Part of our guide to Claude connectors for sales.

How to connect Claude to Gong

Steps 1 to 3 are for a Gong tech admin. Steps 4 and 5 are for each rep.

  1. Step 1: Create the integration

    tech admin

    In Gong, click Admin center in the left sidebar. On the Settings tab, click MCP under Ecosystem, open the MCP servers tab, and click New MCP server integration. Name it Claude.

  2. Step 2: Set the redirect and access

    tech admin

    Set the redirect URI to https://claude.ai/api/mcp/auth_callback. Under Registration type, Manual issues a client ID and secret, and Automatic needs neither. Under Authorization context, choose Personal access. Save.

  3. Step 3: Share the credentials

    tech admin

    With Manual registration, the Client ID and Client Secret appear in the integration details. Share them with the reps who’ll connect, the way you’d share any secret.

  4. Step 4: Add the custom connector

    each rep

    In Claude, go to Customize, then Connectors, and add a custom connector. Name it Gong, enter https://mcp.gong.io/mcp, and in the OAuth settings paste the Client ID and Client Secret.

  5. Step 5: Sign in to Gong

    Click Connect and sign in with your own Gong login. Claude can now use Gong’s three tools, limited to what you can already see in Gong.

What Claude can read and do in Gong

From Gong’s and Anthropic’s own docs, as of October 20, 2026.

Reads

  • Ask account: answers questions about a single account
  • Ask deal: answers questions about a single deal
  • Generate brief: key themes, stakeholders, risks, and next steps

Does

  • None. The integration is read-only, so Claude can’t create, update, or delete anything in Gong.

Limits to know

  • Private calls are left out of all results.
  • Answers come through Gong’s three tools, one account or deal at a time. The MCP server doesn’t hand over raw call transcripts.
  • If no matching integration exists in Gong, the rep sees a message that the tool isn’t authorized for the company.

Three ways reps use Claude with Gong

Copy the prompt, swap in your own deal, and run it with Gong toggled on. The results are illustrations with a made-up company, Acme.

  • What every call on a deal adds up to

    One call tells you what was said. Asking across the deal tells you what keeps coming up.

    You

    Ask Gong about the Acme deal: across every call so far, what are the buyer’s top three priorities, who has joined each call, and which objections keep coming back?

    ClaudeExample

    Acme across 4 calls

    • Priorities: forecast accuracy, ramp time, and CRM hygiene
    • On calls: Jordan (all 4), Priya (calls 3 and 4)
    • Keeps coming back: rollout effort
  • A brief before the next call

    Gong’s brief tool gives Claude the themes, people, risks, and next steps. Claude turns that into your prep.

    You

    Generate a Gong brief for the Acme deal, then turn it into a one-page prep: stakeholders and where they stand, open risks, and the next steps we agreed but haven’t done.

    ClaudeExample

    Acme call prep

    • Jordan: champion. Priya: cautious.
    • Risk: no budget owner named yet
    • Agreed, not done: send the rollout plan
  • Find who’s missing

    Single-threaded deals hide in plain sight. Ask who hasn’t been on a call yet.

    You

    Ask Gong about the Acme account. Has anyone from finance or procurement joined a call? If not, who did our champion say signs off?

    ClaudeExample

    Finance and procurement on Acme

    • No one from finance has joined a call
    • Jordan said Sam Ortiz, CFO, signs off
    • Next step: invite Sam to the pricing call

Safety and permissions

Claude inherits your Gong permissions. It can’t see or change anything you couldn’t. These are the settings worth checking before a team rolls it out.

  • Personal access means each rep signs in with their own Gong login and sees only what Gong already lets them see.
  • Read-only by design: no tool on the Gong MCP server can change Gong data.
  • Private calls never show up in results.
  • Manual registration limits connections to the client where you installed the credentials. Treat the client secret like a password.
  • Gong asks for a separate integration per AI tool, so you can turn one off without touching the others.

Claude alone vs with Arrows

Claude can drive one tool when one rep asks. Arrows drives the whole team’s stack on every deal, with no prompt. Arrows connects to Gong directly and reads the full call transcript, even for a call that never syncs to your CRM.

Claude with the Gong connector

Who starts the work
A rep types a prompt.
How many deals
The one the rep is asking about.
What it follows
That rep’s prompt.
Which tools
Gong, plus whatever else that rep has connected.
Who decides what can happen
Each person’s tool permissions: Always allow, Needs approval, or Blocked.
After the call
A rep asks Gong questions in Claude. Nothing gets written anywhere.
A new stakeholder joins
It shows up if someone thinks to ask.

Arrows

Who starts the work
Arrows starts on its own when something happens on a deal. No prompt.
How many deals
Every deal in the pipeline.
What it follows
Your team’s playbook and each deal’s gameplan.
Which tools
Your team’s CRM, email, call recorder, and docs, through MCP.
Who decides what can happen
Leaders set Off, Ask first, or Allow for every tool, for the whole team.
After the call
Arrows reads the full transcript from Gong and drafts the follow-up and CRM update for the rep to approve.
A new stakeholder joins
Arrows enriches the person and updates the CRM.

Arrows is its own product, not part of Claude. Your reps can keep using Claude alongside it.

Agent kickoff

Every tool. Every deal. No prompts.

An Agent Architect connects your stack and sets what Arrows can do in each tool. Then Arrows does the follow-through on every deal, and your reps approve what matters.

Book an agent kickoff
Tool permissionsExample settings
  • GongRead call transcripts
  • HubSpotDeal and contact updates
  • SalesforceNot used by this team
  • GmailFollow-up emails
  • GranolaRead meeting notes

Gong and Claude: common questions

Does Gong have an MCP server?

Yes. Gong has an official MCP server at https://mcp.gong.io/mcp, with native integrations for Claude, ChatGPT, and Microsoft Copilot. It’s available on any Gong plan, and a Gong tech admin sets it up.

How do I connect Gong to Claude?

A Gong tech admin creates an MCP server integration in Admin center (Settings, then MCP under Ecosystem), with the redirect URI https://claude.ai/api/mcp/auth_callback and Personal access. Each rep then adds a custom connector in Claude with the Gong server URL and the integration’s credentials, and signs in.

Is Gong in Claude’s connector directory?

Not as of October 2026. Gong connects as a custom connector instead. Once it’s connected it works the same way as a directory connector.

What can Claude do with Gong data?

Claude can use three read-only tools: ask account, ask deal, and generate brief, which returns key themes, stakeholders, risks, and next steps. It can’t create, update, or delete anything in Gong, and private calls are excluded.

Can Claude read Gong call transcripts?

Not as raw transcripts through the MCP server. Claude gets answers and briefs that Gong builds from your calls. Arrows reads full transcripts from Gong directly.

Who can set up the Gong MCP server?

A Gong tech admin. Each rep who connects needs a paid Gong seat, and Collaborator accounts can’t connect.