How to integrate Gong MCP with Mastra AI

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Gong Logo
Mastra AI Logo
divider

Introduction

This guide walks you through connecting Gong to Mastra AI 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 Mastra AI 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:
  • Set up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes Gong tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Gong tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your Gong agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

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:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Gong through MCP.

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_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 your requests to Composio
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

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

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session

Create a Tool Router session for Gong

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["gong"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Gong MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "gong" for Gong access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the Gong toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "gong-mastra-agent",
    instructions: "You are an AI agent with Gong tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        gong: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Gong toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

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

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

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

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["gong"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      gong: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "gong-mastra-agent",
    instructions: "You are an AI agent with Gong tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { gong: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Gong through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows

How to build Gong MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Gong MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Gong MCP with Claude Agent SDK

Google ADK

Google ADK

Use Gong MCP with Google ADK

LangChain

LangChain

Use Gong MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Gong MCP with Vercel AI SDK

LlamaIndex

LlamaIndex

Use Gong MCP with LlamaIndex

CrewAI

CrewAI

Use Gong MCP with CrewAI

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 Mastra AI?

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

Book a call↗Get started for free