Simple Gong MCP server
Configuration
View docs{
"mcpServers": {
"kenazk-gong-mcp": {
"command": "docker",
"args": [
"run",
"-it",
"--rm",
"gong-mcp"
],
"env": {
"GONG_ACCESS_KEY": "your_access_key_here",
"GONG_ACCESS_SECRET": "your_access_secret_here"
}
}
}
}You can access Gong’s call recordings and transcripts through a standardized MCP interface. This server lets you list calls, filter by date, and retrieve detailed transcripts, enabling seamless integration with clients like Claude.
Connect your MCP client to the Gong MCP Server using the local stdio configuration. Once connected, you can list Gong calls with optional date range filters and fetch transcripts for specific call IDs. Use the available tools to perform these actions and handle the returned data within your client application.
Prerequisites you need before installing this MCP server are: Node.js 18 or higher and Docker for containerized deployment.
Local development steps you can follow to run the server locally:
npm install
npm run buildIf you prefer to run the server in a container, build the Docker image with the following command:
docker build -t gong-mcp .To run the MCP server from Claude, start the container with the required environment variables for Gong API access.
{
"command": "docker",
"args": [
"run",
"-it",
"--rm",
"gong-mcp"
],
"env": {
"GONG_ACCESS_KEY": "your_access_key_here",
"GONG_ACCESS_SECRET": "your_access_secret_here"
}
}Keep your Gong API credentials secure. Do not expose keys in client applications or logs. Use environment isolation and rotate credentials as needed.
List Gong calls and retrieve transcripts for specific calls using the MCP client’s tooling. These actions enable you to build workflows that review call data and extract insights.
List Gong calls with optional date range filtering. Returns call details including ID, title, start/end times, participants, and duration.
Retrieve transcripts for specified call IDs. Returns detailed transcripts including speaker IDs, topics, and timestamped sentences.