Un serveur Model Context Protocol en lecture seule qui donne à Claude un accès délimité à votre compte Gong : découverte des calls, définitions de trackers, signaux analysés par call, statistiques d’interaction par rep, et un outil dérivé qui indique quels trackers de risque se sont déclenchés sur quels calls — en séparant selon que c’est le client qui l’a dit ou votre propre rep. Le scaffold se trouve dans le bundle d’artefacts sous apps/web/public/artifacts/mcp-server-gong-revops/, qui livre README.md, pyproject.toml et src/gong_revops_mcp/server.py, installable avec pip install -e ..
Commencez par ce que l’API n’a pas, parce que cela détermine la forme de tout le reste. L’API publique de Gong n’expose aucun endpoint de lecture pour les données du deal board. Les endpoints CRM (GET /v2/crm/entities) ne renvoient que les objets que vous avez préalablement téléversés via une intégration CRM générique enregistrée, et la documentation de Gong qualifie cet endpoint de vérification en phase de développement. Un serveur qui promet « demandez à Claude ce qu’il en est de vos deals Gong » fait donc l’une de ces trois choses : il enveloppe l’UI, il lit votre CRM à la place, ou il devine. Celui-ci dérive le risque deal des conversations et le dit : deal_risk_digest renvoie les hits de trackers avec une note vous indiquant de joindre call_id à votre CRM pour la stage, le montant et la date de clôture.
Quand l’utiliser
Sortez-le quand une question RevOps récurrente coûte dix minutes de clics à un humain : quels comptes ont contesté le prix la semaine dernière, sur quels calls un concurrent a été nommé, si les reps d’un segment en difficulté monologuent. Ce sont des jointures à l’intérieur des données de Gong que l’UI vous fait faire à l’œil. Deux rôles en tirent le plus. Le responsable RevOps qui anime une pipeline review hebdomadaire pose la question en langage naturel et colle une réponse structurée dans le deck. Le GTM engineer qui écrit un script jetable contre /v2/calls/extensive à chaque nouvelle question dispose déjà du contentSelector, de la pagination par curseur, du rate limiter et de l’attribution de locuteur.
C’est aussi le bon motif si vous exploitez déjà le serveur MCP Salesforce pour RevOps ou celui de Clari et que vous voulez la couche conversation sur la même surface de chat, pour qu’une question puisse passer de « qu’a dit le client » à « à quelle stage en est-on » sans changer d’onglet. Ce passage est le vrai gain : aucun des deux systèmes n’y répond seul.
Quand NE PAS l’utiliser
Gong livre déjà un serveur MCP officiel. Gong a annoncé la prise en charge de MCP en 2026 et documente un serveur MCP hébergé par Gong, disponible sur n’importe quel plan Gong, configuré par un administrateur technique, avec un accès régi par le niveau de siège. Il permet à Claude, ChatGPT et Microsoft Copilot d’interroger comptes et deals et de récupérer les insights générés par l’IA de Gong. Essayez-le d’abord. Il est first-party, ne demande aucun processus à héberger et respecte les permissions par niveau de siège de Gong, ce que ce scaffold ne fait pas. Construisez la version auto-hébergée quand vous avez besoin d’une surface d’outils figée et auditable — un contentSelector que vous contrôlez, un kill-switch de transcriptions, un plafond de pages, une sortie de trackers avec attribution de locuteur — ou quand votre administrateur n’active pas le serveur hébergé.
Vous n’obtenez pas d’administrateur pour générer une clé API. Les identifiants viennent de Company Settings → Ecosystem → API et seul un administrateur technique peut les créer. Il n’existe pas de clé par utilisateur.
La visibilité des calls par utilisateur est déterminante chez vous. Une seule clé au niveau du compte voit tous les calls des workspaces qu’elle couvre, quel que soit l’humain qui discute. Si votre instance Gong restreint qui peut écouter les calls de qui, ce serveur contourne cette règle. Exploitez-le par analyste avec des clés à portée étroite, ou pas du tout.
Vous voulez les transcriptions verbatim dans le modèle par défaut. Ici elles sont coupées, et le design considère que c’est le bon choix. Si votre workflow est transcription-d’abord, vous lutterez contre le scaffold.
Une ou deux questions par mois. Les filtres de l’UI Gong sont plus rapides qu’un setup à maintenir.
Ce qu’il expose
Six outils de lecture, aucun d’écriture. La surface d’écriture de l’API publique se limite au téléversement de calls et d’objets CRM génériques ; ni l’un ni l’autre n’a sa place derrière un prompt de chat, et la lecture seule supprime toute la classe de panne « le modèle m’a mal compris et a modifié le système de référence ».
find_calls — GET /v2/calls. Métadonnées seulement : id, titre, début, durée, direction, URL Gong. Délimitez la question ici d’abord.
list_trackers — GET /v2/settings/trackers. Définitions uniquement. Gong ne renvoie aucun décompte de correspondances depuis cet endpoint, ce qui surprend ; les décomptes d’occurrences viennent de l’endpoint extensive des calls.
call_signals — POST /v2/calls/extensive. Le cheval de trait : participants, correspondances de trackers, occurrences de trackers, brief Spotlight, key points, issue automatique du call, sujets, temps de parole, statistiques d’interaction par personne, commentaires publics.
call_transcript — POST /v2/calls/transcript. Coupé sauf si GONG_ALLOW_TRANSCRIPTS=true, plafonné à 3 calls, exige une justification.
rep_interaction_stats — POST /v2/stats/interaction. Monologue le plus long, plus longue histoire client, interactivité, patience, taux de questions.
deal_risk_digest — dérivé. Joint les définitions de trackers aux occurrences sur une plage de dates et classe chaque hit en customer, internal ou unattributed.
Posture d’ingénierie
L’attribution de locuteur est tout l’intérêt du digest. « Pricing Pushback » dit par votre propre rep est un signal sur le comportement du rep. Dit par le client, c’est un signal deal. Un décompte de trackers qui additionne les deux bouge pour les mauvaises raisons et produit un chiffre de risque sur lequel personne ne peut agir. deal_risk_digest lit content.trackerOccurrences, cherche chaque speakerId dans le tableau parties du call et sépare selon l’affiliation de la partie. C’est pourquoi le serveur demande les occurrences et pas seulement les décomptes, et c’est la seule chose qu’un wrapper Gong générique ne fera pas pour vous.
Les médias ne sont jamais demandés. Le contentSelector dans server.py est figé, non pilotable par l’appelant, et omet media. La clé ne porte pas api:calls:read:media-url. Le serveur ne génère donc jamais les liens audio/vidéo signés 8 heures de Gong — un lien qui survit à la conversation où il est apparu est une fuite qui attend une capture d’écran.
Les transcriptions sont un kill-switch, pas un prompt.call_transcript vérifie une variable d’environnement avant de s’exécuter et plafonne à trois calls. Se fier à la seule chaîne de justification laisse la parole verbatim du client à une mauvaise lecture assurée de la fenêtre de contexte. Le flag transforme « est-ce qu’on autorise cela, au fond ? » en décision de déploiement plutôt qu’en décision par question.
La pagination est plafonnée et le plafond est signalé.GONG_MAX_PAGES vaut 5 par défaut : un appel d’outil lit au plus 500 enregistrements et renvoie truncated: true s’il s’est arrêté avant. Un modèle qui voit silencieusement la moitié des données répond avec assurance à la mauvaise question.
Les requêtes sont sérialisées, pas réessayées. Gong plafonne par défaut à 3 requêtes par seconde et 10 000 requêtes par jour, en renvoyant 429 avec un en-tête Retry-After. Le scaffold attend 0,34 s entre deux requêtes au lieu de tirer en parallèle et de réagir aux 429, parce qu’une tempête de réessais réactifs consomme quand même le quota quotidien sur des requêtes vouées à échouer.
Réalité des coûts
Trois postes, plus un qui n’en est pas un.
Abonnement Claude. Ce que vous payez déjà — Pro à 20 $/utilisateur/mois, Max à 100–200 $/utilisateur/mois, ou consommation API. Le serveur n’y change rien.
Auto-hébergement. Un processus Python local par utilisateur de Claude Desktop : coût d’infrastructure nul. En service partagé, une petite VM à environ 20–50 $/mois sur n’importe quel cloud.
Quota de l’API Gong. Gratuit avec votre contrat Gong, non facturé en dollars, mais fini : 3 requêtes par seconde et 10 000 requêtes par jour et par entreprise par défaut, relevables en contactant le support Gong. Budgétez-le. Un deal_risk_digest sur 90 jours dans un workspace de 4 000 calls fait 40 pages de 100 = 40 requêtes. Dix questions de ce type par jour font 400 requêtes, confortablement sous le plafond. Ce qui casse le budget, c’est une boucle de curseur sans borne — c’est exactement pour cela que GONG_MAX_PAGES existe.
Sièges Gong. Gong ne publie pas de tarif public ; c’est devisé par siège avec des frais de plateforme. Ce que vous payez ne change pas avec ce serveur : il n’ajoute aucun siège.
Le coût en tokens est dominé par les payloads de réponse, d’où l’amincissement de chaque réponse dans server.py avant renvoi. call_signals sur 20 calls renvoie des briefs et des key points plutôt que le contenu complet et se situe dans les dizaines de milliers de tokens basses. Un call_transcript sur un call de 45 minutes est comparable à lui seul, et c’est le véritable argument pour laisser les transcriptions coupées.
Face aux alternatives
Le serveur MCP officiel de Gong. Traité plus haut : essayez-le d’abord. First-party, tous les plans, permissions par niveau de siège, rien à héberger. Prenez le scaffold auto-hébergé quand vous voulez une surface d’outils qui tient dans un fichier et que vous pouvez figer, ou quand le serveur hébergé n’est pas activé pour vous.
Un serveur MCP Gong communautaire. Plusieurs existent sur GitHub et dans les annuaires MCP, la plupart enveloppant calls et transcriptions. Plus rapide à installer que ce scaffold à lire. La contrepartie : « enveloppe calls et transcriptions » veut dire la plupart du temps transcriptions actives par défaut, aucun plafond de pages et des décomptes de trackers sans attribution de locuteur — les trois choix que ce scaffold tranche différemment à dessein.
Un script jetable contre /v2/calls/extensive. Contrôle maximal, et chaque équipe reconstruit à la main l’auth Basic, l’URL de base propre au compte, la pagination par curseur, le rate limiter et la jointure sur parties. Ce scaffold fait environ 450 lignes avec tout cela déjà câblé.
L’UI de Gong et Spotlight. Plus rapide pour un call isolé, et les données y sont déjà. Cela ne peut pas joindre les données Gong au reste de votre contexte Claude, seule raison d’exploiter tout ceci. Si vous hésitez entre un serveur MCP et un Skill pour votre problème, lisez Claude Skill face au serveur MCP.
Points de vigilance
Le README documente les sept ; les cinq déterminants :
Une mauvaise URL de base renvoie 401, pas 404. L’URL de base de l’API Gong est propre au compte et https://api.gong.io est un défaut répandu, pas universel. Des équipes perdent un après-midi à déboguer des identifiants qui étaient corrects. Garde-fou : _raise_for_gong intercepte le 401 et nomme l’URL de base réellement utilisée, en listant l’écart d’URL de base comme première cause avant les identifiants.
Un tracker renommé se lit comme une bonne nouvelle.deal_risk_digest compare les noms de trackers à l’exact, donc un tracker renommé dans Gong cesse de correspondre et le digest annonce zéro risque. Garde-fou : partiel — lancez list_trackers d’abord et collez les vrais noms dans GONG_RISK_TRACKERS ; les valeurs par défaut livrées sont des placeholders qui ne correspondent à rien dans la plupart des workspaces. Émettre un avertissement quand un nom configuré ne correspond à aucun tracker vivant est le TODO #3 du README.
Les statistiques d’interaction pénalisent le faible volume de calls. Les statistiques de Gong ne dérivent que des calls avec Whisper activé, donc un rep avec trois calls enregistrés est statistiquement indiscernable d’un rep en réelle difficulté. Garde-fou : rep_interaction_stats renvoie cette réserve en ligne dans chaque réponse, pour que le modèle la répète au lieu de coacher sur du bruit ; joignez les décomptes de find_calls avant de montrer les chiffres à un manager.
Troncature silencieuse. Une boucle de curseur arrêtée au plafond de pages ressemble trait pour trait à une réponse complète. Garde-fou : tout outil paginé renvoie truncated: true s’il s’est arrêté avant, et find_calls est le moyen économique de vérifier le volume avant une question coûteuse.
Dérive du consentement. Un client qui a consenti à être enregistré n’a pas pour autant consenti à être résumé par un modèle tiers. Garde-fou : les transcriptions sont coupées par défaut et aucune URL de média n’est générée ; vérifiez votre DPA avant de basculer GONG_ALLOW_TRANSCRIPTS.
Stack
Gong — conversation intelligence, trackers, briefs Spotlight, statistiques d’interaction
MCP Python SDK — mcp>=1.2.0 ; fournit Server, stdio_server et les décorateurs du registre d’outils
httpx — client REST asynchrone contre l’hôte de l’API Gong de votre compte, auth Basic avec base64("key:secret")
Claude Desktop ou Claude Code — interface en langage naturel et appelant d’outils
GONG_ALLOW_TRANSCRIPTS — le verrou au niveau de l’environnement qui décide si la parole verbatim du client atteint le modèle
GONG_MAX_PAGES — le garde-fou de quota qui rend aussi visible au modèle que la réponse est incomplète
# 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())