# How to integrate Google Meet MCP with Google ADK

```json
{
  "title": "How to integrate Google Meet MCP with Google ADK",
  "toolkit": "Google Meet",
  "toolkit_slug": "googlemeet",
  "framework": "Google ADK",
  "framework_slug": "google-adk",
  "url": "https://composio.dev/toolkits/googlemeet/framework/google-adk",
  "markdown_url": "https://composio.dev/toolkits/googlemeet/framework/google-adk.md",
  "updated_at": "2026-05-12T10:13:58.785Z"
}
```

## Introduction

This guide walks you through connecting Google Meet to Google ADK using the Composio tool router. By the end, you'll have a working Google Meet agent that can schedule a new video meeting for tomorrow, list all meetings i hosted last week, get transcript from your most recent meeting through natural language commands.
This guide will help you understand how to give your Google ADK 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.

## Also integrate Google Meet with

- [ChatGPT](https://composio.dev/toolkits/googlemeet/framework/chatgpt)
- [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)
- [Claude Code](https://composio.dev/toolkits/googlemeet/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/googlemeet/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/googlemeet/framework/codex)
- [Cursor](https://composio.dev/toolkits/googlemeet/framework/cursor)
- [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)
- [CLI](https://composio.dev/toolkits/googlemeet/framework/cli)
- [LangChain](https://composio.dev/toolkits/googlemeet/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/googlemeet/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/googlemeet/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/googlemeet/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/googlemeet/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Get a Google Meet account set up and connected to Composio
- Install the Google ADK and Composio packages
- Create a Composio Tool Router session for Google Meet
- Build an agent that connects to Google Meet through MCP
- Interact with Google Meet using natural language

## What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.
Key features include:
- Gemini Integration: Native support for Google's Gemini models
- MCP Toolset: Built-in support for Model Context Protocol tools
- Streamable HTTP: Connect to external services through streamable HTTP
- CLI and Web UI: Run agents via command line or web interface

## 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 meetings and recordings, so your agent can schedule new meetings, fetch past conference details, access recordings and transcripts, and manage meeting spaces on your behalf.
- Instant meeting scheduling and management: Ask your agent to create new Google Meet sessions or update existing meeting spaces with specific settings and access controls.
- Comprehensive meeting record retrieval: Have your agent list all past conference records, filter them by time or criteria, and pull up detailed information about any meeting.
- Access recordings and transcripts: Effortlessly retrieve recordings or full transcripts of your previous Google Meet conferences for reference, review, or sharing.
- Participant session insights: Let your agent list all participants in a given meeting or fetch detailed information about specific attendee sessions for attendance tracking or follow-up.
- Flexible post-meeting actions: Enable your agent to update meeting spaces, manage access, and ensure your Google Meet environment stays organized and up to date.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `GOOGLEMEET_CREATE_MEET` | Create Google Meet Space | Creates a new Google Meet space with optional configuration. Does not attach to any calendar event — calendar linking requires a separate Calendar tool call. Capture `meetingUri`, `meetingCode`, and `space.name` from the response immediately for downstream lookups. Requires `meetings.space.created` OAuth scope. Returns HTTP 429 under rapid calls; apply exponential backoff. Use when you need a meeting space with specific access controls, moderation, recording, or transcription settings. |
| `GOOGLEMEET_END_ACTIVE_CONFERENCE` | End active conference | Ends an active conference in a Google Meet space. REQUIRES 'space_name' parameter (e.g., 'spaces/jQCFfuBOdN5z' or just 'jQCFfuBOdN5z'). Use when you need to terminate an ongoing conference in a specified space. This operation only succeeds if a conference is actively running in the space. You must always provide the space_name to identify which space's conference to end. Immediately drops all active participants — 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_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_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_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 | Retrieves all transcripts for a specific Google Meet conference using its conference_record_id. Transcripts require processing time after a meeting ends — empty results may be transient; retry after a delay before concluding no transcripts exist. Returns results only if transcription was enabled during the meeting and permitted by the organizer's domain policies; an empty list may also indicate transcription was never 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_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 all participant sessions for a specific participant in a Google Meet conference. 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. Returns session details including start time and end time for each session. |
| `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_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_SPACE` | Update Google Meet Space | Updates the settings of an existing Google Meet space. Requires organizer/host privileges and the meetings.space.created OAuth scope. REQUIRED PARAMETER: - name: The space identifier (e.g., 'spaces/jQCFfuBOdN5z'). This is always required to identify which space to update. OPTIONAL PARAMETERS: - config: The new configuration settings to apply (accessType, entryPointAccess, moderation, etc.) - updateMask: Specify which fields to update. If omitted, all provided config fields are updated. Example: To change access type, provide name='spaces/abc123' and config={'accessType': 'OPEN'} |

## 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:
- A Google API key for Gemini models
- A Composio account and API key
- Python 3.9 or later installed
- Basic familiarity with Python

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

Google API Key
- Go to [Google AI Studio](https://aistudio.google.com/app/apikey) and create an API key.
- Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
- Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.

### 2. Install dependencies

Inside your virtual environment, install the required packages.
What's happening:
- google-adk is Google's Agents Development Kit
- composio connects your agent to Google Meet via MCP
- python-dotenv loads environment variables
```bash
pip install google-adk composio python-dotenv
```

### 3. Set up ADK project

Set up a new Google ADK project.
What's happening:
- This creates an agent folder with a root agent file and .env file
```bash
adk create my_agent
```

### 4. Set environment variables

Save all your credentials in the .env file.
What's happening:
- GOOGLE_API_KEY authenticates with Google's Gemini models
- COMPOSIO_API_KEY authenticates with Composio
- COMPOSIO_USER_ID identifies the user for session management
```bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email
```

### 5. Import modules and validate environment

What's happening:
- os reads environment variables
- Composio is the main Composio SDK client
- GoogleProvider declares that you are using Google ADK as the agent runtime
- Agent is the Google ADK LLM agent class
- McpToolset lets the ADK agent call MCP tools over HTTP
```python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")
```

### 6. Create Composio client and Tool Router session

What's happening:
- Authenticates to Composio with your API key
- Declares Google ADK as the provider
- Spins up a short-lived MCP endpoint for your user and selected toolkit
- Stores the MCP HTTP URL for the ADK MCP integration
```python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["googlemeet"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
```

### 7. Set up the McpToolset and create the Agent

What's happening:
- Connects the ADK agent to the Composio MCP endpoint through McpToolset
- Uses Gemini as the model powering the agent
- Lists exact tool names in instruction to reduce misnamed tool calls
```python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Google Meet operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
```

### 8. Run the agent

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.
What's happening:
- adk run runs the agent in CLI mode
- adk web . opens a web UI for interactive testing
```bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web
```

## Complete Code

```python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["googlemeet"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Google Meet operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
```

## Conclusion

You've successfully integrated Google Meet with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Google Meet using natural language commands.
Key takeaways:
- The Tool Router approach dynamically routes requests to the appropriate Google Meet tools
- Environment variables keep your credentials secure and separate from code
- Clear agent instructions reduce tool calling errors
- The ADK web UI provides an interactive interface for testing and development
You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

## How to build Google Meet MCP Agent with another framework

- [ChatGPT](https://composio.dev/toolkits/googlemeet/framework/chatgpt)
- [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)
- [Claude Code](https://composio.dev/toolkits/googlemeet/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/googlemeet/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/googlemeet/framework/codex)
- [Cursor](https://composio.dev/toolkits/googlemeet/framework/cursor)
- [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)
- [CLI](https://composio.dev/toolkits/googlemeet/framework/cli)
- [LangChain](https://composio.dev/toolkits/googlemeet/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/googlemeet/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/googlemeet/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/googlemeet/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/googlemeet/framework/crew-ai)

## 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.
- [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.
- [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.
- [Dailybot](https://composio.dev/toolkits/dailybot) - DailyBot streamlines team collaboration with chat-based standups, reminders, and polls. It keeps work flowing smoothly in your favorite messaging platforms.
- [Dialmycalls](https://composio.dev/toolkits/dialmycalls) - Dialmycalls is a mass notification service for sending voice and text messages to contacts. It helps teams and organizations quickly broadcast urgent alerts and updates.
- [Dialpad](https://composio.dev/toolkits/dialpad) - Dialpad is a cloud-based business phone and contact center system for teams. It unifies voice, video, messaging, and meetings across your devices.
- [Discord](https://composio.dev/toolkits/discord) - Discord is a real-time messaging and VoIP platform for communities and teams. It lets users chat, share media, and collaborate across public and private channels.
- [Discordbot](https://composio.dev/toolkits/discordbot) - Discordbot is an automation tool for Discord servers that handles moderation, messaging, and user engagement. It helps communities run smoothly by automating routine and complex tasks.
- [Echtpost](https://composio.dev/toolkits/echtpost) - Echtpost is a secure digital communication platform for encrypted document and message exchange. It ensures confidential data stays private and protected during transmission.
- [Egnyte](https://composio.dev/toolkits/egnyte) - Egnyte is a cloud-based platform for secure file sharing, storage, and governance. It helps teams collaborate efficiently while maintaining data compliance and security.
- [Heartbeat](https://composio.dev/toolkits/heartbeat) - Heartbeat is a plug-and-play platform for building and managing online communities. It helps you organize users, channels, events, and discussions in one place.

## 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 Google ADK?

Yes, you can. Google ADK 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)