Gong MCP Server
Servidor Gong MCP
Un servidor de Protocolo de Contexto de Modelo (MCP) que proporciona acceso a la API de Gong para recuperar grabaciones y transcripciones de llamadas. Este servidor permite a Claude interactuar con los datos de Gong a través de una interfaz estandarizada.
Características
Lista de llamadas de Gong con filtrado de rango de fechas opcional
Recupere transcripciones detalladas de llamadas específicas
Autenticación segura mediante las credenciales de API de Gong
Interfaz MCP estandarizada para una fácil integración con Claude
Related MCP server: GCP MCP
Prerrequisitos
Node.js 18 o superior
Docker (opcional, para implementación en contenedores)
Credenciales de la API de Gong (clave de acceso y secreto)
Instalación
Desarrollo local
Clonar el repositorio
Instalar dependencias:
npm installConstruir el proyecto:
npm run build
Estibador
Construir el contenedor:
docker build -t gong-mcp .Configurando Claude
Abrir la configuración de Claude Desktop
Vaya a la sección Servidores MCP
Agregue un nuevo servidor con la siguiente configuración:
{
"command": "docker",
"args": [
"run",
"-it",
"--rm",
"gong-mcp"
],
"env": {
"GONG_ACCESS_KEY": "your_access_key_here",
"GONG_ACCESS_SECRET": "your_access_secret_here"
}
}Reemplace las credenciales del marcador de posición con sus credenciales reales de la API de Gong de su archivo
.env
Herramientas disponibles
Lista de llamadas
Recupera una lista de llamadas de Gong con filtrado de rango de fechas opcional.
{
name: "list_calls",
description: "List Gong calls with optional date range filtering. Returns call details including ID, title, start/end times, participants, and duration.",
inputSchema: {
type: "object",
properties: {
fromDateTime: {
type: "string",
description: "Start date/time in ISO format (e.g. 2024-03-01T00:00:00Z)"
},
toDateTime: {
type: "string",
description: "End date/time in ISO format (e.g. 2024-03-31T23:59:59Z)"
}
}
}
}Recuperar transcripciones
Recupera transcripciones detalladas para identificaciones de llamadas específicas.
{
name: "retrieve_transcripts",
description: "Retrieve transcripts for specified call IDs. Returns detailed transcripts including speaker IDs, topics, and timestamped sentences.",
inputSchema: {
type: "object",
properties: {
callIds: {
type: "array",
items: { type: "string" },
description: "Array of Gong call IDs to retrieve transcripts for"
}
},
required: ["callIds"]
}
}Licencia
Licencia MIT: consulte el archivo de LICENCIA para obtener más detalles
Contribuyendo
Bifurcar el repositorio
Crea tu rama de funciones (
git checkout -b feature/amazing-feature)Confirme sus cambios (
git commit -m 'Add some amazing feature')Empujar a la rama (
git push origin feature/amazing-feature)Abrir una solicitud de extracción
Available Tools
2 toolslist_callsB
List Gong calls with optional date range filtering. Returns call details including ID, title, start/end times, participants, and duration.
Inputs: fromDateTime, toDateTime.
retrieve_transcriptsB
Retrieve transcripts for specified call IDs. Returns detailed transcripts including speaker IDs, topics, and timestamped sentences.
Inputs: callIds (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: list_calls retrieves metadata about calls, while retrieve_transcripts fetches detailed transcripts for specific calls. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool.
Both tools follow a consistent verb_noun pattern (list_calls and retrieve_transcripts), using snake_case and clear action verbs. The naming is predictable and readable across the set.
With only two tools, the server feels thin for a Gong MCP server, which typically handles call-related operations. This limited set may not cover essential workflows like creating, updating, or deleting calls, or accessing other call metadata beyond listing and transcripts.
Inferring the domain as call management, there are significant gaps: no tools for creating, updating, or deleting calls, and missing operations like searching calls, accessing call recordings, or managing participants. This incomplete surface will likely cause agent failures in broader workflows.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
Hosted CallRail MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server utilizing Claude AI for generating intelligent queries and offering documentation assistance based on API documentation analysis.3MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude to interact with Google Cloud Platform environments through natural language, allowing users to query and manage GCP resources during conversations.91,244 npm199MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude to initiate and manage real-time voice calls using Twilio and OpenAI's voice models.65MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that allows Claude AI to interact with custom tools, enabling extension of Claude's capabilities through the MCP framework.-