# How to connect Google Meet to Grok Bot

> Connect Google Meet to Grok Bot through Agent200's MCP server: managed OAuth, ready-made tools and one API key.

- Page: https://www.agent200.com/tools/google-meet/framework/grok-bot/
- Connector: [Google Meet](https://www.agent200.com/tools/google-meet.md)
- Framework: Grok Bot
- Updated: 2026-11-15

## Instructions for AI agents

Goal: connect Google Meet to Grok Bot with Agent200, through its MCP server.
Guide: https://www.agent200.com/tools/google-meet/framework/grok-bot/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Grok Bot's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure Google Meet is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Grok Bot: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Grok Bot's exact menus or commands.
4. The first Google Meet request returns an authorization link if the user has not connected Google Meet yet: show it to them and continue once they have approved access on Google Meet's own page.
5. Check it works with this request: "Create a Meet link for my call with Alex"
   What should come back:
   - An answer built from your own Google Meet data.
   - Behind the scenes, Grok Bot calls an Agent200 tool for Google Meet, such as `google_meet_get_space`.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Google Meet, then retry.

## Overview

This guide connects Google Meet to Grok Bot through Agent200's MCP server. When you finish, Grok Bot can search, read and act in Google Meet with the tools Agent200 provides, whenever a request needs them.

You add one MCP server to Grok Bot with your Agent200 API key. Your Google Meet account is connected through managed OAuth: you approve access once on Google Meet's own page, and Agent200 keeps the connection working.

- **Connector:** [Google Meet](https://www.agent200.com/tools/google-meet/)
- **Works with:** Grok Bot · Agent app, through MCP
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [7 tools](https://www.agent200.com/tools/google-meet/framework/grok-bot/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **Google Meet enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **An end user with a Google Meet account.** They approve access once, on Google Meet's own page.
- **Grok Bot, with custom MCP servers allowed.** Grok Bot comes with SuperGrok, Grok Business seats and paid Cursor plans. On a team, the admin's connector policy must allow the Agent200 server.

## Connect Google Meet to Grok Bot

### Step 1: Create your Agent200 API key

Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Grok Bot in the next step, as "Authorization: Bearer <your key>". One key covers Google Meet and every other connector enabled for your project. Keep it out of chats and source control.

Create an API key: https://agent200.com/platform/apikeys/

### Step 2: Open the custom connector form

In Grok Bot, open **Connect apps** from the sidebar and choose **Add a custom connector** at the bottom.

### Step 3: Fill in the server and your key

Enter the name Agent200, pick Type **Remote HTTPS**, enter the server URL and add one HTTP header: `Authorization` with the value `Bearer` followed by your key. Leave Client ID empty, then choose **Add plugin**.

File `Add a custom connector`:

```text
Name:          Agent200
Type:          Remote HTTPS
Server URL:    https://api.agent200.com/mcp/
HTTP headers:  Authorization: Bearer YOUR_AGENT200_API_KEY
```

### Step 4: Attach Agent200 in a chat

In a Bot chat, type `@` and attach Agent200 to the task. Custom servers are account-wide, so every Bot on the account can use it.

### Step 5: Connect your Google Meet account

The first time you ask Grok Bot for something in Google Meet, Agent200 returns an authorization link. Open it and approve access on Google Meet's own page. Agent200 stores the connection and keeps it working; your password never reaches Grok Bot or Agent200.

## Test your connection

Ask: "Create a Meet link for my call with Alex"

What should come back:

- An answer built from your own Google Meet data.
- Behind the scenes, Grok Bot calls an Agent200 tool for Google Meet, such as `google_meet_get_space`.

If Grok Bot shows an authorization link instead, you have not connected Google Meet yet: open it, approve access, then ask again.

## Google Meet tools Grok Bot can call

- **Create a meeting space** (`google_meet_create_space`, write): Create a meeting space and get its link.
- **Get a meeting space** (`google_meet_get_space`, read): Read a meeting space's link, code and settings.
- **End a meeting** (`google_meet_end_conference`, write): End the call running in a meeting space.
- **List past meetings** (`google_meet_list_conferences`, read): List past meetings with their start and end times.
- **List participants** (`google_meet_list_participants`, read): List who joined a past meeting.
- **List recordings** (`google_meet_list_recordings`, read): List a past meeting's recordings, saved in Google Drive.
- **Read a transcript** (`google_meet_get_transcript`, read): Read a past meeting's transcript, entry by entry.

## How it works

1. **You ask Grok Bot.** In your own words, for something in Google Meet.
2. **Grok Bot picks a tool.** It sees the Google Meet tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** With your own Google Meet connection, within the tools and scopes your project allows.
4. **Grok Bot answers.** It gets the result back from the MCP server and uses it in its reply or its next step.

**Each user's own connection.** Connections belong to individual end users. A request for one user never reaches another user's Google Meet account.

**Permissions at every level.** Your project settings decide what the agent may request, the end user decides what they authorize, and Google Meet enforces what its API grants.

## Troubleshooting

### The server cannot be saved, or shows Disabled by team admin

Your team’s connector policy blocks it. Ask the admin to allow the Agent200 server address on the Plugins & MCPs page of the Cursor dashboard.

### Calls fail on a team with a network allowlist

If the admin applies the network allowlist to MCP servers, api.agent200.com must be on it.

### The connector shows Needs auth, or tools return 401

Check the Authorization header is exactly `Bearer`, a space and a valid key, then reconnect. If the key was replaced, remove the connector and add it again.

### The Bot cannot see the Google Meet tools

Check Agent200 is enabled in your plugins, attach it with @ in the chat, and start a new chat if it was added mid-conversation.

### Grok Bot shows a Google Meet authorization link

You have not connected Google Meet yet, or the connection needs to be approved again. Open the link, approve access on Google Meet's own page, then ask Grok Bot again.

### A tool call is refused or returns less than expected

Agent200 runs only what your project allows. Check that Google Meet and the tools you need are enabled in the dashboard's Connectors settings, and that you granted Google Meet the access the task needs.

### The API key was pasted into a chat or committed

Create a new key on the [API keys page](https://agent200.com/platform/apikeys/), replace it in Grok Bot's MCP settings, and stop using the old one. Paste the key only into Grok Bot's settings, never into a chat.

## Use Google Meet with another framework

- [Google Meet + Claude](https://www.agent200.com/tools/google-meet/framework/claude.md)
- [Google Meet + ChatGPT](https://www.agent200.com/tools/google-meet/framework/chatgpt.md)
- [Google Meet + Claude Code](https://www.agent200.com/tools/google-meet/framework/claude-code.md)
- [Google Meet + Muse](https://www.agent200.com/tools/google-meet/framework/muse.md)
- [Google Meet + OpenAI Dots](https://www.agent200.com/tools/google-meet/framework/openai-dots.md)
- [Google Meet + Claude Duet](https://www.agent200.com/tools/google-meet/framework/claude-duet.md)
- [Google Meet + Hermes Agent](https://www.agent200.com/tools/google-meet/framework/hermes-agent.md)
- [Google Meet + OpenClaw](https://www.agent200.com/tools/google-meet/framework/openclaw.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
