Skip to main content
Glama
Gong MCP Server

Gong MCP Server

by kenazk

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

  1. Clonar el repositorio

  2. Instalar dependencias:

    npm install
  3. Construir el proyecto:

    npm run build

Estibador

Construir el contenedor:

docker build -t gong-mcp .

Configurando Claude

  1. Abrir la configuración de Claude Desktop

  2. Vaya a la sección Servidores MCP

  3. 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"
  }
}
  1. 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

  1. Bifurcar el repositorio

  2. Crea tu rama de funciones ( git checkout -b feature/amazing-feature )

  3. Confirme sus cambios ( git commit -m 'Add some amazing feature' )

  4. Empujar a la rama ( git push origin feature/amazing-feature )

  5. Abrir una solicitud de extracción

Available Tools

2 tools
list_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

    B3.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness2/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      A 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.
      9
      1,244 npm
      199
      MIT