How to integrate Google Meet MCP with LangChain

Connect LangChain to Google Meet MCP. Schedule a new video meeting for tomorrow, list all meetings i hosted last week, and more using natural language, with authentication handled for you.

Google Meet logoGoogle Meet
Oauth2

Google Meet is a secure video conferencing platform for virtual meetings, chat, and screen sharing. It helps teams connect, collaborate, and communicate seamlessly from anywhere.

25 Tools

Introduction

This guide walks you through connecting Google Meet to LangChain using the Composio tool router. By the end, you'll have a working Google Meet agent that can create meeting spaces, fetch recordings and transcripts, list participants, read smart notes, and end active conferences through natural language commands.

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

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

For exact tool slugs and parameter tables, see the tool catalog in the Composio docs.

Also integrate Google Meet with

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Google Meet project to Composio
  • Create a Tool Router MCP session for Google Meet
  • Initialize an MCP client and retrieve Google Meet tools
  • Build a LangChain agent that can interact with Google Meet
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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

The Google Meet MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Google Meet account. It provides structured and secure access to your meeting spaces, conferences, participants, recordings, and transcripts, so your agent can create meetings, update meeting settings, review attendance, retrieve recordings, and read transcripts on your behalf.

  • Meeting creation and configuration: Have your agent create new Google Meet spaces and update the settings of existing spaces.
  • Conference management: Direct your agent to review past conferences or end a conference that is currently active.
  • Participant and attendance review: Let the agent list meeting participants and inspect their individual attendance sessions.
  • Recording retrieval: Instruct your agent to find recordings associated with a completed conference.
  • Transcript review: Have your agent retrieve structured transcript entries with speaker, timing, and spoken text details.

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 starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming
2

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.
3

Install dependencies

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • @composio/langchain provides Composio integration for LangChain
  • @langchain/mcp-adapters enables MCP client connections
  • @langchain/core is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_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's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv/config import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Google Meet functionality through MCP
6

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Google Meet tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['googlemeet']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Google Meet tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use Google Meet tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "googlemeet-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Google Meet MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available Google Meet tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Google Meet related question or task to the agent.\n");

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

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;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

Here's the complete code to get you started with Google Meet and LangChain:

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['googlemeet']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "googlemeet-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Google Meet related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    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;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

You've successfully built a LangChain agent that can interact with Google Meet through Composio's Tool Router.

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
TOOLS

Supported Tools

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

Batch Update Google Meet Members

Update 1 to 500 Google Meet members in one space in a single batch.

Create Google Meet Space

Creates a new Google Meet space with optional access controls, moderation, recording, or transcription settings, without attaching it to a calendar event.

Create Member

Create a member in a Google Meet space, optionally assigning a co-host role.

Delete Google Meet Space Member

Deletes a member who was previously assigned roles in a Google Meet space.

End active conference

Ends an active conference in a specified Google Meet space, immediately dropping active participants.

Get conference record by name

Tool to get a specific conference record by its resource name.

Get Meet details

Retrieve details of a Google Meet space using its unique identifier.

Get Member

Get a configured Google Meet space member by resource name, including their email and meeting role.

Get Participant

Get a Google Meet conference participant by resource name, including their identity and first-join/last-leave times.

Get Participant Details

Retrieves detailed information about a specific participant session from a Google Meet conference record.

Get Recording

Get a Google Meet recording's metadata by resource name, including its state, timestamps, and Google Drive destination when available.

Get recordings by conference record ID

Retrieves recordings from Google Meet for a given conference record ID.

Get Smart Note

Get metadata for a Google Meet smart note generated by Take Notes with Gemini.

Get Transcript

Retrieves a specific transcript by its resource name.

Get Transcript Entry

Fetches a single transcript entry by resource name for targeted inspection or incremental processing.

Get transcripts by conference record ID

Lists a page of transcripts for a Google Meet conference record, with a continuation token when more results are available.

List Conference Records

Tool to list conference records.

List Members

List configured members of a Google Meet space, including their email and meeting role.

List Participants

Lists the participants in a conference record.

List Participant Sessions

Lists a page of participant sessions for a specific participant in a Google Meet conference, including session start and end times.

List Recordings

Tool to list recording resources from a conference record.

List Smart Notes

List metadata for smart notes generated by Take Notes with Gemini in a Google Meet conference.

List Transcript Entries

Tool to list structured transcript entries (speaker/time/text segments) for a specific Google Meet transcript.

Update Google Meet Member

Update an existing Google Meet space member's email or meeting role.

Update Google Meet Space

Updates the configuration of an existing Google Meet space, including access, moderation and artifact settings, using a supplied or automatically derived update mask.

FAQ

Frequently asked questions

Start with Google Meet.It takes 30 seconds.

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

Start building