How to integrate Gong MCP with LlamaIndex

This guide walks you through connecting Gong to LlamaIndex using the Composio tool router. By the end, you'll have a working Gong agent that can create a new gong meeting with your team, list user activity statistics for last week, add call recording media to a specific call through natural language commands. This guide will help you understand how to give your LlamaIndex 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.

Gong logoGong
BasicOauth2

Gong is a platform for video meetings, call recording, and team collaboration. It helps teams capture conversations, analyze calls, and turn insights into action.

57 Tools

Introduction

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

This guide will help you understand how to give your LlamaIndex 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.

Also integrate Gong with

TL;DR

Here's what you'll learn:
  • Set your OpenAI and Composio API keys
  • Install LlamaIndex and Composio packages
  • Create a Composio Tool Router session for Gong
  • Connect LlamaIndex to the Gong MCP server
  • Build a Gong-powered agent using LlamaIndex
  • Interact with Gong through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

  • ReAct Agent: Reasoning and acting pattern for tool-using agents
  • MCP Tools: Native support for Model Context Protocol
  • Context Management: Maintain conversation context across interactions
  • Async Support: Built for async/await patterns

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.

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

What is Composio SDK?

Composio's Composio SDK 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 Composio SDK

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

How the Composio SDK works

The Composio SDK 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

Step by step10 STEPS
1

Prerequisites

Before you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Gong account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Gong

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID
3

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Gong access
5

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called gong_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

7

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["gong"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Gong actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, gong)
  • The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
  • LlamaIndex will connect to this endpoint to dynamically discover and use the available Gong tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

  • We're creating a direct terminal interface to chat with Gong
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Gong tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Gong
10

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Gong, then start asking questions.

Complete Code

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

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["gong"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Gong actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Gong to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Gong tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.
TOOLS

Supported Tools

Every Gong action and event your agent gets out of the box.

Add call media

Adds a call media, recorded by a telephony system (PBX) or other media recording facility.

Add new call v2 calls

When 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 api

Lists the aggregated activity of multiple users within the Gong system for each time period within the defined date range.

Aggregate user activity statistics

Lists the activity of multiple users within the Gong system during a defined period.

Assign prospects to flow

Use this endpoint to assign a number of prospects to a flow.

Retrieve activity scorecards report

Retrieve 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 meetings

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:meetings:user:create'.

Create permission profile v2 permission profile

Create a permission profile in a given workspace.

Data privacy for phone number

Shows the elements in the Gong system that reference the given phone number.

Delete a generic CRM integration

Deletes an existing generic CRM integration from the Gong platform.

Delete Meeting

Deletes a Gong meeting created via the Meetings API (Beta).

Delete users from call access list

Remove individual user access from calls.

Erase data for email address

Erase all data associated with an email address from Gong (GDPR compliance).

Erase data for phone number

Given 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 profiles

Returns a list of all permission profiles.

Get Call By ID

Tool to fetch specific call metadata by call ID.

Get Call Transcript

Tool to retrieve call transcripts from Gong.

Get Crm Integration Details

Retrieves details of generic CRM integrations registered with Gong.

Get crm objects v2 crm entities

Retrieves specific CRM objects by their IDs from Gong's CRM integration.

Get Flow Prospects

Tool to retrieve Gong Engage flows assigned to specified prospects.

Get Interaction Statistics

Tool to retrieve interaction trend statistics for users based on calls with Whisper enabled.

Get permission profile

Returns a permission profile.

Get CRM Request Status

The GetCRMRequestStatus endpoint retrieves the current status of CRM integration requests in the Gong platform.

Get User By ID

Tool to retrieve individual user details by user ID.

Get User Settings History

Tool to retrieve historical changes to a user's settings.

List all coaching metrics v2 coaching

List all of the coaching metrics of a manager.

List all company workspaces v2 workspaces

Returns a list of all workspaces including their details.

List all users v2 users

List all of the company's users.

List Call Outcomes

Tool to retrieve all available call outcomes defined in Gong.

List Flow Folders

Tool to list all Gong Engage flow folders with visibility types.

List Folder Calls

Given a folder id, this endpoint retrieves a list of calls in it.

List gong engage flows v2 flows

Engage 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 schema

Retrieves schema fields for a specific CRM object type within a Generic CRM integration.

List Scorecards

Tool to retrieve all scorecards within the Gong system.

List Tasks

Tool to retrieve Engage tasks assigned to a specific user with filtering options.

List users by filter v2 users extensive

List multiple Users.

Get user call access

Retrieves a list of users who have been granted individual access to specific calls through the API.

Post a digital interaction v2 digital interaction

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:digital-interactions:write'.

Post day by day activity stats

Retrieve the daily activity of multiple users within the Gong system for a range of dates.

Register Crm Integration

Updates an existing CRM integration in the Gong platform.

Report Content Share Event

Tool to push content share engagement events to Gong's activity timeline.

Report Content View Event

Tool to log content view engagement events to Gong's activity timeline.

Report Custom Engagement Event

Report custom engagement events to Gong's activity timeline.

Retrieve call data by date range v2 calls

List calls that took place during a specified date range.

Retrieve data privacy info for email address

Retrieves data privacy information for a third-party email address.

Retrieve filtered call details

Lists 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 folders

Use this endpoint to retrieve a list of public library folders.

Retrieve logs data by type and time range v2 logs

List log entries that took place during a specified time range.

Retrieve manual crm call associations

Returns a list of all calls that were manually associated or re-associated with CRM account and deal/opportunity since a given time.

Retrieve tracker details v2 settings trackers

Retrieves details of all keyword trackers in the system or in a given workspace.

Retrieve users from permission profile

Returns a list of all users whose access is controlled by the given permission profile.

Set User Call Access

Give individual users access to calls.

Unassign Flows By CRM ID

Tool to unassign flows from prospects by their CRM Prospect ID.

Update a gong meeting v2 meetings meetingid

When accessed through a Bearer token authorization method, this endpoint requires the scope 'api:meetings:user:update'.

Update permission profile v2 permission profile

Update a permission profile.

Upload crm objects v2 crm entities

Uploads CRM entity data to Gong via LDJSON file.

Validate Meeting Integration

Validates Gong meeting integration status for one or more users by their email addresses.

FAQ

Frequently asked questions

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.

Yes, you can. LlamaIndex 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.

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.

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.

Start with Gong.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Gong tool your agent needs.Free to start.

Start building