gong-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@gong-mcp show me the transcript from yesterday's call with Acme Corp"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Gong MCP
MCP integration for Gong API, enabling AI assistants to interact with Gong call recordings, transcripts, and analytics.
Features
Authentication via secure Basic Auth
Access to calls, transcripts, users, and more
Compatible with Cursor AI assistant
Includes brief generation capability
Related MCP server: MCP-openproject
Prerequisites
Node.js >= 20.0.0
pnpm (recommended) or npm
Gong API credentials (Access Key and Secret)
Setup
Clone this repository
Install dependencies:
pnpm installBuild the TypeScript code:
pnpm buildConfigure your global Cursor MCP config at
~/.cursor/mcp.jsonwith your Gong credentials:{ "mcpServers": { "gong-mcp": { "type": "stdio", "command": "/opt/homebrew/bin/node", "args": ["/path/to/gong-mcp/build/index.js"], "cwd": "/path/to/gong-mcp", "environment": { "GONG_ACCESS_KEY": "your-access-key", "GONG_SECRET": "your-secret" } } } }
Environment Variables
The following environment variables are required:
GONG_ACCESS_KEY: Your Gong API access keyGONG_SECRET: Your Gong API secret
These can be set either in your environment or in the Cursor MCP config.
Documentation
Main Documentation - Detailed API and usage documentation
Sample Requests - Example API requests and responses
Development
Available npm scripts:
pnpm build # Build the TypeScript code
pnpm dev # Watch mode for development
pnpm test # Run all tests
pnpm test:smoke # Run smoke tests only
pnpm lint # Run ESLintTesting
Run the smoke tests to validate your setup:
pnpm test:smokeNote: Make sure to have GONG_ACCESS_KEY and GONG_SECRET environment variables set before running tests.
Usage with Cursor
Once configured in your global Cursor MCP settings, the AI assistant can:
Retrieve call recordings and transcripts
Search for calls by date range or participants
Access user information
Generate briefs for deals/accounts
Analyze call patterns and metrics
Available Tools
6 toolsgetv2askanythinggeneratebriefD
Generate account/deal brief
Inputs: workspace-id (required), brief-name (required), entity-type (required), crm-entity-id (required), +3 more.
getv2callsbyidC
Retrieve a single call
Inputs: id (required).
getv2dataprivacydataforemailaddressD
Activities for an email address (GDPR helper)
Inputs: emailAddress (required), cursor.
getv2usersB
List Gong users (100-row pages)
Inputs: cursor.
postv2callsextensiveC
Filtered call list with rich payload
Inputs: requestBody (required).
postv2callstranscriptC
Download transcripts
Inputs: requestBody (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
The tools have distinct purposes: generating briefs, retrieving calls, GDPR activities, listing users, filtering calls, and downloading transcripts. There is some potential overlap between getv2callsbyid and postv2callsextensive (both involve call data), but their descriptions clarify that one retrieves a single call while the other filters lists, reducing confusion.
The naming is inconsistent, mixing HTTP methods (get, post) with descriptive suffixes in a non-uniform pattern. For example, getv2askanythinggeneratebrief includes an action verb 'generate' in the name, while others like getv2users do not. This lack of a clear, predictable naming convention makes the set harder to navigate.
With 6 tools, the count is reasonable for a Gong CRM integration server. It covers key areas like calls, users, and data privacy without being overwhelming. However, it feels slightly thin for comprehensive CRM operations, such as missing update or delete functionalities.
The toolset covers core read operations for calls, users, and GDPR activities, but lacks obvious CRUD completeness. There are no tools for creating, updating, or deleting resources, which are essential for full CRM workflows. This creates gaps that agents might struggle with for comprehensive task handling.
Maintenance
Related MCP Connectors
Related MCP Servers
- -
- ISC
- MIT
- -