How to integrate Google Meet MCP with Grok Build

Connect Grok Build to Google Meet MCP. Schedule a new video meeting for tomorrow, list all meetings i hosted last week, and more from your terminal, 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.

15 Tools

How to integrate Google Meet MCP with Grok Build

Grok Build is xAI's terminal coding agent. It runs on Grok 4.5, plans its work before it acts, and can run multiple sub-agents in parallel. It also reads Claude Code's MCP configuration, so any server you already have in a .mcp.json is picked up with no changes.

In this guide, I will show you how to connect your Google Meet account to Grok Build through Composio, so it can schedule a new video meeting for tomorrow, list all meetings I hosted last week, get transcript from your most recent meeting, and more without leaving the terminal. Composio holds the OAuth tokens for you, and Grok Build only calls the tools you approve.

Also integrate Google Meet with

Why use Composio over a standalone MCP server?

  • Read and write access. Composio's Google Meet integration lets Grok Build take real actions like creating drafts, sending updates, and labeling records, not just reading data.
  • 1,000+ SaaS toolkits out of the box. One endpoint gives you a full catalog of pre-built connectors, from Gmail and Slack to Notion, Linear, and Salesforce.
  • One MCP server for every app. Wire up a single Composio server instead of maintaining a separate MCP entry for each app.
  • Smart, context-aware tool loading. Grok Build caps how many tools it holds in a single request. Composio loads only the tools a task needs, so you do not spend that budget on tools you are not using.
  • Cross-app automation. Chain actions across apps in one run. Pull a thread, summarize it in Notion, and post the highlights to Slack from a single prompt.

Prerequisites

  • Grok Build installed and signed in. Install with curl -fsSL https://x.ai/cli/install.sh | bash on macOS or Linux, or irm https://x.ai/cli/install.ps1 | iex on Windows PowerShell. On first launch Grok opens a browser to authenticate; for headless or CI use, set an XAI_API_KEY environment variable instead (create the key at console.x.ai).
  • Access to the Google Meet account you want to connect.
  • The Composio MCP endpoint. Composio's server is remote and hosted, so there is nothing to run locally and no tunnel to set up.

Step-by-step: Connect Google Meet to Grok Build

1. Install and verify Grok Build

Install the CLI, then restart your shell so the grok binary lands on your PATH:

bash
curl -fsSL https://x.ai/cli/install.sh | bash
which grok

On Windows, install with PowerShell instead: irm https://x.ai/cli/install.ps1 | iex. If which grok returns a path, you are set. Grok Build runs on Grok 4.5 by default; you can switch models inside the session with /model <name>.

2. Add the Composio server

Add Composio as a remote HTTP MCP server with the grok mcp add command:

bash
grok mcp add --transport http composio https://connect.composio.dev/mcp

You can also add and manage servers from inside a session. Run /mcps to open the extensions modal on the MCP tab, then add a new server and paste the Composio URL. Added this way, Grok auto-detects the name from the URL and lists the server as connect:

bash
https://connect.composio.dev/mcp
Grok Build /mcps extensions modal listing MCP servers Grok Build adding the Composio MCP server with its URL

Grok also reads Claude Code-style config, so an entry in ~/.grok/config.toml or a project .mcp.json works the same way.

3. Authenticate

Composio uses OAuth. In the /mcps modal, select the Composio server and press i to authenticate (Grok also triggers this browser flow automatically the first time it uses a Composio tool). Click Allow to authorize access. Grok stores the tokens under ~/.grok/mcp_credentials.json, and /mcps shows Composio as connected.

Grok Build prompting to authenticate the Composio MCP server Composio authorization screen with the Allow button for Grok Build

4. Start building

Ask Grok to work with your Google Meet account through Composio. On the first Google Meet action, Composio prompts you to connect the account through OAuth. Approve the scopes once, and Composio handles token refresh from there.

What you can do after connecting Google Meet

  • Schedule a new video meeting for tomorrow
  • List all meetings I hosted last week
  • Get transcript from your most recent meeting
  • Update access settings for a specific Meet

Security + privacy notes (important)

  • Use least-privilege access. Grant only the Google Meet scopes you actually need.
  • Review OAuth scopes before approving. Check that the requested scopes match what you expect Composio and Grok Build to do.
  • Keep write actions human-reviewed. Grok Build proposes a plan before it acts. Leave that approval step on for actions like sending messages or editing records.
  • Keep secrets out of version control. Your XAI_API_KEY and any tokens should never be committed. Use environment variables or a secrets manager.
TOOLS

Supported Tools

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

Create Google Meet Space

Creates a new Google Meet space with optional configuration.

End active conference

Ends an active conference in a Google Meet space.

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 Participant Details

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

Get recordings by conference record ID

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

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

Retrieves all transcripts for a specific Google Meet conference using its conference_record_id.

List Conference Records

Tool to list conference records.

List Participants

Lists the participants in a conference record.

List Participant Sessions

Lists all participant sessions for a specific participant in a Google Meet conference.

List Recordings

Tool to list recording resources from a conference record.

List Transcript Entries

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

Update Google Meet Space

Updates the settings of an existing Google Meet space.

FAQ

Frequently asked questions

A standalone Google Meet MCP server gives Grok Build a fixed set of Google Meet tools tied to that one server. The Composio Tool Router lets Grok Build load tools from Google Meet and many other apps on demand, based on the task, all through a single endpoint.

Yes. Grok Build ships with native MCP support. Add a server with the grok mcp add command, from the in-session /mcps modal, or by editing ~/.grok/config.toml. It also reads Claude Code-style .mcp.json files, so Grok Build discovers the tools automatically.

Yes. Grok Build has zero-migration compatibility with Claude Code's configuration, so the same Composio server entry works in both without edits.

Tokens, keys, and configuration are encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant, so your Google Meet data and credentials are handled to that standard.

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