How to integrate Gong MCP with CrewAI

Framework Integration Gradient
Gong Logo
CrewAI Logo
divider

Introduction

This guide walks you through connecting Gong to CrewAI using the Composio tool router. By the end, you'll have a working Gong agent that can create a new gong meeting with my team, list user activity statistics for last week, add call recording media to a specific call, show all contacts linked to this phone number through natural language commands.

This guide will help you understand how to give your CrewAI agent real control over a Gong account through Composio's Gong MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

TL;DR

Here's what you'll learn:
  • Get a Composio API key and configure your Gong connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Gong
  • Build a conversational loop where your agent can execute Gong operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

  • Agent Roles: Define specialized agents with specific goals and backstories
  • Task Management: Create tasks with clear descriptions and expected outputs
  • Crew Orchestration: Combine agents and tasks into collaborative workflows
  • MCP Integration: Connect to external tools through Model Context Protocol

What is the Gong MCP server, and what's possible with it?

The Gong MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Gong account. It provides structured and secure access to your meetings, calls, and team collaboration data, so your agent can schedule meetings, analyze call recordings, generate user activity reports, and manage CRM integrations—all on your behalf.

  • Automated meeting scheduling and management: Have your agent create new Gong meetings, ensuring your team and clients are always connected at the right time.
  • Call recording upload and analysis: Let your agent add call media, process call recordings, and help organize your sales conversations for later review.
  • User activity and scorecard reporting: Direct your agent to generate detailed reports on team activity, review scorecards, and aggregate user statistics for performance insights.
  • Prospect and flow management: Assign prospects to sales flows, helping automate outreach and follow-ups directly from your CRM data.
  • CRM integration and data privacy controls: Enable your agent to manage CRM integrations and surface all records related to specific phone numbers, ensuring compliance and streamlined operations.

Supported Tools & Triggers

Tools
Add call media v2 calls id mediaAdds a call media, recorded by a telephony system (PBX) or other media recording facility.
Add new call v2 callsWhen using this endpoint, either provide a downloadMediaUrl or use the returned callId in a follow-up request to /v2/calls/{id}/media to upload the media file.
Aggregate activity by period via apiLists the aggregated activity of multiple users within the Gong system for each time period within the defined date range.
Aggregate user activity statisticsLists the activity of multiple users within the Gong system during a defined period.
Assign prospects to flowUse this endpoint to assign a number of prospects to a flow.
Create activity scorecards reportRetrieve all the answers for the scorecards that were reviewed during a specified date range, for calls that took place during a specified date range, for specific scorecards or for specific reviewed users.
Create a new gong meeting v2 meetingsWhen accessed through a Bearer token authorization method, this endpoint requires the scope 'api:meetings:user:create'.
Create permission profile v2 permission profileCreate a permission profile in a given workspace.
Data privacy for phone numberShows the elements in the Gong system that reference the given phone number.
Delete a generic crm integration v2 crm integrationsDeletes an existing CRM integration from the Gong platform.
Delete a gong meeting v2 meetingsWhen accessed through a Bearer token authorization method, this endpoint requires the scope 'api:meetings:user:delete'.
Delete users from call access listRemove individual user access from calls.
Erase data for email addressGiven an email address, this endpoint deletes from the Gong system any calls or email messages that reference this address.
Erase data for phone numberGiven a phone number, this endpoint deletes from the Gong system any leads or contacts with a matching phone number or mobile phone number.
Fetch all permission profilesReturns a list of all permission profiles.
Get Crm Integration Details.
Get crm objects v2 crm entitiesRetrieves CRM entities from the Gong platform.
Get permission profileReturns a permission profile.
Get request status v2 crm request statusThe GetCRMRequestStatus endpoint retrieves the current status of CRM integration requests in the Gong platform.
List all coaching metrics v2 coachingList all of the coaching metrics of a manager.
List all company workspaces v2 workspacesReturns a list of all workspaces including their details.
List all users v2 usersList all of the company's users.
List flows for crm prospectsGet the Gong Engage flows assigned to the given prospects.
List Folder CallsGiven a folder id, this endpoint retrieves a list of calls in it.
List gong engage flows v2 flowsEngage flows have the following visibility types: * Company: visible to everyone in the company, can only be edited by users with edit permissions.
List schema fields v2 crm entity schemaRetrieves the comprehensive schema of CRM entities in the Gong platform.
List users by filter v2 users extensiveList multiple Users.
Manage user call accessReturns a list of users who have received individual access to calls through the API.
Post a digital interaction v2 digital interactionWhen accessed through a Bearer token authorization method, this endpoint requires the scope 'api:digital-interactions:write'.
Post day by day activity statsRetrieve the daily activity of multiple users within the Gong system for a range of dates.
Post interaction filter statsReturns interaction stats for users based on calls that have Whisper turned on.
Post meeting integration statusWhen accessed through a Bearer token authorization method, this endpoint requires the scope 'api:meetings:integration:status'.
Register Crm IntegrationUpdates an existing CRM integration in the Gong platform.
Report content viewed eventPush engagement events into Gong and display them as events in Gong’s activity timeline, when a content is viewed by an external participant (for example, a contract was “viewed” by the prospect) When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:engagement-data:write'.
Report Custom Engagement EventPush engagement events into Gong and display them as events in Gong’s activity timeline, when a content is engaged by an external participant (for example, a contract was “signed” by the prospect) When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:engagement-data:write'.
Retrieve call data by date range v2 callsList calls that took place during a specified date range.
Retrieve data for a specific call v2 calls idRetrieve data for a specific call.
Retrieve data privacy info for email addressShows the elements in the Gong system that reference the given email address.
Retrieve filtered call detailsLists detailed call data for calls that took place during a specified date range, have specified call IDs or hosted by specified users.
Retrieve library folders v2 library foldersUse this endpoint to retrieve a list of public library folders.
Retrieve logs data by type and time range v2 logsList log entries that took place during a specified time range.
Retrieve manual crm call associationsReturns a list of all calls that were manually associated or re-associated with CRM account and deal/opportunity since a given time.
Retrieve scorecards details v2 settings scorecardsRetrieve all the scorecards within the Gong system.
Retrieve tracker details v2 settings trackersRetrieves details of all keyword trackers in the system or in a given workspace.
Retrieve transcripts of calls v2 calls transcriptReturns transcripts for calls that took place during the specified date period.
Retrieve User Settings HistoryRetrieve a specific user's settings history.
Retrieve users from permission profileReturns a list of all users whose access is controlled by the given permission profile.
Retrieve user v2 users idRetrieve a specific user.
Set User Call AccessGive individual users access to calls.
Update a gong meeting v2 meetings meetingidWhen accessed through a Bearer token authorization method, this endpoint requires the scope 'api:meetings:user:update'.
Update permission profile v2 permission profileUpdate a permission profile.
Update shared content eventPush engagement events into Gong and display them as events in Gong’s activity timeline, when a Gong user shares content with external participants (for example, a contract was “shared” by the account executive with his prospects) When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:engagement-data:write'.
Upload crm objects v2 crm entitiesUploads CRM data files to the Gong platform for integration and analysis.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Gong connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

bash
pip install composio crewai crewai-tools python-dotenv
What's happening:
  • composio connects your agent to Gong via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools includes MCP helpers
  • python-dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID scopes the session to your account
  • OPENAI_API_KEY lets CrewAI use your chosen OpenAI model

Import dependencies

python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter  # optional import if you plan to adapt tools
from composio import Composio
from dotenv import load_dotenv
import os
from crewai.mcp import MCPServerHTTP

load_dotenv()
What's happening:
  • CrewAI classes define agents and tasks, and run the workflow
  • MCPServerHTTP connects the agent to an MCP endpoint
  • Composio will give you a short lived Gong MCP URL

Create a Composio Tool Router session for Gong

python
composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
session = composio.create(
    user_id=os.getenv("USER_ID"),
    toolkits=["gong"],
)
url = session.mcp.url
What's happening:
  • You create a Gong only session through Composio
  • Composio returns an MCP HTTP URL that exposes Gong tools

Configure the LLM

python
llm = LLM(
    model="gpt-5-mini",
    api_key=os.getenv("OPENAI_API_KEY"),
)
What's happening:
  • CrewAI will call this LLM for planning and responses
  • You can swap in a different model if needed

Attach the MCP server and create the agent

python
toolkit_agent = Agent(
    role="Gong Assistant",
    goal="Help users interact with Gong through natural language commands",
    backstory=(
        "You are an expert assistant with access to Gong tools. "
        "You can perform various Gong operations on behalf of the user."
    ),
    mcps=[
        MCPServerHTTP(
            url=url,
            streamable=True,
            cache_tools_list=True,
            headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")},
        ),
    ],
    llm=llm,
    verbose=True,
    max_iter=10,
)
What's happening:
  • MCPServerHTTP connects the agent to the Gong MCP endpoint
  • cache_tools_list saves a tools catalog for faster subsequent runs
  • verbose helps you see what the agent is doing

Add a REPL loop with Task and Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")
print("Try asking the agent to perform Gong operations.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Based on the conversation history:\n{conversation_context}\n\n"
            f"Current user request: {user_input}\n\n"
            f"Please help the user with their Gong related request."
        ),
        expected_output="A helpful response addressing the user's request",
        agent=toolkit_agent,
    )

    crew = Crew(
        agents=[toolkit_agent],
        tasks=[task],
        verbose=False,
    )

    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
What's happening:
  • You build a simple chat loop and keep a running context
  • Each user turn becomes a Task handled by the same agent
  • Crew executes the task and returns a response

Run the application

python
if __name__ == "__main__":
    main()
What's happening:
  • Standard Python entry point so you can run python crewai_gong_agent.py

Complete Code

Here's the complete code to get you started with Gong and CrewAI:

python
# file: crewai_gong_agent.py
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter  # optional
from composio import Composio
from dotenv import load_dotenv
import os
from crewai.mcp import MCPServerHTTP

load_dotenv()

def main():
    # Initialize Composio and create a Gong session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["gong"],
    )
    url = session.mcp.url

    # Configure LLM
    llm = LLM(
        model="gpt-5-mini",
        api_key=os.getenv("OPENAI_API_KEY"),
    )

    # Create Gong assistant agent
    toolkit_agent = Agent(
        role="Gong Assistant",
        goal="Help users interact with Gong through natural language commands",
        backstory=(
            "You are an expert assistant with access to Gong tools. "
            "You can perform various Gong operations on behalf of the user."
        ),
        mcps=[
            MCPServerHTTP(
                url=url,
                streamable=True,
                cache_tools_list=True,
                headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")},
            ),
        ],
        llm=llm,
        verbose=True,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Try asking the agent to perform Gong operations.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Based on the conversation history:\n{conversation_context}\n\n"
                f"Current user request: {user_input}\n\n"
                f"Please help the user with their Gong related request."
            ),
            expected_output="A helpful response addressing the user's request",
            agent=toolkit_agent,
        )

        crew = Crew(
            agents=[toolkit_agent],
            tasks=[task],
            verbose=False,
        )

        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

if __name__ == "__main__":
    main()

Conclusion

You now have a CrewAI agent connected to Gong through Composio's Tool Router. The agent can perform Gong operations through natural language commands. Next steps:
  • Add role-specific instructions to customize agent behavior
  • Plug in more toolkits for multi-app workflows
  • Chain tasks for complex multi-step operations

How to build Gong MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Gong MCP?

With a standalone Gong MCP server, the agents and LLMs can only access a fixed set of Gong tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Gong and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with CrewAI?

Yes, you can. CrewAI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Gong tools.

Can I manage the permissions and scopes for Gong while using Tool Router?

Yes, absolutely. You can configure which Gong scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Gong data and credentials are handled as safely as possible.

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.