# How to connect Google Meet to Muse

```json
{
  "title": "How to connect Google Meet to Muse",
  "toolkit": "Google Meet",
  "toolkit_slug": "googlemeet",
  "framework": "Muse",
  "framework_slug": "muse",
  "url": "https://composio.dev/toolkits/googlemeet/framework/muse",
  "markdown_url": "https://composio.dev/toolkits/googlemeet/framework/muse.md",
  "updated_at": "2026-10-04T16:43:45.641Z"
}
```

## Introduction

Muse is Meta's AI assistant. It can connect to outside tools through custom connectors, which use the Model Context Protocol (MCP).
This guide explains how to connect Google Meet to Muse using Composio Connect, which handles OAuth, token refresh, and reliability so you do not have to. You add Composio as a custom connector once, then ask Muse to work with Google Meet in plain language.

## 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)
- [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)
- [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)
- [Pydantic AI](https://composio.dev/toolkits/googlemeet/framework/pydantic-ai)
- [AutoGen](https://composio.dev/toolkits/googlemeet/framework/autogen)

## TL;DR

- Cross-app workflows across 1,500+ apps from a single plugin layer.
- On-demand tool loading so Muse only loads the tools needed for the current task.
- Programmatic tool calling through a remote workbench for complex, multi-step workflows.
- Multi-account support so users can connect and switch between multiple accounts for the same app.
- Shared account access so teams or agents can work through common business accounts and service connections.
- Managed authentication with OAuth handling, credential storage, and token refresh managed by Composio.
- Safer credential handling so app credentials stay outside the model context and tool responses.
- User-level account isolation so actions run against the correct connected account instead of mixing user access.

## Connect Google Meet to Muse

### Connecting Google Meet to Muse
You add Composio to Muse once as a custom connector, then connect Google Meet from the chat.

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

## Troubleshooting

### 1. Why doesn't Muse show a button to add my API key?

Muse shows the button only when you ask it to open the secure credentials store.
- Start a new chat.
- Send the message from step 1 exactly as written.
- If Muse asks for the key in the chat, do not paste it. Ask Muse to open the secure credentials store.

### 2. Why does the Composio connection fail after I add my API key?

The key or the connector settings are not correct.
- Copy the full key from the Composio dashboard. It starts with ck_.
- Make sure the URL is https://connect.composio.dev/mcp and the header is x-consumer-api-key.
- Remove the Composio connector in Muse settings, then do steps 1 to 3 again.

### 3. Why doesn't Muse use the Composio tools for Google Meet?

Muse may not pick the Composio connector for the request.
- Ask Muse to list its Composio tools.
- Name Composio and Google Meet in your request, for example: Use Composio to connect to Google Meet.
- If it still does not work, start a new chat and try again.

### 4. Why does Muse ask me to connect Google Meet again?

Your Google Meet connection expired or was removed.
- Open the link Muse gives you and sign in to Google Meet again.
- Check that the Google Meet connection shows as ACTIVE in the Composio dashboard.

### 5. What do I do if I pasted my API key into the chat?

Treat the key as exposed.
- Create a new API key in the Composio dashboard and delete the old one.
- Add the new key in Muse's secure credentials store, not in the chat.

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

Once connected, Muse can access the Google Meet MCP server through Composio to run the actions you authorize, using plain language in the chat.

## Complete Code

None listed.

## Conclusion

### Way Forward
Now that Google Meet is connected, extend your setup by connecting the other apps you already use every day, so Muse can run true cross-app workflows end to end.
- Connect Calendar to turn threads into scheduled meetings automatically.
- Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
- Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
- Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.
Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single connection, Muse can coordinate multiple tools safely and reliably in one conversation.

## 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)
- [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)
- [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)
- [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.
- [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.
- [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.
- [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.

## Frequently Asked Questions

### Does Muse support MCP?

Yes. Muse supports custom connectors that use the Model Context Protocol (MCP). Composio connects as one custom connector over remote streamable HTTP at https://connect.composio.dev/mcp, and gives Muse access to Google Meet and 1,500+ other apps.

### Where do I get the API key for the Composio connector?

Copy it from the Composio dashboard. It starts with ck_. Enter it only in Muse's secure credentials store, never in the chat.

### Can I connect more than one Google Meet account to Muse?

Yes. Composio supports multiple connected accounts for the same app. Give each Google Meet connection a name, such as work or personal, and tell Muse which one to use.

### How safe is my Google Meet data with Composio?

Tokens, keys, and configuration are encrypted at rest and in transit. Your Composio API key stays in Muse's secure credentials store, not in the chat or the model context. Composio is SOC 2 Type 2 compliant.

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