Un servidor Model Context Protocol de solo lectura que le da a Claude acceso delimitado a tu cuenta de Gong: descubrimiento de llamadas, definiciones de trackers, señales analizadas por llamada, estadísticas de interacción por rep y una herramienta derivada que reporta qué trackers de riesgo se activaron en qué llamadas — separando si lo dijo el cliente o tu propio rep. El scaffold está en el bundle de artefactos en apps/web/public/artifacts/mcp-server-gong-revops/, que incluye README.md, pyproject.toml y src/gong_revops_mcp/server.py, instalable con pip install -e ..
Empieza por lo que la API no tiene, porque determina la forma de todo lo demás. La API pública de Gong no expone ningún endpoint de lectura para los datos del deal board. Los endpoints de CRM (GET /v2/crm/entities) devuelven solo objetos que subiste antes mediante una integración CRM genérica registrada, y la documentación de Gong marca ese endpoint como verificación en fase de desarrollo. Así que un servidor que promete «pregúntale a Claude sobre tus deals de Gong» está haciendo una de tres cosas: envolver la UI, leer tu CRM en su lugar, o adivinar. Este deriva el riesgo del deal desde las conversaciones y lo dice: deal_risk_digest devuelve los hits de trackers con una nota que te indica unir call_id a tu CRM para stage, monto y fecha de cierre.
Cuándo usarlo
Recurre a él cuando una pregunta recurrente de RevOps le cuesta a una persona diez minutos de clics: qué cuentas objetaron el precio la semana pasada, en qué llamadas se nombró a un competidor, si los reps de un segmento con problemas están monologando. Esos son joins entre los propios datos de Gong que la UI te obliga a hacer a ojo. Dos roles sacan el mayor provecho. El líder de RevOps que corre un pipeline review semanal pregunta en lenguaje natural y pega una respuesta estructurada en el deck. El GTM engineer que escribe un script desechable contra /v2/calls/extensive cada vez que alguien plantea una pregunta nueva ya tiene el contentSelector, la paginación por cursor, el rate limiter y la atribución de hablante conectados.
También es el patrón correcto si ya corres el servidor MCP de Salesforce para RevOps o el de Clari y quieres la capa de conversación en la misma superficie de chat, para que una pregunta pueda cruzar de «qué dijo el cliente» a «en qué stage está» sin cambiar de pestaña. Ese cruce es el verdadero beneficio: ninguno de los dos sistemas lo responde solo.
Cuándo NO usarlo
Gong ya publica un servidor MCP oficial. Gong anunció soporte para MCP en 2026 y documenta un servidor MCP alojado por Gong, disponible en cualquier plan de Gong, configurado por un administrador técnico y con acceso gobernado por el nivel de asiento. Permite que Claude, ChatGPT y Microsoft Copilot pregunten sobre cuentas y deals y extraigan los insights generados por la IA de Gong. Pruébalo primero. Es de primera parte, no requiere hospedar ningún proceso y respeta los permisos por nivel de asiento de Gong, algo que este scaffold no hace. Construye la versión autohospedada cuando necesites una superficie de herramientas fija y auditable — un contentSelector que controlas, un kill-switch de transcripciones, un límite de páginas, salida de trackers con atribución de hablante — o cuando tu administrador no habilite el servidor alojado.
No consigues que un administrador genere una API key. Las credenciales salen de Company Settings → Ecosystem → API y solo un administrador técnico puede crearlas. No existe una key por usuario.
La visibilidad de llamadas por usuario es determinante para ti. Una sola key a nivel de cuenta ve todas las llamadas de los workspaces que cubre, sin importar qué persona esté conversando. Si tu instancia de Gong restringe quién puede escuchar las llamadas de quién, este servidor lo evade. Córrelo por analista con keys de alcance estrecho, o no lo corras.
Quieres transcripciones textuales en el modelo por defecto. Aquí están apagadas, y el diseño asume que eso es lo correcto. Si tu workflow es transcripción-primero, vas a pelear contra el scaffold.
Una o dos preguntas al mes. Los filtros propios de la UI de Gong son más rápidos que un setup que tienes que mantener.
Qué expone
Seis herramientas de lectura, ninguna de escritura. La superficie de escritura de la API pública es la subida de llamadas y la subida de objetos de CRM genérico; ninguna de las dos pertenece detrás de un prompt de chat, y solo-lectura elimina toda la clase de fallo de «el modelo me malinterpretó y cambió el sistema de registro».
find_calls — GET /v2/calls. Solo metadata: id, título, inicio, duración, dirección, URL de Gong. Delimita la pregunta aquí primero.
list_trackers — GET /v2/settings/trackers. Solo definiciones de trackers. Gong no devuelve conteos de coincidencias desde este endpoint, lo que sorprende a la gente; los conteos de ocurrencias vienen del endpoint extensive de llamadas.
call_signals — POST /v2/calls/extensive. El caballo de batalla: participantes, coincidencias de trackers, ocurrencias de trackers, brief de Spotlight, key points, resultado automático de la llamada, temas, tiempo de habla, estadísticas de interacción por persona, comentarios públicos.
call_transcript — POST /v2/calls/transcript. Apagado a menos que GONG_ALLOW_TRANSCRIPTS=true, limitado a 3 llamadas, exige una justificación.
rep_interaction_stats — POST /v2/stats/interaction. Monólogo más largo, historia de cliente más larga, interactividad, paciencia, tasa de preguntas.
deal_risk_digest — derivada. Une definiciones de trackers con ocurrencias en un rango de fechas y clasifica cada hit como customer, internal o unattributed.
Postura de ingeniería
La atribución de hablante es el sentido completo del digest. «Pricing Pushback» dicho por tu propio rep es una señal de comportamiento del rep. Dicho por el cliente, es una señal del deal. Un conteo de trackers que los suma se mueve por las razones equivocadas y produce un número de riesgo sobre el que nadie puede actuar. deal_risk_digest lee content.trackerOccurrences, busca cada speakerId en el array parties de la llamada y separa por afiliación de la parte. Por eso el servidor pide ocurrencias y no solo conteos, y es lo único que un wrapper genérico de Gong no va a hacer por ti.
Nunca se piden medios. El contentSelector en server.py es fijo, no controlado por quien llama, y omite media. La key no tiene api:calls:read:media-url. Así el servidor nunca genera los enlaces firmados de audio/video de 8 horas de Gong — un enlace que sobrevive a la conversación en la que apareció es una fuga esperando una captura de pantalla.
Las transcripciones son un kill-switch, no un prompt.call_transcript verifica una variable de entorno antes de correr y limita a tres llamadas. Confiar solo en un string de justificación deja el habla textual del cliente a una malinterpretación confiada de distancia de la ventana de contexto. La bandera convierte «¿permitimos esto en absoluto?» en una decisión de despliegue en lugar de una por pregunta.
La paginación está limitada y el límite se reporta.GONG_MAX_PAGES está en 5 por defecto, así que una llamada a herramienta lee como máximo 500 registros y devuelve truncated: true cuando se detuvo antes. Un modelo que ve la mitad de los datos en silencio responde con confianza la pregunta equivocada.
Las peticiones se serializan, no se reintentan. Gong limita a 3 peticiones por segundo y 10.000 peticiones por día por defecto, devolviendo 429 con un header Retry-After. El scaffold espera 0,34s entre peticiones en lugar de disparar en paralelo y reaccionar a los 429, porque una tormenta de reintentos reactivos igual gasta cuota diaria en peticiones que iban a fallar de todos modos.
Realidad de costos
Tres líneas, más una que no es línea.
Suscripción a Claude. Lo que ya pagas — Pro a $20/usuario/mes, Max a $100–200/usuario/mes, o consumo de API. El servidor no cambia nada aquí.
Autohospedaje. Un proceso Python local por usuario de Claude Desktop: costo cero de infraestructura. Como servicio compartido, una VM pequeña a unos $20–50/mes en cualquier cloud.
Cuota de la API de Gong. Gratis con tu contrato de Gong, no medida en dólares, pero finita: 3 peticiones por segundo y 10.000 peticiones por día por empresa por defecto, ampliables contactando al soporte de Gong. Presupuéstala. Un deal_risk_digest sobre 90 días en un workspace con 4.000 llamadas son 40 páginas de 100 = 40 peticiones. Diez preguntas así al día son 400 peticiones, cómodamente dentro del techo. Lo que rompe el presupuesto es un loop de cursor sin límite, que es exactamente lo que GONG_MAX_PAGES existe para evitar.
Asientos de Gong. Gong no publica precios de lista; se cotiza por asiento con una tarifa de plataforma. Lo que pagues no cambia con este servidor — no agrega asientos.
El costo en tokens lo domina el payload de las respuestas, por eso server.py adelgaza cada respuesta antes de devolverla. call_signals sobre 20 llamadas devuelve briefs y key points en lugar de contenido completo y cae en las decenas bajas de miles de tokens. Un call_transcript sobre una llamada de 45 minutos es comparable por sí solo, y ese es el argumento real para dejar las transcripciones apagadas.
Frente a las alternativas
El servidor MCP oficial de Gong. Cubierto arriba: pruébalo primero. De primera parte, cualquier plan, permisos por nivel de asiento, nada que hospedar. Elige el scaffold autohospedado cuando necesites una superficie de herramientas que puedas leer en un archivo y fijar, o cuando el servidor alojado no esté habilitado para ti.
Un servidor MCP de Gong de la comunidad. Existen varios en GitHub y en directorios de MCP, la mayoría envolviendo llamadas y transcripciones. Más rápido de instalar que leer este scaffold. La contrapartida es que «envuelve llamadas y transcripciones» suele significar transcripciones activadas por defecto, sin límite de páginas y conteos de trackers sin atribución de hablante — las tres decisiones que este scaffold toma distinto a propósito.
Un script desechable contra /v2/calls/extensive. Control máximo, y cada equipo reconstruye a mano la autenticación Basic, la base URL específica de la cuenta, la paginación por cursor, el rate limiter y el join con parties. Este scaffold son unas 450 líneas con todo eso ya conectado.
La propia UI de Gong y Spotlight. Más rápido para una sola llamada y los datos ya están ahí. No puede unir datos de Gong con el resto de tu contexto de Claude, que es la única razón para correr cualquiera de estas cosas. Si no tienes claro si un servidor MCP o un Skill es la forma correcta para tu problema, lee Claude Skill frente a servidor MCP.
Puntos de cuidado
El README documenta los siete; los cinco determinantes:
Una base URL equivocada devuelve 401, no 404. La base URL de la API de Gong es específica de la cuenta y https://api.gong.io es un default común, no universal. Los equipos pierden una tarde depurando credenciales que estaban bien. Guarda: _raise_for_gong intercepta el 401 y nombra la base URL que realmente usó, listando el desajuste de base URL como primera causa antes que las credenciales.
Un tracker renombrado se lee como buena noticia.deal_risk_digest compara nombres de trackers exactamente, así que un tracker renombrado en Gong deja de coincidir y el digest reporta cero riesgo. Guarda: parcial — corre list_trackers primero y pega los nombres reales en GONG_RISK_TRACKERS; los defaults que vienen son placeholders que no coinciden con nada en la mayoría de workspaces. Emitir una advertencia cuando un nombre configurado no coincide con ningún tracker vivo es el TODO #3 del README.
Las estadísticas de interacción castigan el bajo volumen de llamadas. Las estadísticas de Gong derivan solo de llamadas con Whisper habilitado, así que un rep con tres llamadas grabadas es estadísticamente indistinguible de un rep con un problema real. Guarda: rep_interaction_stats devuelve esa advertencia en línea en cada respuesta, para que el modelo la repita en lugar de dar coaching sobre ruido; une los conteos de find_calls antes de mostrar los números a un manager.
Truncamiento silencioso. Un loop de cursor detenido en el límite de páginas se ve idéntico a una respuesta completa. Guarda: toda herramienta paginada devuelve truncated: true cuando se detuvo antes, y find_calls es la forma económica de revisar volumen antes de hacer una pregunta costosa.
Deriva del consentimiento. Un cliente que consintió ser grabado no consintió por ello ser resumido por un modelo de terceros. Guarda: las transcripciones están apagadas por defecto y nunca se generan URLs de medios; revisa tu DPA antes de activar GONG_ALLOW_TRANSCRIPTS.
Stack
Gong — conversation intelligence, trackers, briefs de Spotlight, estadísticas de interacción
MCP Python SDK — mcp>=1.2.0; provee Server, stdio_server y los decoradores del registro de herramientas
httpx — cliente REST async contra el host de la API de Gong de tu cuenta, autenticación Basic con base64("key:secret")
Claude Desktop o Claude Code — interfaz de lenguaje natural y llamador de herramientas
GONG_ALLOW_TRANSCRIPTS — el candado a nivel de entorno que decide si el habla textual del cliente llega al modelo en absoluto
GONG_MAX_PAGES — la guarda de cuota que además hace visible al modelo que la respuesta está incompleta
# mcp-server-gong-revops
A read-only MCP server over the Gong public API v2, tuned for RevOps questions that currently require a human to open Gong, filter a call list, read four calls, and write down what they saw. Exposes call discovery, tracker definitions, per-call analyzed signals (tracker matches with speaker attribution, Spotlight brief, key points, call outcome, talk-ratio stats), per-rep interaction stats, and one derived tool — `deal_risk_digest` — that joins tracker definitions to tracker occurrences and splits them by who actually said the thing.
> **STATUS: scaffold — not runtime-tested.** The code follows the official `mcp` Python SDK conventions and the endpoint paths, scopes, and field names track the public Gong API docs (help.gong.io/apidocs) as of 2026-07. It has not been executed against a live Gong account. Response field names in particular vary by account configuration — verify before you rely on it.
## Two things this server refuses to do
**No `get_deals` tool.** Gong's public API has no native read endpoint for deal-board data. The CRM endpoints (`GET /v2/crm/entities`) only read back objects you previously *uploaded* through a registered generic CRM integration, and Gong's own documentation marks that endpoint as development-phase verification only. Any MCP server advertising "ask Claude about your Gong deals" is either wrapping the UI, reading your CRM, or inventing the answer. `deal_risk_digest` is the honest substitute: it derives risk signals from conversations and tells you to join to the CRM for stage and amount.
**No writes.** The public API's write surface is call upload and generic-CRM object upload. Neither belongs behind a chat prompt, and read-only removes the entire class of "the model misread me and mutated the system of record" failure. If you need writes later, add them as separately-named tools with mandatory justification strings — never as a free-text command.
## What it exposes
- `find_calls(fromDateTime, toDateTime?, workspace_id?)` — `GET /v2/calls`. Cheap metadata: id, title, start, duration, direction, Gong URL. Scope a question here first, then pass ids to `call_signals`. Follows at most `GONG_MAX_PAGES` cursor pages of 100.
- `list_trackers(workspace_id?)` — `GET /v2/settings/trackers`. Tracker **definitions only** — ids, names, keywords, affiliation. No match counts; Gong does not return occurrence statistics from this endpoint. Call it to learn what your workspace actually tracks before guessing a tracker name in a question.
- `call_signals(call_ids? | fromDateTime, toDateTime?, workspace_id?)` — `POST /v2/calls/extensive` with a fixed `contentSelector`: parties, tracker matches, tracker occurrences, Spotlight brief, key points, auto call outcome, topics, speaker talk time, per-person interaction stats, public comments. The workhorse tool.
- `call_transcript(call_ids, justification)` — `POST /v2/calls/transcript`. Verbatim monologues with speaker id and millisecond offsets. Disabled unless `GONG_ALLOW_TRANSCRIPTS=true`, capped at `GONG_MAX_TRANSCRIPT_CALLS` (default 3), and requires a justification of at least 10 characters.
- `rep_interaction_stats(fromDate, toDate, user_ids?)` — `POST /v2/stats/interaction`. Longest monologue, longest customer story, interactivity, patience, question rate, per rep.
- `deal_risk_digest(fromDateTime, toDateTime?, tracker_names?, workspace_id?)` — derived. Scans calls in the range, keeps only occurrences of the trackers named in `GONG_RISK_TRACKERS`, and reports each hit split into `customer` / `internal` / `unattributed` by the speaker's party affiliation.
## Setup
### 1. Install
```bash
git clone <wherever you put this>
cd mcp-server-gong-revops
python -m venv .venv
source .venv/bin/activate # or .venv\Scripts\activate on Windows
pip install -e .
```
### 2. Generate Gong API credentials
A **technical administrator** creates these — a standard user seat cannot. In Gong: **Company Settings → Ecosystem → API**, then generate an Access Key and Access Key Secret. Copy the secret immediately; Gong shows it once.
The same page displays **your account's base URL**. Copy it. `https://api.gong.io` is the common value but not a universal one — accounts on regional or dedicated hosts get a different origin, and a wrong base URL returns **401, not 404**, which sends people debugging a credential problem they do not have.
### 3. Grant scopes
Scopes are attached to the key by the administrator who creates it. This server needs five:
| Scope | Used by |
|---|---|
| `api:calls:read:basic` | `find_calls` |
| `api:calls:read:extensive` | `call_signals`, `deal_risk_digest` |
| `api:calls:read:transcript` | `call_transcript` |
| `api:settings:trackers:read` | `list_trackers` |
| `api:stats:interaction` | `rep_interaction_stats` |
Grant only what you intend to use. Omitting `api:calls:read:transcript` is a second, key-level lock on transcripts on top of `GONG_ALLOW_TRANSCRIPTS`. Note what is deliberately **absent**: `api:calls:read:media-url`. The server never requests media URLs, so it never mints the 8-hour signed audio/video links that would otherwise outlive the conversation they appeared in.
### 4. Configure environment
```bash
export GONG_ACCESS_KEY="your-access-key"
export GONG_ACCESS_KEY_SECRET="your-access-key-secret"
export GONG_BASE_URL="https://api.gong.io" # COPY YOURS from Company Settings -> API
export GONG_ALLOW_TRANSCRIPTS="false" # true enables call_transcript
export GONG_MAX_TRANSCRIPT_CALLS="3" # cap per transcript call
export GONG_MAX_PAGES="5" # cursor pages followed per tool call
export GONG_WORKSPACE_ID="" # optional default workspace
export GONG_MIN_REQUEST_INTERVAL="0.34" # seconds between requests (3/s limit)
export GONG_RISK_TRACKERS="Pricing Pushback,Competitor Mention,Budget Freeze,Legal Review,Champion Left"
```
Env var notes:
- **`GONG_ACCESS_KEY` / `GONG_ACCESS_KEY_SECRET`** — from Company Settings → Ecosystem → API. Combined as `base64("key:secret")` and sent as `Authorization: Basic <token>`. If you register this as a Gong OAuth app instead, replace `auth_headers()` with a `Bearer` token.
- **`GONG_BASE_URL`** — account-specific. Copy it rather than trusting the default. This is the single most common setup failure.
- **`GONG_ALLOW_TRANSCRIPTS`** — the PII kill-switch. Transcripts put full verbatim customer speech into model context. Off by default; flip it only after someone has decided that is allowed for this data.
- **`GONG_MAX_TRANSCRIPT_CALLS`** — blast-radius cap. Three transcripts is already a large prompt. Raise it deliberately, never to "just get the analysis done."
- **`GONG_MAX_PAGES`** — the quota guard. Gong pages at 100 records and allows 10,000 requests/day by default; an unbounded cursor loop over a busy workspace can spend a real share of that answering one question. 5 pages = up to 500 records per tool call, and the response reports `truncated: true` so the model knows it did not see everything.
- **`GONG_RISK_TRACKERS`** — which tracker names count as risk. Gong ships no "this tracker means risk" flag, so this is a judgment your team makes. Replace the defaults with your actual tracker names from `list_trackers` — the defaults are placeholders and will match nothing in most workspaces.
- **`GONG_MIN_REQUEST_INTERVAL`** — requests are serialized behind this interval to stay under 3/second. Reactive 429 retries still burn daily quota on requests that were always going to fail.
### 5. Register with Claude
`claude_desktop_config.json` (macOS: `~/Library/Application Support/Claude/`, Windows: `%APPDATA%\Claude\`):
```json
{
"mcpServers": {
"gong-revops": {
"command": "/absolute/path/to/mcp-server-gong-revops/.venv/bin/python",
"args": ["-m", "gong_revops_mcp.server"],
"env": {
"GONG_ACCESS_KEY": "your-access-key",
"GONG_ACCESS_KEY_SECRET": "your-access-key-secret",
"GONG_BASE_URL": "https://api.gong.io",
"GONG_ALLOW_TRANSCRIPTS": "false",
"GONG_MAX_PAGES": "5",
"GONG_RISK_TRACKERS": "Pricing Pushback,Competitor Mention,Legal Review"
}
}
}
}
```
For Claude Code, the same block goes in `.mcp.json` at the project root. Restart the client after editing.
### 6. Sanity check
Run these three in order. Each one isolates a different failure.
1. **"List the Gong trackers in my workspace."** → exercises auth, base URL, and `api:settings:trackers:read` on the cheapest possible request. A 401 here means base URL or credentials; a 403 means scopes. Copy the real tracker names out of the response into `GONG_RISK_TRACKERS`.
2. **"Find Gong calls from the last 7 days."** → exercises `GET /v2/calls` and cursor pagination. If `truncated` comes back `true`, your workspace has more than `GONG_MAX_PAGES × 100` calls in a week; narrow the range in real questions.
3. **"Pull the signals for the three most recent of those calls and tell me which trackers the customer raised."** → exercises `/v2/calls/extensive`, the fixed `contentSelector`, and speaker attribution. If tracker occurrences come back empty while counts are non-zero, your account does not expose `content.trackerOccurrences` and `deal_risk_digest` will report everything as `unattributed`.
## Security model
- **Token scope.** One account-level API key with five read scopes. It is not per-user: the key sees every call in the workspaces it covers, regardless of which human is chatting. Anyone who can talk to this MCP server can read any recorded call. If your Gong instance relies on per-user visibility rules, this server bypasses them — run it per-analyst with narrowly-scoped keys, or do not run it.
- **What leaves Gong.** Call metadata, party names/emails/titles, tracker matches, Spotlight briefs, key points, topics, and interaction stats go into the model context on every `call_signals` call. Verbatim customer speech goes only through `call_transcript`, which is off by default.
- **What never leaves.** Audio and video. The server does not request the `media` field and does not hold `api:calls:read:media-url`, so no signed recording links are minted.
- **Recording consent is upstream.** This server inherits whatever consent posture your Gong instance already has. It does not create a new consent question, but it does widen who can read the result — a recording a customer consented to being *recorded* is not automatically one they consented to being *summarized by a third-party model*. Check your DPA before enabling transcripts.
## Known limits — numbered TODO list before production use
1. **Not runtime-tested.** Every response-slimming function assumes field names from the docs (`metaData.id`, `content.trackers[].occurrences[].speakerId`, `usersAggregateActivity`). Run each tool once against a real account and fix the shapes before trusting output.
2. **No retry with backoff.** A 429 raises with the `Retry-After` value in the message instead of sleeping and retrying. Fine for interactive chat, wrong for unattended use.
3. **`deal_risk_digest` matches tracker names case-insensitively and exactly.** A renamed tracker silently stops matching and the digest reports zero risk — which reads as good news. Add a warning when a configured name matches no tracker returned by `list_trackers`.
4. **No caching.** Asking the same question twice spends the quota twice. A short-lived cache keyed on the filter would cut the common repeat-question cost.
5. **`rep_interaction_stats` has no call-count denominator.** Gong's stats derive only from calls with Whisper enabled, so a rep with three recorded calls looks statistically identical to a rep with a real problem. Join `find_calls` counts before showing these numbers to a manager.
6. **Single workspace assumption in the digest.** `deal_risk_digest` accepts one `workspace_id`; multi-workspace accounts need one call per workspace and a merge step.
7. **Account name comes from party emails, not the CRM.** `external_parties` is a list of names/emails, not a resolved account. Joining on email domain is the usual fix and it is not implemented here.
"""
gong-revops-mcp — read-only MCP server over the Gong public API v2.
Exposes call discovery, tracker definitions, extensive per-call signals (trackers,
tracker occurrences, Spotlight brief, key points, call outcome, per-person interaction
stats), rep interaction stats, and a derived deal-risk digest that joins tracker
definitions to tracker occurrences across a date range.
Two things this server deliberately does NOT do:
1. There is no `get_deals` tool. Gong's public API has no native read endpoint for
deal-board data. `GET /v2/crm/entities` only reads back objects you previously
uploaded through a registered generic CRM integration, and Gong's own docs mark it
as development-phase verification only. Deal risk here is DERIVED from calls plus
trackers (see `deal_risk_digest`); for authoritative deal fields, query the CRM's
own API instead.
2. There are no writes. The public API's write surface is call upload and generic-CRM
object upload, neither of which belongs behind a chat prompt. Read-only removes the
whole class of "the model misread me and changed the system of record" failure.
STATUS: scaffold — not runtime-tested. Endpoint paths, scopes, and field names track
the public Gong API docs (help.gong.io/apidocs) as of 2026-07; verify against your
account before relying on it. Your base URL is account-specific — see README.
Run as: python -m gong_revops_mcp.server
"""
from __future__ import annotations
import asyncio
import base64
import os
import time
from typing import Any
import httpx
from mcp.server import Server
from mcp.server.stdio import stdio_server
from mcp.types import TextContent, Tool
# ----- Configuration (read from env at startup) -----
GONG_ACCESS_KEY = os.environ.get("GONG_ACCESS_KEY")
GONG_ACCESS_KEY_SECRET = os.environ.get("GONG_ACCESS_KEY_SECRET")
# The Gong API base URL is ACCOUNT-SPECIFIC. api.gong.io is the common default, but
# accounts on regional or dedicated hosts get a different origin. Find yours at
# Company Settings -> API (see README) — a wrong base URL presents as 401, not 404,
# which sends people hunting for a credential problem they do not have.
GONG_BASE_URL = os.environ.get("GONG_BASE_URL", "https://api.gong.io").rstrip("/")
# Transcripts are the highest-PII and highest-token surface in the API: full verbatim
# customer speech, thousands of tokens per call. Off unless explicitly opted in.
GONG_ALLOW_TRANSCRIPTS = os.environ.get("GONG_ALLOW_TRANSCRIPTS", "false").lower() == "true"
# Blast-radius cap on transcript pulls. Three calls of transcript is already a large
# prompt; a date-range transcript pull across a team is how you blow a context window
# and a day's API quota in one question.
GONG_MAX_TRANSCRIPT_CALLS = int(os.environ.get("GONG_MAX_TRANSCRIPT_CALLS", "3"))
# Cursor-following guard. Gong pages at 100 records and allows 10,000 calls/day; an
# unbounded cursor loop over a busy workspace can consume a meaningful share of that
# quota answering one question. Five pages = up to 500 records per tool call.
GONG_MAX_PAGES = int(os.environ.get("GONG_MAX_PAGES", "5"))
# Optional default workspace, so callers do not pass workspaceId on every query.
GONG_WORKSPACE_ID = os.environ.get("GONG_WORKSPACE_ID")
# Tracker names that count as risk signals for deal_risk_digest. Gong ships no
# "this tracker means risk" flag — which trackers are risk is a judgment call your
# team makes, so it is configuration, not a hardcoded list.
GONG_RISK_TRACKERS = [
t.strip()
for t in os.environ.get(
"GONG_RISK_TRACKERS",
"Pricing Pushback,Competitor Mention,Budget Freeze,Legal Review,Champion Left",
).split(",")
if t.strip()
]
# Gong throttles at 3 requests/second. We serialize requests behind a minimum
# interval rather than firing concurrently and handling 429s reactively — a reactive
# retry storm still burns daily quota on requests that were always going to fail.
MIN_REQUEST_INTERVAL = float(os.environ.get("GONG_MIN_REQUEST_INTERVAL", "0.34"))
PAGE_SIZE = 100
_rate_lock = asyncio.Lock()
_last_request_at = 0.0
def require_config() -> None:
missing = [
name
for name, value in (
("GONG_ACCESS_KEY", GONG_ACCESS_KEY),
("GONG_ACCESS_KEY_SECRET", GONG_ACCESS_KEY_SECRET),
)
if not value
]
if missing:
raise RuntimeError(f"Required env vars are unset: {', '.join(missing)}")
def auth_headers() -> dict[str, str]:
# Gong's API-key method is HTTP Basic with base64("<access key>:<secret>").
# OAuth apps use "Authorization: Bearer <token>" instead; swap this function if
# you register the server as a Gong app rather than using an account API key.
token = base64.b64encode(
f"{GONG_ACCESS_KEY}:{GONG_ACCESS_KEY_SECRET}".encode()
).decode()
return {
"Authorization": f"Basic {token}",
"Content-Type": "application/json",
}
# ----- Gong REST helpers -----
async def _throttle() -> None:
global _last_request_at
async with _rate_lock:
wait = MIN_REQUEST_INTERVAL - (time.monotonic() - _last_request_at)
if wait > 0:
await asyncio.sleep(wait)
_last_request_at = time.monotonic()
async def gong_request(
method: str, path: str, *, params: dict[str, Any] | None = None, json: dict[str, Any] | None = None
) -> dict[str, Any]:
await _throttle()
async with httpx.AsyncClient(timeout=60.0) as client:
r = await client.request(
method, f"{GONG_BASE_URL}{path}", headers=auth_headers(), params=params, json=json
)
_raise_for_gong(r, path)
return r.json() if r.content else {}
def _raise_for_gong(r: httpx.Response, path: str) -> None:
if r.status_code == 401:
raise PermissionError(
"Gong returned 401. Two causes, in order of likelihood: (1) GONG_BASE_URL "
f"is wrong for this account — {GONG_BASE_URL} is a guess unless you copied it "
"from Company Settings -> API; (2) the access key/secret pair is wrong or "
"revoked. A wrong base URL does NOT return 404."
)
if r.status_code == 403:
raise PermissionError(
f"Gong returned 403 on {path}. The API key is missing a scope. This server "
"needs api:calls:read:basic, api:calls:read:extensive, "
"api:calls:read:transcript, api:settings:trackers:read, and "
"api:stats:interaction. Scopes are set per key by a technical administrator."
)
if r.status_code == 429:
retry_after = r.headers.get("Retry-After", "unknown")
raise RuntimeError(
f"Gong returned 429 (rate limit; Retry-After={retry_after}s). Default limits "
"are 3 requests/second and 10,000 requests/day. Lower GONG_MAX_PAGES, raise "
"GONG_MIN_REQUEST_INTERVAL, or ask Gong support to raise the account limit."
)
r.raise_for_status()
async def paged_post(path: str, body: dict[str, Any], record_key: str) -> tuple[list[Any], bool]:
"""POST through cursor pagination up to GONG_MAX_PAGES. Returns (records, truncated)."""
records: list[Any] = []
cursor: str | None = None
for _ in range(max(1, GONG_MAX_PAGES)):
payload = dict(body)
if cursor:
payload["cursor"] = cursor
data = await gong_request("POST", path, json=payload)
records.extend(data.get(record_key, []) or [])
cursor = (data.get("records") or {}).get("cursor")
if not cursor:
return records, False
return records, True
def _date_filter(arguments: dict[str, Any], *, keys: tuple[str, str]) -> dict[str, Any]:
out: dict[str, Any] = {}
for key in keys:
if v := arguments.get(key):
out[key] = v
workspace = arguments.get("workspace_id") or GONG_WORKSPACE_ID
if workspace:
out["workspaceId"] = workspace
return out
# ----- Server + tool registry -----
server = Server("gong-revops")
# The contentSelector this server sends to /v2/calls/extensive. Fixed, not
# caller-controlled: `media` is deliberately absent so the server never requests
# 8-hour signed audio/video URLs (a separate scope, and a link that outlives the
# conversation it appeared in). `content.trackerOccurrences` is included because
# tracker *counts* without speaker and timestamp cannot tell you whether the customer
# raised pricing or your rep did — which inverts the meaning of the signal.
SIGNALS_CONTENT_SELECTOR: dict[str, Any] = {
"context": "Extended",
"contextTiming": ["Now"],
"exposedFields": {
"parties": True,
"content": {
"trackers": True,
"trackerOccurrences": True,
"brief": True,
"keyPoints": True,
"callOutcome": True,
"topics": True,
},
"interaction": {
"speakers": True,
"personInteractionStats": True,
"questions": True,
},
"collaboration": {"publicComments": True},
},
}
@server.list_tools()
async def list_tools() -> list[Tool]:
return [
Tool(
name="find_calls",
description=(
"List calls in a date range (GET /v2/calls). Cheap metadata only — id, "
"title, start time, duration, participant count. Use this first to scope "
"a question, then pass the ids you care about to call_signals. Pages at "
"100 records; follows at most GONG_MAX_PAGES pages."
),
inputSchema={
"type": "object",
"properties": {
"fromDateTime": {
"type": "string",
"description": "ISO-8601, e.g. 2026-07-01T00:00:00Z. Calls starting at or after.",
},
"toDateTime": {
"type": "string",
"description": "ISO-8601. Calls starting before.",
},
"workspace_id": {"type": "string"},
},
"required": ["fromDateTime"],
},
),
Tool(
name="list_trackers",
description=(
"List keyword/smart tracker DEFINITIONS (GET /v2/settings/trackers). "
"Returns configuration only — names, ids, keywords, affiliation — and no "
"match counts. Occurrence counts come from call_signals. Call this to "
"learn what your workspace actually tracks before assuming a tracker name."
),
inputSchema={
"type": "object",
"properties": {"workspace_id": {"type": "string"}},
},
),
Tool(
name="call_signals",
description=(
"Retrieve analyzed signals for specific calls (POST /v2/calls/extensive): "
"parties, tracker matches with speaker and timestamp, Spotlight brief, key "
"points, auto call outcome, topics, talk ratio and interactivity stats, and "
"public comments. No transcript, no media URLs. This is the workhorse tool."
),
inputSchema={
"type": "object",
"properties": {
"call_ids": {
"type": "array",
"items": {"type": "string"},
"description": "Specific Gong call ids. Preferred over a date range.",
},
"fromDateTime": {"type": "string", "description": "ISO-8601, used when call_ids is omitted."},
"toDateTime": {"type": "string", "description": "ISO-8601."},
"workspace_id": {"type": "string"},
},
},
),
Tool(
name="call_transcript",
description=(
"Retrieve verbatim transcripts for up to GONG_MAX_TRANSCRIPT_CALLS calls "
"(POST /v2/calls/transcript). Disabled unless GONG_ALLOW_TRANSCRIPTS=true. "
"Requires a justification. Prefer call_signals — the brief and key points "
"answer most questions at a fraction of the tokens and the PII exposure."
),
inputSchema={
"type": "object",
"properties": {
"call_ids": {"type": "array", "items": {"type": "string"}},
"justification": {
"type": "string",
"description": "Why the verbatim transcript is needed instead of the brief. Min 10 chars.",
},
},
"required": ["call_ids", "justification"],
},
),
Tool(
name="rep_interaction_stats",
description=(
"Per-rep aggregated interaction stats over a date range "
"(POST /v2/stats/interaction): longest monologue, longest customer story, "
"interactivity, patience, question rate. Covers only calls that had Whisper "
"enabled, so a rep with few recorded calls looks like a rep with bad numbers."
),
inputSchema={
"type": "object",
"properties": {
"fromDate": {"type": "string", "description": "YYYY-MM-DD"},
"toDate": {"type": "string", "description": "YYYY-MM-DD"},
"user_ids": {"type": "array", "items": {"type": "string"}},
},
"required": ["fromDate", "toDate"],
},
),
Tool(
name="deal_risk_digest",
description=(
"Derived signal, not a Gong endpoint. Joins tracker definitions to tracker "
"occurrences across a date range and reports which calls and accounts hit "
"the risk trackers named in GONG_RISK_TRACKERS, split by whether the "
"CUSTOMER or your own rep said it. Gong has no public deals endpoint; this "
"is the closest honest substitute. Attribute nothing to a deal stage from "
"this output — join it to your CRM for that."
),
inputSchema={
"type": "object",
"properties": {
"fromDateTime": {"type": "string", "description": "ISO-8601"},
"toDateTime": {"type": "string", "description": "ISO-8601"},
"tracker_names": {
"type": "array",
"items": {"type": "string"},
"description": "Override GONG_RISK_TRACKERS for this call.",
},
"workspace_id": {"type": "string"},
},
"required": ["fromDateTime"],
},
),
]
@server.call_tool()
async def call_tool(name: str, arguments: dict[str, Any]) -> list[TextContent]:
if name == "find_calls":
params = _date_filter(arguments, keys=("fromDateTime", "toDateTime"))
rows: list[dict[str, Any]] = []
cursor: str | None = None
truncated = False
for page in range(max(1, GONG_MAX_PAGES)):
q = dict(params)
if cursor:
q["cursor"] = cursor
data = await gong_request("GET", "/v2/calls", params=q)
rows.extend(data.get("calls", []) or [])
cursor = (data.get("records") or {}).get("cursor")
if not cursor:
break
truncated = page == max(1, GONG_MAX_PAGES) - 1
return [TextContent(type="text", text=str(_slim_calls(rows, truncated)))]
if name == "list_trackers":
params: dict[str, Any] = {}
workspace = arguments.get("workspace_id") or GONG_WORKSPACE_ID
if workspace:
params["workspaceId"] = workspace
data = await gong_request("GET", "/v2/settings/trackers", params=params)
trackers = [
{
"trackerId": t.get("trackerId"),
"trackerName": t.get("trackerName"),
"affiliation": t.get("affiliation"),
"keywords": [
kw
for lang in (t.get("languageKeywords") or [])
for kw in (lang.get("keywords") or [])
][:20],
}
for t in (data.get("keywordTrackers") or [])
]
return [
TextContent(
type="text",
text=str(
{
"trackers": trackers,
"note": "Definitions only — no match counts. Occurrences come from call_signals.",
}
),
)
]
if name == "call_signals":
body: dict[str, Any] = {"contentSelector": SIGNALS_CONTENT_SELECTOR}
call_ids = arguments.get("call_ids")
if call_ids:
body["filter"] = {"callIds": [str(c) for c in call_ids]}
else:
if not arguments.get("fromDateTime"):
raise ValueError("Pass call_ids, or fromDateTime to scope a date range.")
body["filter"] = _date_filter(arguments, keys=("fromDateTime", "toDateTime"))
calls, truncated = await paged_post("/v2/calls/extensive", body, "calls")
return [TextContent(type="text", text=str(_slim_signals(calls, truncated)))]
if name == "call_transcript":
justification = (arguments.get("justification") or "").strip()
if len(justification) < 10:
raise ValueError("justification is mandatory and must be at least 10 characters.")
if not GONG_ALLOW_TRANSCRIPTS:
raise PermissionError(
"call_transcript is disabled. Verbatim transcripts put full customer "
"speech into the model context. Set GONG_ALLOW_TRANSCRIPTS=true only "
"after confirming that is allowed for this data."
)
call_ids = [str(c) for c in (arguments.get("call_ids") or [])]
if not call_ids:
raise ValueError("call_ids must be a non-empty list.")
if len(call_ids) > GONG_MAX_TRANSCRIPT_CALLS:
raise ValueError(
f"Refusing {len(call_ids)} transcripts in one call; the cap is "
f"{GONG_MAX_TRANSCRIPT_CALLS}. Narrow the question with call_signals "
"first, or raise GONG_MAX_TRANSCRIPT_CALLS deliberately."
)
data = await gong_request(
"POST", "/v2/calls/transcript", json={"filter": {"callIds": call_ids}}
)
return [
TextContent(
type="text",
text=str(
{
"justification": justification,
"callTranscripts": data.get("callTranscripts", []),
}
),
)
]
if name == "rep_interaction_stats":
body: dict[str, Any] = {
"filter": {
"fromDate": arguments["fromDate"],
"toDate": arguments["toDate"],
}
}
if v := arguments.get("user_ids"):
body["filter"]["userIds"] = [str(u) for u in v]
rows, truncated = await paged_post("/v2/stats/interaction", body, "usersAggregateActivity")
return [
TextContent(
type="text",
text=str(
{
"users": rows,
"truncated": truncated,
"caveat": (
"Stats derive only from calls with Whisper enabled. Low call "
"volume reads as poor metrics; check call counts before coaching."
),
}
),
)
]
if name == "deal_risk_digest":
wanted = [t.lower() for t in (arguments.get("tracker_names") or GONG_RISK_TRACKERS)]
body = {
"filter": _date_filter(arguments, keys=("fromDateTime", "toDateTime")),
"contentSelector": SIGNALS_CONTENT_SELECTOR,
}
calls, truncated = await paged_post("/v2/calls/extensive", body, "calls")
return [TextContent(type="text", text=str(_risk_digest(calls, wanted, truncated)))]
raise ValueError(f"Unknown tool: {name}")
# ----- Response slimming (keep model payloads tractable) -----
def _slim_calls(calls: list[dict[str, Any]], truncated: bool) -> dict[str, Any]:
rows = [
{
"id": c.get("id"),
"title": c.get("title"),
"started": c.get("started"),
"duration_s": c.get("duration"),
"direction": c.get("direction"),
"url": c.get("url"),
}
for c in calls
]
return {"count": len(rows), "truncated": truncated, "calls": rows}
def _external_parties(call: dict[str, Any]) -> list[str]:
return [
p.get("name") or p.get("emailAddress") or "?"
for p in (call.get("parties") or [])
if (p.get("affiliation") or "").lower() == "external"
]
def _slim_signals(calls: list[dict[str, Any]], truncated: bool) -> dict[str, Any]:
rows = []
for c in calls:
meta = c.get("metaData") or {}
content = c.get("content") or {}
rows.append(
{
"id": meta.get("id"),
"title": meta.get("title"),
"started": meta.get("started"),
"outcome": (content.get("callOutcome") or {}).get("category"),
"external_parties": _external_parties(c),
"trackers": [
{"name": t.get("name"), "count": t.get("count")}
for t in (content.get("trackers") or [])
if t.get("count")
],
"brief": content.get("brief"),
"key_points": [kp.get("text") for kp in (content.get("keyPoints") or [])],
"topics": [
{"name": t.get("name"), "duration_s": t.get("duration")}
for t in (content.get("topics") or [])
],
}
)
return {"count": len(rows), "truncated": truncated, "calls": rows}
def _risk_digest(
calls: list[dict[str, Any]], wanted: list[str], truncated: bool
) -> dict[str, Any]:
"""Join tracker occurrences to speaker affiliation, per call.
Speaker affiliation is the load-bearing part. "Pricing Pushback" said by your own
rep is a rep-behavior signal; said by the customer it is a deal signal. Counting
them together produces a risk number that moves for the wrong reasons.
"""
hits = []
for c in calls:
meta = c.get("metaData") or {}
parties = {p.get("speakerId"): p for p in (c.get("parties") or []) if p.get("speakerId")}
matched = []
for tracker in (c.get("content") or {}).get("trackers") or []:
if (tracker.get("name") or "").lower() not in wanted:
continue
by_side = {"customer": 0, "internal": 0, "unattributed": 0}
for occ in tracker.get("occurrences") or []:
party = parties.get(occ.get("speakerId"))
affiliation = (party or {}).get("affiliation", "")
if affiliation.lower() == "external":
by_side["customer"] += 1
elif affiliation.lower() == "internal":
by_side["internal"] += 1
else:
by_side["unattributed"] += 1
if not any(by_side.values()):
# Tracker matched but occurrences were not exposed; report the count
# rather than dropping the signal, and mark it unattributed.
by_side["unattributed"] = tracker.get("count") or 0
matched.append({"tracker": tracker.get("name"), "said_by": by_side})
if matched:
hits.append(
{
"call_id": meta.get("id"),
"title": meta.get("title"),
"started": meta.get("started"),
"external_parties": _external_parties(c),
"risk_trackers": matched,
}
)
return {
"calls_scanned": len(calls),
"calls_with_risk_signals": len(hits),
"truncated": truncated,
"risk_trackers_checked": wanted,
"hits": hits,
"note": (
"Derived from tracker occurrences on calls. Gong's public API exposes no "
"deal-board read endpoint — join call_id or account name to your CRM for "
"stage, amount, and close date. Do not treat this as a forecast."
),
}
# ----- Entrypoint -----
async def main() -> None:
require_config()
async with stdio_server() as (read, write):
await server.run(read, write, server.create_initialization_options())
if __name__ == "__main__":
asyncio.run(main())