Skip to main content
Glama
Gong MCP

Gong MCP

by tadnir

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GONG_HEADLESSNotrue hides the sign-in browser's window; the sign-in page still shows it. Google's sign-in refuses headless Chromium. On Linux without a screen the server starts an Xvfb one (install xvfb), as the image doesfalse
GONG_LOG_FILENoWhere to write logs, e.g. /proc/1/fd/2
GONG_LOGIN_URLNoThe link handed out, when the page sits behind a reverse proxy. When set, the page starts with the server.http://localhost:<port>/
GONG_CONFIG_DIRNoWhere the session and the sign-in browser's profile are saved~/.config/gong-mcp
GONG_LOGIN_HOSTNoAddress the sign-in page listens on127.0.0.1
GONG_LOGIN_PORTNoIts port; a free one is used if another copy holds it8769
GONG_CHROMIUM_URLNoAnother Chromium to sign in withPlaywright's Chromium

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Unofficial, read-only client for the user's own Gong account, through the same endpoints as Gong's web app, signed in as the user. Unaffiliated with Gong. search_calls finds calls by date range, title, account, deal, external contact email or company participant (find_people gives participant ids); get_call gives one call's participants, duration, topics and trackers; get_call_transcript gives what was said, by speaker. list_accounts and list_deals list the CRM accounts and deals Gong shows the user; their CRM ids narrow search_calls. whoami says who is signed in and in which workspace. Call content is the user's company's confidential data: quote only what the user asks for. When a tool says the user must sign in, call gong_login and give the user the link it returns; the user signs in on that page. Never ask for their password, codes or cookies in the chat.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
gong_loginA

Get the link where the user signs in to Gong (Gong's own sign-in and the company's SSO run on that page, never in the chat). Returns the status when already signed in.

gong_session_statusA

Whether this server is signed in to Gong, since when, until when, and the sign-in link when it is not.

gong_logoutB

Forget the Gong session saved here.

whoamiA

Who is signed in to Gong: the user, the company and the workspace this server reads.

search_callsA

Find calls, newest first: by date range, title, account, deal, external contact email or company participants. Returns the total and each call's id, title, start time, duration, owner, participants, account and deal, topics and Gong's brief.

get_callA

One call's details: title, time, duration, participants (company and external), the account and deal, topics, trackers and other analysis Gong shows on the call page.

get_call_transcriptB

One call's transcript: what each speaker said, with timestamps.

find_peopleA

Look up company users, teams and external people by the start of a name or email; company users' ids are for search_calls' participantIds.

list_accountsB

CRM accounts Gong shows the user: the ones they own, or those matching a name.

list_dealsC

Deals (opportunities) Gong shows the user, or one account's.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 10 tools

Disambiguation4/5

Each tool targets a distinct resource+action: auth (login/logout), session state, identity, deals, calls, transcripts, people, accounts. The only mild overlaps are gong_session_status vs. whoami (session vs. identity) and gong_login vs. gong_session_status (both return the sign-in link), but the descriptions make the boundaries clear enough.

Naming Consistency3/5

Two conventions coexist: a gong_-prefixed namespace for auth tools (gong_login, gong_session_status, gong_logout) and bare verb_noun names for data tools (list_deals, search_calls, get_call, find_people, list_accounts), plus the outlier whoami. Each group is internally consistent and readable, but the set as a whole is mixed.

Tool Count5/5

Ten tools is well within the sweet spot, and every tool earns its place: auth lifecycle, identity, and one tool per core data object (calls, transcripts, deals, accounts, people). Nothing feels redundant or padded.

Completeness4/5

The main read workflow is fully covered: sign in, find people/accounts, list deals, search calls, fetch a call and its transcript. Minor gaps remain—there is no detail fetch for a deal or account (only list_*), and no topic/tracker-centric lookup—but agents can work around these via search_calls.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues