Gong MCP

Live

OAUTH 2.1

REVENUE INTELLIGENCE

CRM & Sales

Gong MCP gives agents authenticated access to your revenue intelligence: ask about any account or deal and get synthesized answers, not raw call dumps.

  • Per-user credentials: each call uses the actual user's token, never a shared bot.
  • Encrypted per-tenant vault: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: pre-call scope check, 90-day SIEM-exportable audit chain.
Gong MCP
agent · Acme Q3
Run
What risks came up on the Acme Corp renewal in the last 30 days?
S
gongmcp_ask_deal
112ms
Gong agent
3 risks across 5 calls: security review stalled since Oct 9, champion Dana Ortiz quiet after the pricing call, competitor raised twice. Next step owner unassigned.
Sources: 5 calls, 2 reps, Oct 1 to Oct 28
gongmcp
5 calls
18:29
Message Claude...

Tools your revenue agent reaches for on Gong, scoped per user.

CALL ANY TOOL
Query your revenue intelligence over MCP: account answers, deal answers, and structured briefs synthesized from Gong calls and messages.
gongmcp_ask_account
Ask about an account
Answer natural-language questions about a CRM account by analyzing Gong calls and messages in a time range. Returns synthesized insights, not raw data.
Parameters
Name
Type
Required
Description
crmAccount
string
Required
The CRM account name (e.g. 'Cisco Systems Inc') or direct CRM ID. Name lookup uses exact matching.
question
string
Required
Natural-language question about the account: themes, risks, blockers, stakeholders, goals, or next steps.
fromDateTime
string
Optional
Inclusive start of the activity window in ISO 8601 with timezone. Omit both dates to default to the last 30 days.
toDateTime
string
Optional
Inclusive end of the activity window in ISO 8601 with timezone. Must be later than fromDateTime.
workspace
string
Optional
Required when the account has multiple workspaces. Numeric workspace ID or case-insensitive name.
gongmcp_ask_deal
Ask about a deal
gongmcp_generate_brief
Generate a brief
Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Gong tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["gongmcp"], toolNames: [
    "gongmcp_ask_account",
    "gongmcp_ask_deal",
    "gongmcp_generate_brief"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "What risks came up on the Acme Corp renewal?" }] });
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["gongmcp"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Summarize objections on the Globex expansion deal." }],
  tools,
});

// Execute the tool call with the user's vaulted Gong credential
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["gongmcp"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Who are the key stakeholders at Cisco Systems?" }],
  tools,
});

// Tool call runs with the user's vaulted Gong credential
await sk.tools.executeTool(msg.content, "user_123");
import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["gongmcp"] }, pageSize: 100,
});

const agent = new Agent({
  name: "gong_revenue_agent",
  model: "gemini-2.5-pro",
  instruction: "Answer deal and account questions from Gong for the signed-in user.",
  tools,
});

await agent.run("Generate a Key Players brief for the Acme Corp account.");
Try these prompts
Copy any prompt into your agent. Each maps directly to a Gong tool. Click to copy, paste into your agent, done.
Deal risk & review
Copy the prompt
Copied
What risks came up on the Acme Corp renewal in the last 30 days?
Copy the prompt
Copied
Summarize objections on the Globex expansion deal.
Copy the prompt
Copied
Has pricing come up on the Initech opportunity since October 1?
Account intelligence
Copy the prompt
Copied
Who are the key stakeholders at Cisco Systems based on recent calls?
Copy the prompt
Copied
What business goals has Acme Corp mentioned this quarter?
Copy the prompt
Copied
Any competitor mentions across Globex activity in the last 90 days?
Briefs & handovers
Copy the prompt
Copied
Generate a Key Players brief for the Acme Corp account.
Copy the prompt
Copied
Build a Pain Points brief for the Globex deal before Friday's review.
Copy the prompt
Copied
Prep a handover brief for the Initech contact covering the last 90 days.
SEE HOW AUTH WORKS
Your users connect once. Their Gong credentials stay vaulted, every call is scope-checked, and every action is logged.
1
Authorize
Your user connects
Gong MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Gong MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Gong MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Gong MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other revenue connectors.
SALES
Deal intelligence agent
Combine Gong, Attio, and Slack signals to surface deal risks and next-best actions. Updated after every call.
SALES
Sales call prep agent
Pull Granola notes and Attio contact history to draft a pre-call brief before every sales meeting. Zero rep input.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with identity, scope enforcement, and audit. Connectors follow.
01.
Shared tokens break per-user analytics
A shared Gong token looks fine in a demo. In production every deal question runs as one service account: reps can reach calls they should never see, and you cannot tell who asked what. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Gong today. Ten connectors tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Gong as the user or through a shared key?
As the user. Scalekit resolves the credential of the person who triggered the agent at request time, so every account question and brief in your audit trail is attributed to a real user, not a shared service account. Gong's own visibility rules apply per user.
Where is the Gong token stored?
In an AES-256 encrypted vault with per-tenant namespacing. Tokens are resolved at request time, never enter LLM context, refresh automatically, and can be revoked from one dashboard.
Can I limit what the agent does in Gong?
Yes. Filter by tool name in listScopedTools to expose only what you want, for example deal questions without brief generation. Scalekit also enforces scope checks before every API call, and you choose the authorization scopes when you create the Gong integration.
What happens when a user revokes access?
The credential is invalidated at the next tool call. The call fails closed, other users' connections are unaffected, and the revocation is logged in the audit chain.
How is Gong MCP different from the Gong REST connector?
The Gong connector exposes raw API endpoints: list calls, pull transcripts, fetch stats. Gong MCP delivers tools over the Model Context Protocol that return synthesized answers about accounts, deals, and contacts, so your agent gets insights instead of payloads to parse. Scalekit vaults and scopes both the same way, behind one auth layer.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""gongmcp"": {
""url"": ""https://mcp.scalekit.com/gongmcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.gongmcp]
url = ""https://mcp.scalekit.com/gongmcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""gongmcp"": {
""url"": ""https://mcp.scalekit.com/gongmcp"",
""type"": ""http""
}
}
}