Gong MCP Server

An MCP (Model Context Protocol) server that provides access to your Gong.io data. Query calls, transcripts, users, keyword trackers, and more directly from Claude or any MCP-compatible client.

Tools Quick Reference

Prerequisites

• Node.js 18+ or Docker
• Gong API credentials (Access Key and Secret)

1. Log into Gong as an admin
2. Go to Company Settings → Ecosystem → API
3. Click Create API Key
4. Save both the Access Key and Secret (the secret is only shown once)

Option 1: npx (no install required)

npx gongio-mcp

Option 2: Global npm install

npm install -g gongio-mcp
gongio-mcp

Option 3: From source

git clone https://github.com/JustinBeckwith/gongio-mcp.git
cd gongio-mcp
npm install
npm run build
node dist/index.js

Option 4: Docker (build locally)

git clone https://github.com/JustinBeckwith/gongio-mcp.git
cd gongio-mcp
docker build -t gongio-mcp .
docker run --rm -i \
  -e GONG_ACCESS_KEY=your-access-key \
  -e GONG_ACCESS_KEY_SECRET=your-secret-key \
  gongio-mcp

Set your Gong credentials as environment variables:

export GONG_ACCESS_KEY="your-access-key"
export GONG_ACCESS_KEY_SECRET="your-secret-key"

Or pass them inline:

GONG_ACCESS_KEY=your-key GONG_ACCESS_KEY_SECRET=your-secret npx gongio-mcp

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

Using npx:

{
  "mcpServers": {
    "gong": {
      "command": "npx",
      "args": ["gongio-mcp"],
      "env": {
        "GONG_ACCESS_KEY": "your-access-key",
        "GONG_ACCESS_KEY_SECRET": "your-secret-key"
      }
    }
  }
}

Using Docker:

{
  "mcpServers": {
    "gong": {
      "command": "docker",
      "args": ["run", "--rm", "-i",
               "-e", "GONG_ACCESS_KEY",
               "-e", "GONG_ACCESS_KEY_SECRET",
               "gongio-mcp"],
      "env": {
        "GONG_ACCESS_KEY": "your-access-key",
        "GONG_ACCESS_KEY_SECRET": "your-secret-key"
      }
    }
  }
}

Claude Code

Using npx:

claude mcp add gong -e GONG_ACCESS_KEY=your-key -e GONG_ACCESS_KEY_SECRET=your-secret -- npx gongio-mcp

Using Docker (after docker build -t gongio-mcp .):

claude mcp add gong -e GONG_ACCESS_KEY=your-key -e GONG_ACCESS_KEY_SECRET=your-secret -- docker run --rm -i -e GONG_ACCESS_KEY -e GONG_ACCESS_KEY_SECRET gongio-mcp

Available Tools

List calls with optional date range and workspace filters. Returns minimal call metadata (ID, title, date, duration).

Parameters:

Get the URL, timing, direction, scope, system, and other metadata for one call. Faster than get_call_summary when you only need call metadata.

Parameters:

Get an AI-generated summary including brief overview, key points, topics, action items, and detailed outline. This is the recommended way to understand a call — use get_call_transcript only if you need exact quotes.

Parameters:

Get the raw transcript with speaker attribution. Transcripts are paginated (default 10KB) to prevent context overflow — use maxLength and offset to navigate.

Parameters:

Search calls with advanced filters. More flexible than list_calls for targeted queries.

Parameters:

List all keyword tracker definitions including tracked phrases, affiliation (whose speech is tracked), and filter queries. Explains tracker hits visible in get_call_summary output.

Parameters:

List all Gong workspaces with their IDs and names. Use these IDs as filters in list_calls, search_calls, get_trackers, and other tools. Most companies have 1–3 workspaces (e.g., by region or product line).

Parameters: None

Get a specific user's profile including name, email, title, phone, and settings. Useful for resolving user IDs returned from call data.

Parameters:

Search and filter users by IDs or creation date. More flexible than list_users for resolving specific user IDs from call data in bulk.

Parameters:

List all Gong users in your workspace. Returns name, email, and title for each user.

Parameters:

List all public Gong call library folders for a workspace. Returns folder IDs and names used with get_library_folder_calls. Private and archived folders are not returned.

Parameters:

Get all calls saved in a specific Gong library folder. Returns call IDs, titles, curator notes, and snippet timing for clips. Call IDs can be passed directly to get_call_summary or get_call_transcript.

Parameters:

Available Resources

Returns a markdown-formatted list of all users in your Gong workspace. Useful for resolving user IDs found in call data.

Parameters: None

Example Prompts

Once connected to Claude, you can ask:

• "List my Gong calls from last week"
• "Get the details for call 123456789"
• "Show me a summary of call 123456789"
• "Get the transcript for call 789012"
• "What workspaces do we have in Gong?"
• "What keywords is Gong tracking for competitors?"
• "What call library folders do we have in Gong?"
• "Show me the calls in the 'Best Discovery Calls' library folder"
• "Who are all the users in our Gong workspace?"
• "Search for calls hosted by Justin (user ID 232255198215877499) in July 2025"
• "Look up these user IDs: 111, 222, 333"

Contributing

Interested in contributing? Check out CONTRIBUTING.md for development setup, testing instructions, and guidelines.

The repository includes gong-openapi.json — a local copy of the Gong API OpenAPI spec. It's useful as a reference when adding new tools: use it to look up endpoint paths, parameter names, and response shapes without leaving your editor. The latest spec can be downloaded from the Gong API documentation.