Gong MCP Server
Gong MCP Server
Ein Model Context Protocol (MCP)-Server, der Zugriff auf die Gong-API zum Abrufen von Anrufaufzeichnungen und Transkripten bietet. Dieser Server ermöglicht Claude die Interaktion mit Gong-Daten über eine standardisierte Schnittstelle.
Merkmale
Gong-Anrufe auflisten mit optionaler Datumsbereichsfilterung
Abrufen detaillierter Transkripte für bestimmte Anrufe
Sichere Authentifizierung mit den API-Anmeldeinformationen von Gong
Standardisierte MCP-Schnittstelle für die einfache Integration mit Claude
Related MCP server: GCP MCP
Voraussetzungen
Node.js 18 oder höher
Docker (optional, für containerisierte Bereitstellung)
Gong-API-Anmeldeinformationen (Zugriffsschlüssel und Geheimnis)
Installation
Lokale Entwicklung
Klonen Sie das Repository
Installieren Sie Abhängigkeiten:
npm installErstellen Sie das Projekt:
npm run build
Docker
Erstellen Sie den Container:
docker build -t gong-mcp .Claude konfigurieren
Öffnen Sie die Claude Desktop-Einstellungen
Navigieren Sie zum Abschnitt „MCP-Server“
Fügen Sie einen neuen Server mit der folgenden Konfiguration hinzu:
{
"command": "docker",
"args": [
"run",
"-it",
"--rm",
"gong-mcp"
],
"env": {
"GONG_ACCESS_KEY": "your_access_key_here",
"GONG_ACCESS_SECRET": "your_access_secret_here"
}
}Ersetzen Sie die Platzhalter-Anmeldeinformationen durch Ihre tatsächlichen Gong-API-Anmeldeinformationen aus Ihrer
.envDatei
Verfügbare Tools
Anrufe auflisten
Ruft eine Liste von Gong-Anrufen mit optionaler Datumsbereichsfilterung ab.
{
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)"
}
}
}
}Transkripte abrufen
Ruft detaillierte Transkripte für angegebene Anruf-IDs ab.
{
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"]
}
}Lizenz
MIT-Lizenz – Einzelheiten finden Sie in der Datei „LICENSE“
Beitragen
Forken Sie das Repository
Erstellen Sie Ihren Feature-Zweig (
git checkout -b feature/amazing-feature)Übernehmen Sie Ihre Änderungen (
git commit -m 'Add some amazing feature')Pushen zum Zweig (
git push origin feature/amazing-feature)Öffnen einer Pull-Anfrage
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.15 npm3MIT
- 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,773 npm200MIT
- 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.64MIT
- 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.-