Bring Revenue Intelligence
to CrewAI
Learn how to connect Gong to CrewAI and start using 14 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Gong MCP Server?
Connect your Gong account to any AI agent and unlock conversation intelligence insights through natural conversation.
What you can do
- Call Management — List all recorded calls, filter by user or date range, and inspect individual call metadata with participants and topics
- Transcripts — Retrieve full speaker-labeled transcripts for any recorded call
- Team Analytics — List all team members with roles and activity metrics, and drill into per-user call statistics
- Scorecard Evaluation — Browse scoring rubrics and retrieve call quality scores for coaching
- Deal Pipeline — View deal stages, amounts, and associated calls for pipeline visibility
- Coaching Library — Access curated calls saved to the Gong coaching library for training
- Aggregate Statistics — Retrieve org-wide call metrics: total calls, duration, talk ratios
How it works
1. Subscribe to this server
2. Enter your Gong Access Key and Access Key Secret from Company Settings > API
3. Start analyzing your conversations from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Sales Managers — review call recordings, track rep performance, and identify coaching opportunities
- Revenue Operations — correlate deal pipeline data with conversation patterns to forecast accurately
- Sales Enablement — curate best-practice calls in the coaching library and evaluate with scorecards
Built-in capabilities (14)
Verify connectivity
Get call details
Get call statistics
Get call transcript
Get user details
Get user stats
Get call scores
List calls
List calls by date range
List calls by user
List deals
List library calls
List scorecards
List users
Why CrewAI?
When paired with CrewAI, Gong becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Gong tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Gong in CrewAI
Gong and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Gong to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Gong in CrewAI
The Gong MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 14 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Gong for CrewAI
Every tool call from CrewAI to the Gong MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I access the full transcript of a recorded sales call?
Yes. Use list_calls to browse all recorded calls, then call get_transcript with the Call ID to retrieve the full speaker-labeled transcript. Each segment includes the speaker name, timestamp, and spoken text. Use get_call for additional metadata like topics discussed and action items.
Does Gong require two separate credentials?
Yes. Gong uses HTTP Basic Authentication with an Access Key and an Access Key Secret. Both are generated in Company Settings > Ecosystem > API > API Keys. The credentials are Base64-encoded and sent in the Authorization header. You must be a Technical Administrator to generate API keys.
Can I track deal pipeline data alongside call recordings?
Yes. The list_deals tool retrieves your deal pipeline with stages, amounts, and associated calls. Cross-reference with list_calls and get_call to understand which conversations influenced deal progression. Use get_call_stats for aggregate metrics like total call volume and talk ratios.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.