# How to integrate Google Meet MCP with Mastra AI

```json
{
  "title": "How to integrate Google Meet MCP with Mastra AI",
  "toolkit": "Google Meet",
  "toolkit_slug": "googlemeet",
  "framework": "Mastra AI",
  "framework_slug": "mastra-ai",
  "url": "https://composio.dev/toolkits/googlemeet/framework/mastra-ai",
  "markdown_url": "https://composio.dev/toolkits/googlemeet/framework/mastra-ai.md",
  "updated_at": "2026-11-07T07:09:30.708Z"
}
```

## Introduction

This guide walks you through connecting Google Meet to Mastra AI 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 Mastra AI 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](https://docs.composio.dev/toolkits/googlemeet).

## Also integrate Google Meet with

- [Claude Code](https://composio.dev/toolkits/googlemeet/framework/claude-code)
- [Cursor](https://composio.dev/toolkits/googlemeet/framework/cursor)
- [ChatGPT](https://composio.dev/toolkits/googlemeet/framework/chatgpt)
- [Claude Cowork](https://composio.dev/toolkits/googlemeet/framework/claude-cowork)
- [Antigravity](https://composio.dev/toolkits/googlemeet/framework/antigravity)
- [OpenAI Agents SDK](https://composio.dev/toolkits/googlemeet/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/googlemeet/framework/claude-agents-sdk)
- [Grok Bot](https://composio.dev/toolkits/googlemeet/framework/grok-bot)
- [Muse](https://composio.dev/toolkits/googlemeet/framework/muse)
- [Codex](https://composio.dev/toolkits/googlemeet/framework/codex)
- [Grok Build](https://composio.dev/toolkits/googlemeet/framework/grok-build)
- [VS Code](https://composio.dev/toolkits/googlemeet/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/googlemeet/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/googlemeet/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/googlemeet/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/googlemeet/framework/atomic-agent)
- [Pi](https://composio.dev/toolkits/googlemeet/framework/pi-agent)
- [DeepSeek Harness](https://composio.dev/toolkits/googlemeet/framework/deepseek)
- [Google ADK](https://composio.dev/toolkits/googlemeet/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/googlemeet/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/googlemeet/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/googlemeet/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/googlemeet/framework/crew-ai)
- [Pydantic AI](https://composio.dev/toolkits/googlemeet/framework/pydantic-ai)
- [AutoGen](https://composio.dev/toolkits/googlemeet/framework/autogen)

## 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 Google Meet tools
- Connect Mastra's MCP client to the Composio generated MCP URL
- Fetch Google Meet 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 Google Meet 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 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.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `GOOGLEMEET_BATCH_UPDATE_MEMBERS` | Batch Update Google Meet Members | Update 1 to 500 Google Meet members in one space in a single batch. Requires meetings.space.created. Supply nested member names and optional email or role values. A child updateMask requires an identical top-level updateMask. With neither mask, all fields are updated, including clearing unset fields. |
| `GOOGLEMEET_CREATE_MEET` | 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. Returns the space name, meeting URI and meeting code when available, and requires the meetings.space.created OAuth scope. |
| `GOOGLEMEET_CREATE_MEMBER` | Create Member | Create a member in a Google Meet space, optionally assigning a co-host role. Members configured with a role can join the space without knocking. Supply the space resource name and the member's email address. |
| `GOOGLEMEET_DELETE_MEMBER` | Delete Google Meet Space Member | Deletes a member who was previously assigned roles in a Google Meet space. Requires the full spaces/{space}/members/{member} resource name. This removes the member's space role assignment, not a participant from an active conference. Returns an empty object on success. |
| `GOOGLEMEET_END_ACTIVE_CONFERENCE` | End active conference | Ends an active conference in a specified Google Meet space, immediately dropping active participants. A response indicating there is no active conference is also treated as success; obtain explicit user confirmation before calling. |
| `GOOGLEMEET_GET_CONFERENCE_RECORD_BY_NAME` | Get conference record by name | Tool to get a specific conference record by its resource name. Use when you have the conference record ID and need to retrieve detailed information about a single meeting instance. |
| `GOOGLEMEET_GET_MEET` | Get Meet details | Retrieve details of a Google Meet space using its unique identifier. Newly created spaces may return incomplete data; retry after 1–3 seconds if needed. |
| `GOOGLEMEET_GET_MEMBER` | Get Member | Get a configured Google Meet space member by resource name, including their email and meeting role. Use when the space and member identifiers are already known. |
| `GOOGLEMEET_GET_PARTICIPANT` | Get Participant | Get a Google Meet conference participant by resource name, including their identity and first-join/last-leave times. Use when the conference record and participant IDs are known. |
| `GOOGLEMEET_GET_PARTICIPANT_SESSION` | Get Participant Details | Retrieves detailed information about a specific participant session from a Google Meet conference record. Returns session details including start time and end time for a single join/leave session. A participant session represents each unique join or leave session when a user joins a conference from a device. If a user joins multiple times from the same device, each join creates a new session. PREREQUISITE: You must first obtain the participant session resource name. Use LIST_PARTICIPANT_SESSIONS with a conference record ID and participant ID to get available sessions and their resource names. The 'name' parameter is REQUIRED and must be in the format: 'conferenceRecords/{conference_record}/participants/{participant}/participantSessions/{participant_session}' |
| `GOOGLEMEET_GET_RECORDING` | Get Recording | Get a Google Meet recording's metadata by resource name, including its state, timestamps, and Google Drive destination when available. Use when the conference record and recording identifiers are known; this does not download the recording file. |
| `GOOGLEMEET_GET_RECORDINGS_BY_CONFERENCE_RECORD_ID` | Get recordings by conference record ID | Retrieves recordings from Google Meet for a given conference record ID. Only returns recordings if recording was enabled and permitted by the organizer's domain policies; a valid conference_record_id does not guarantee recordings exist. After a meeting ends, recordings may take several minutes to process — an empty result may be temporary, not permanent. |
| `GOOGLEMEET_GET_SMART_NOTE` | Get Smart Note | Get metadata for a Google Meet smart note generated by Take Notes with Gemini. Use when the conference record and smart note identifiers are known. Returns state, timestamps, and the Google Docs destination when available, not the full note content. Fetch document content separately with the Google Docs API. |
| `GOOGLEMEET_GET_TRANSCRIPT` | Get Transcript | Retrieves a specific transcript by its resource name. Returns transcript details including state (STARTED, ENDED, FILE_GENERATED), start/end times, and Google Docs destination. PREREQUISITE: Obtain the transcript resource name first by using GET_TRANSCRIPTS_BY_CONFERENCE_RECORD_ID or construct it from known IDs. |
| `GOOGLEMEET_GET_TRANSCRIPT_ENTRY` | Get Transcript Entry | Fetches a single transcript entry by resource name for targeted inspection or incremental processing. Use when you have a specific transcript entry resource name and need to retrieve its details (text, speaker, timestamps, language). PREREQUISITE: Obtain the transcript entry resource name first by using LIST_TRANSCRIPT_ENTRIES or construct it from known IDs. The 'name' parameter is REQUIRED and must follow the format: 'conferenceRecords/{conferenceRecordId}/transcripts/{transcriptId}/entries/{entryId}' |
| `GOOGLEMEET_GET_TRANSCRIPTS_BY_CONFERENCE_RECORD_ID` | 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. Transcripts may require processing time after a meeting ends; an empty result may be transient or indicate that no transcript was generated. |
| `GOOGLEMEET_LIST_CONFERENCE_RECORDS` | List Conference Records | Tool to list conference records. Use when you need to retrieve a list of past conferences, optionally filtering them by criteria like meeting code, space name, or time range. |
| `GOOGLEMEET_LIST_MEMBERS` | List Members | List configured members of a Google Meet space, including their email and meeting role. Use to discover space member resource names, not participants attending a conference. Follow nextPageToken to retrieve subsequent pages. |
| `GOOGLEMEET_LIST_PARTICIPANTS` | List Participants | Lists the participants in a conference record. By default, ordered by join time descending. Use to retrieve all participants who joined a specific Google Meet conference, with support for filtering active participants (where `latest_end_time IS NULL`). |
| `GOOGLEMEET_LIST_PARTICIPANT_SESSIONS` | List Participant Sessions | Lists a page of participant sessions for a specific participant in a Google Meet conference, including session start and end times. Sessions represent joins from devices, with repeated joins creating separate sessions; use the returned page token to retrieve further sessions. |
| `GOOGLEMEET_LIST_RECORDINGS` | List Recordings | Tool to list recording resources from a conference record. Use when you need to retrieve recordings from a specific Google Meet conference. Recordings are created when meeting recording is enabled and saved to Google Drive as MP4 files. |
| `GOOGLEMEET_LIST_SMART_NOTES` | List Smart Notes | List metadata for smart notes generated by Take Notes with Gemini in a Google Meet conference. Returns resource names, generation states, timestamps, and Google Docs destinations, not note text. Follow nextPageToken to retrieve subsequent pages. |
| `GOOGLEMEET_LIST_TRANSCRIPT_ENTRIES` | List Transcript Entries | Tool to list structured transcript entries (speaker/time/text segments) for a specific Google Meet transcript. Use when you need to access the detailed content of a transcript, including individual spoken segments with timestamps and speaker information. Note: The transcript entries returned by the API might not match the transcription in Google Docs due to interleaved speakers or post-generation modifications. |
| `GOOGLEMEET_UPDATE_MEMBER` | Update Google Meet Member | Update an existing Google Meet space member's email or meeting role. Requires meetings.space.created. Use update_mask to select fields; omitted or empty updates provided values, while '*' also clears fields not provided. |
| `GOOGLEMEET_UPDATE_SPACE` | 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. Requires an applicable meetings.space.created or meetings.space.settings OAuth scope. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Google Meet MCP server is an implementation of the Model Context Protocol that connects your AI agent to Google Meet. It provides structured and secure access so your agent can perform Google Meet operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. 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

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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](https://dashboard.composio.dev?cta_placement=toolkit-framework-docs).
- Go to Settings and copy your API key.
- This key lets your Mastra agent talk to Composio and reach Google Meet through MCP.

### 2. Install dependencies

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
```bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv
```

### 3. Set up environment variables

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
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import libraries and validate environment

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
```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,
});
```

### 5. Create a Tool Router session for Google Meet

What's happening:
- create spins up a short-lived MCP HTTP endpoint for this user
- The toolkits array contains "googlemeet" for Google Meet access
- session.mcp.url is the MCP URL that Mastra's MCPClient will connect to
```typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["googlemeet"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Google Meet MCP URL:", composioMCPUrl);
```

### 6. Configure Mastra MCP client and fetch tools

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 Google Meet toolkit
```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);
```

### 7. Create the Mastra agent

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
```typescript
const agent = new Agent({
    name: "googlemeet-mastra-agent",
    instructions: "You are an AI agent with Google Meet tools via Composio.",
    model: "openai/gpt-5",
  });
```

### 8. Set up interactive chat interface

What's happening:
- messages keeps the full conversation history in Mastra's expected format
- agent.generate runs the agent with conversation history and Google Meet 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
```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: {
        googlemeet: 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);
});
```

## Complete Code

```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: ["googlemeet"],
  });

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "googlemeet-mastra-agent",
    instructions: "You are an AI agent with Google Meet 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: { googlemeet: 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 Google Meet 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 Google Meet MCP Agent with another framework

- [Claude Code](https://composio.dev/toolkits/googlemeet/framework/claude-code)
- [Cursor](https://composio.dev/toolkits/googlemeet/framework/cursor)
- [ChatGPT](https://composio.dev/toolkits/googlemeet/framework/chatgpt)
- [Claude Cowork](https://composio.dev/toolkits/googlemeet/framework/claude-cowork)
- [Antigravity](https://composio.dev/toolkits/googlemeet/framework/antigravity)
- [OpenAI Agents SDK](https://composio.dev/toolkits/googlemeet/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/googlemeet/framework/claude-agents-sdk)
- [Grok Bot](https://composio.dev/toolkits/googlemeet/framework/grok-bot)
- [Muse](https://composio.dev/toolkits/googlemeet/framework/muse)
- [Codex](https://composio.dev/toolkits/googlemeet/framework/codex)
- [Grok Build](https://composio.dev/toolkits/googlemeet/framework/grok-build)
- [VS Code](https://composio.dev/toolkits/googlemeet/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/googlemeet/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/googlemeet/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/googlemeet/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/googlemeet/framework/atomic-agent)
- [Pi](https://composio.dev/toolkits/googlemeet/framework/pi-agent)
- [DeepSeek Harness](https://composio.dev/toolkits/googlemeet/framework/deepseek)
- [Google ADK](https://composio.dev/toolkits/googlemeet/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/googlemeet/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/googlemeet/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/googlemeet/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/googlemeet/framework/crew-ai)
- [Pydantic AI](https://composio.dev/toolkits/googlemeet/framework/pydantic-ai)
- [AutoGen](https://composio.dev/toolkits/googlemeet/framework/autogen)

## Related Toolkits

- [Gmail](https://composio.dev/toolkits/gmail) - Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable.
- [Outlook](https://composio.dev/toolkits/outlook) - Outlook is Microsoft's email and calendaring platform for unified communications and scheduling. It helps users stay organized with powerful email, contacts, and calendar management.
- [Slack](https://composio.dev/toolkits/slack) - Slack is a channel-based messaging platform for teams and organizations. It helps people collaborate in real time, share files, and connect all their tools in one place.
- [Gong](https://composio.dev/toolkits/gong) - Gong is a platform for video meetings, call recording, and team collaboration. It helps teams capture conversations, analyze calls, and turn insights into action.
- [Microsoft teams](https://composio.dev/toolkits/microsoft_teams) - Microsoft Teams is a collaboration platform that combines chat, meetings, and file sharing within Microsoft 365. It keeps distributed teams connected and productive through seamless virtual communication.
- [Slackbot](https://composio.dev/toolkits/slackbot) - Slackbot is a conversational automation tool for Slack that handles reminders, notifications, and automated responses. It boosts team productivity by streamlining onboarding, answering FAQs, and managing timely alerts—all right inside Slack.
- [2chat](https://composio.dev/toolkits/_2chat) - 2chat is an API platform for WhatsApp and multichannel text messaging. It streamlines chat automation, group management, and real-time messaging for developers.
- [Agent mail](https://composio.dev/toolkits/agent_mail) - Agent mail provides AI agents with dedicated email inboxes for sending, receiving, and managing emails. It empowers agents to communicate autonomously with people, services, and other agents—no human intervention needed.
- [Aircall](https://composio.dev/toolkits/aircall) - Aircall is a cloud-based phone and call-center platform for business communications. It centralizes calls, contacts, teams, numbers, and tags in one place.
- [Android Texter](https://composio.dev/toolkits/android_texter) - Android Texter is an API service that connects Android phones to SMS, MMS, contacts, and device data. Use it to automate mobile messaging without building your own phone-to-API bridge.
- [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place.
- [Blooio](https://composio.dev/toolkits/blooio) - Blooio is a stable v2 API platform for messaging, chats, contacts, groups, phone numbers, and account analytics. It gives teams a clean way to build reliable communication workflows without stitching together fragile custom APIs.
- [Callback24](https://composio.dev/toolkits/callback24) - Callback24 is a telephony API for managing phone calls, users, services, and routing groups. It centralizes call control and routing to automate voice workflows and operations.
- [CallOnTheGo](https://composio.dev/toolkits/callonthego) - CallOnTheGo is a telephony API for managing phone numbers, caller IDs, suppression lists, audio assets, contact lists, and Voice AI campaigns. It provides programmatic control over calling infrastructure and campaign automation for scalable voice outreach.
- [Carbon Voice MCP](https://composio.dev/toolkits/carbon_voice_mcp) - Carbon Voice MCP is a voice-first collaboration platform for messages, conversations, and workflows. Use it to centralize voice communications and streamline team collaboration.
- [CardClan](https://composio.dev/toolkits/cardclan) - CardClan is a digital card platform for creating and sending personalized team cards. Use it to celebrate moments, share card links, and manage card workflows without extra coordination.
- [Chatwork](https://composio.dev/toolkits/chatwork) - Chatwork is a team communication platform with group chats, file sharing, and task management. It helps businesses boost collaboration and streamline productivity.
- [Clickmeeting](https://composio.dev/toolkits/clickmeeting) - ClickMeeting is a cloud-based platform for running online meetings and webinars. It helps businesses and individuals host, manage, and engage virtual audiences with ease.
- [Confluence](https://composio.dev/toolkits/confluence) - Confluence is Atlassian's team collaboration and knowledge management platform. It helps your team organize, share, and update documents and project content in one secure workspace.
- [Daily](https://composio.dev/toolkits/daily) - Daily is a WebRTC video and audio API platform for building rooms, meetings, recordings, live streams, transcriptions, and telephony. It gives developers reliable real-time media infrastructure without managing complex conferencing stacks.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Google Meet MCP?

With a standalone Google Meet MCP server, the agents and LLMs can only access a fixed set of Google Meet tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Google Meet 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 Google Meet tools.

### Can I manage the permissions and scopes for Google Meet while using Tool Router?

Yes, absolutely. You can configure which Google Meet 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 Google Meet data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
