MCP ServerIntegrations

Gong Integration Setup

Connect your Gong sales call recordings to the Mind Reasoner MCP Server
Access Sales Call Transcripts

Connect Gong to pull sales call recordings and transcripts directly into your AI workflows. Create minds from customer conversations without manual file downloads.

What You’ll Get

When you connect Gong to your MCP server, you unlock 3 additional tools:

  • gong_list_calls - List call recordings with date filtering and metadata
  • gong_get_transcript - Get detailed transcripts with speaker names and emails
  • gong_get_call_details - Get participant details, topics, structure, and speaker stats

These tools work alongside the 8 core Mind Reasoner tools, giving you seamless access to your sales call data.

Prerequisites

Gong Account Requirements

To generate API credentials, you need Technical Administrator role in your Gong account. If you don’t have this role, contact your Gong administrator.

Choose Your Integration Approach

You have two options for working with Gong data:

Best for: AI-driven workflows, natural language access, no coding

Benefits:

  • Access Gong calls through simple AI commands
  • Automatic authentication and error handling
  • Seamless integration with Mind Reasoner mind creation
  • Works in Claude Desktop, Claude Code, and other MCP clients

Setup: Follow the steps below to add Gong credentials to your MCP server

Option 2: Direct Gong API Integration

Best for: Custom applications, specialized workflows, full API control

Benefits:

  • Complete control over API calls and data processing
  • Build custom integrations with other services
  • Implement specialized business logic

Resources:

MCP Server Integration Setup

1

Get Your Gong API Credentials

1. Log in to Gong

Navigate to app.gong.io

2. Access API Settings

Go to Settings → Ecosystem → API (or visit app.gong.io/company/api directly)

3. Generate Access Key

Click “Create” or “Generate New Access Key”

You’ll receive two credentials:

  • Access Key (similar to a username)
  • Access Key Secret (similar to a password)
Save Your Secret Immediately

The Access Key Secret is shown only once. Copy and save it securely immediately—you cannot retrieve it later. If you lose it, you’ll need to generate a new key pair.

2

Configure Your MCP Server

The configuration method depends on how you’re running the MCP server:

For Local/Stdio Mode (Claude Desktop, Claude Code CLI)

Add these environment variables to your configuration:

Environment Variables (.env)
$# Required - Mind Reasoner
>MIND_REASONER_API_KEY=your_mind_reasoner_key
>
># Optional - Gong Integration
>GONG_ACCESS_KEY={{GONG_ACCESS_KEY}}
>GONG_ACCESS_SECRET={{GONG_ACCESS_SECRET}}

For Hosted/HTTP Mode (Serverless, Custom Clients)

Pass credentials as HTTP headers with each request:

HTTP Headers
$# Required
>Authorization: Bearer YOUR_MIND_REASONER_KEY
>
># Optional - Gong
>X-Gong-Access-Key: {{GONG_ACCESS_KEY}}
>X-Gong-Access-Secret: {{GONG_ACCESS_SECRET}}
Per-Request Authentication (HTTP Mode)

In HTTP mode, you can provide different Gong credentials for each request. This is useful for multi-tenant applications or supporting multiple Gong accounts.

3

Restart Your MCP Client

If using Claude Desktop or Claude Code:

$# Restart Claude Desktop or Claude Code
># The Gong tools will be available automatically

No restart needed for HTTP/serverless mode—changes take effect immediately.

4

Verify the Connection

Test that Gong tools are available:

Ask your AI assistant:

"What Gong tools do you have access to?"

Expected response:

  • gong_list_calls
  • gong_get_transcript
  • gong_get_call_details

Try a test query:

"Show me my last 5 Gong calls from this week"

If you see call data, you’re all set!

Integration Active

Gong is now connected to your MCP server. You can access sales call transcripts directly through natural language commands in your AI assistant.

Authentication Details

How Gong Authentication Works

Gong uses HMAC-SHA256 signature-based authentication for API security:

  1. Each API request generates a signature using your Access Key Secret
  2. The signature is computed from: HTTP method + URL path + timestamp + request body
  3. The Access Key and signature are sent in the request headers
  4. Gong validates the signature to authenticate the request

This ensures that even if someone intercepts your Access Key, they cannot make valid API requests without your Access Key Secret.

Security Best Practices

Protect Your Gong Credentials

Your Gong credentials provide access to all sales call recordings and transcripts in your account.

Security checklist:

  • Never share Access Key Secret in messages or screenshots
  • Don’t commit credentials to version control (use .env files, add to .gitignore)
  • Use environment variables for local development
  • Rotate credentials periodically from Gong settings
  • If compromised, immediately revoke the key and generate a new one
  • Audit API key usage regularly in Gong settings

Troubleshooting

”Gong tools not available”

Possible causes:

  • Credentials not configured
  • Environment variables not loaded
  • MCP client not restarted after configuration

Solutions:

  1. Verify environment variables are set correctly
  2. Check for typos in variable names (GONG_ACCESS_KEY, GONG_ACCESS_SECRET)
  3. Restart your MCP client (Claude Desktop, Claude Code)
  4. Ask: “What MCP tools are available?” to see current tool list

”Authentication failed” or 401 errors

Possible causes:

  • Incorrect Access Key or Access Key Secret
  • Credentials expired or revoked
  • Signature generation error

Solutions:

  1. Verify credentials match exactly what’s shown in Gong settings
  2. Check for extra spaces or line breaks in credentials
  3. Generate a new Access Key pair in Gong settings
  4. Ensure you copied the Access Key Secret when it was first shown
  5. Verify your Gong account has API access enabled

”Rate limit exceeded” or 429 errors

Cause: Too many API requests to Gong in a short time period

Solutions:

  1. Wait for the time specified in the error message
  2. Reduce the frequency of calls list queries
  3. Use date filtering to reduce result set sizes
  4. Contact Gong support to discuss rate limit increases for your account

No calls returned from gong_list_calls

Possible causes:

  • No calls in the specified date range
  • User permissions don’t include call access
  • Gong account has no recorded calls

Solutions:

  1. Try a wider date range
  2. Verify your Gong account has recorded calls
  3. Check user permissions in Gong settings
  4. Test with no date filter to see if any calls are accessible

Example Workflows

Once Gong is connected, try these workflows:

List Recent Calls

"Show me my last 10 Gong calls from this month"

AI uses: gong_list_calls with date filtering

Create Mind from Call

"Create a mind from my Gong call with Sarah Johnson from last week"

AI workflow:

  1. Lists calls and finds the matching call
  2. Retrieves full transcript with gong_get_transcript
  3. Creates a new mind with create_mind
  4. Uploads transcript data
  5. Creates snapshot and waits for training

Analyze Call Patterns

"Get details about my top 3 longest calls this month,
 including speaker stats and topics discussed"

AI uses: gong_list_calls + gong_get_call_details for each call

Bulk Mind Creation

"Create minds for all participants in my Gong calls
 from the last 30 days who spoke for more than 10 minutes"

AI orchestrates:

  1. Lists all calls from last 30 days
  2. Gets call details for each to check speaker time
  3. Creates minds for qualifying speakers
  4. Uploads transcripts filtered to each speaker’s segments

Next Steps

🔧

Explore Gong Tools

Learn about all 3 Gong tools, their parameters, and detailed usage examples.

Gong Tools Reference →
🎥

Add More Integrations

Connect Fathom or Fireflies for access to even more meeting transcripts.

All Integrations →
💡

Complete Workflows

See end-to-end examples of creating minds from Gong data.

Quickstart Guide →

Official Documentation

For direct API integration or advanced use cases: