# Google Meet for AI agents. Managed auth, ready-made tools.

> Create meeting spaces and read past meetings, participants, recordings and transcripts in Google Meet on behalf of each of your users.

- Page: https://www.agent200.com/tools/google-meet/
- Category: Communication
- Authentication: Managed OAuth
- Identifier in code: `google_meet`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-15

## Instructions for AI agents

Connector: Google Meet, through Agent200. In code: "google_meet".
What it does: Create meeting spaces and read past meetings, participants, recordings and transcripts in Google Meet on behalf of each of your users.
Page: https://www.agent200.com/tools/google-meet/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Google Meet's own page, through the authorization link Agent200 returns. Never ask a user for a Google Meet password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: google_meet_get_space, google_meet_list_conferences, google_meet_list_participants, google_meet_list_recordings, google_meet_get_transcript. Write tools: google_meet_create_space, google_meet_end_conference. Name "google_meet" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/tools/google-meet/framework/claude/
   https://www.agent200.com/tools/google-meet/framework/chatgpt/
   https://www.agent200.com/tools/google-meet/framework/claude-code/
   https://www.agent200.com/tools/google-meet/framework/muse/
   https://www.agent200.com/tools/google-meet/framework/grok-bot/
   https://www.agent200.com/tools/google-meet/framework/openai-dots/
   https://www.agent200.com/tools/google-meet/framework/claude-duet/
   https://www.agent200.com/tools/google-meet/framework/hermes-agent/
   https://www.agent200.com/tools/google-meet/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

## About

With the Google Meet connector, your agent works with the meetings of each user who connects their own Google account. It can create a meeting link, end a running call, and look back at past meetings: who joined, the recordings and the transcripts, using only the tools your project allows.

Google Meet is Google's video meeting service, part of Google Workspace.

## Google Meet tools

- **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.

## Limits you can set

**Turn single tools on or off.** Allow `google_meet_create_space` and the reading tools, and switch off `google_meet_end_conference` if the agent should never end a call.

**Restrict what the agent reaches.** Choose the endpoints and scopes a project may use, for example creating meetings but not reading transcripts. A call outside them is refused.

## Get started

### Step 1: Set up the SDK

Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 2: Let your user connect Google Meet

Each end user authorizes their own Google Meet account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

File `connect.js`:

```js
// Each end user authorizes their own Google Meet account, once.
const connection = await agent200
  .user("user_123")
  .connect("google_meet");

if (connection.authorizationUrl) {
  // Show this link to your user; Agent200 handles the rest.
  console.log(connection.authorizationUrl);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 3: Run with the Google Meet tools

Name the user, the model and the tools. The model decides which Google Meet tools to call, and Agent200 executes them with that user's connection.

File `run.js`:

```js
const result = await agent200
  .user("user_123")
  .run({
    model: "openai/gpt-5.6-sol",
    input: "Create a Meet link for my call with Alex",
    tools: ["google_meet"],
  });

console.log(result.output);
```

(Conceptual example of the Agent200 SDK.)

## Sign-in and permissions

**Who signs in.** Each of your users, once, with their Google account on Google's own sign-in page. You never see or store their password.

**What access is requested.** The Google Meet permissions the connection needs, such as creating meeting spaces or reading meeting data, listed on Google's consent screen. Users can remove access later in their Google Account settings.

## Example requests

- "Create a Meet link for my call with Alex"
- "Who joined yesterday's planning meeting?"
- "Summarize the transcript of this morning's standup"

## Guides: Google Meet with your AI framework

- [Google Meet + Claude](https://www.agent200.com/tools/google-meet/framework/claude.md): Connect Google Meet to Claude through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Google Meet + ChatGPT](https://www.agent200.com/tools/google-meet/framework/chatgpt.md): ChatGPT cannot send an API key to a custom MCP server, so this guide builds Google Meet into your own agent with OpenAI's models and the Agent200 SDK.
- [Google Meet + Claude Code](https://www.agent200.com/tools/google-meet/framework/claude-code.md): Have Claude Code build a Google Meet agent with the Agent200 SDK: managed OAuth, ready-made tools and one API key.
- [Google Meet + Muse](https://www.agent200.com/tools/google-meet/framework/muse.md): Connect Google Meet to Muse through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Google Meet + Grok Bot](https://www.agent200.com/tools/google-meet/framework/grok-bot.md): Connect Google Meet to Grok Bot through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Google Meet + OpenAI Dots](https://www.agent200.com/tools/google-meet/framework/openai-dots.md): Dots cannot send an API key to a custom MCP server, so this guide builds an always-on Google Meet agent with OpenAI's models and the Agent200 SDK.
- [Google Meet + Claude Duet](https://www.agent200.com/tools/google-meet/framework/claude-duet.md): Connect Google Meet to Claude Duet through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Google Meet + Hermes Agent](https://www.agent200.com/tools/google-meet/framework/hermes-agent.md): Connect Google Meet to Hermes Agent through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Google Meet + OpenClaw](https://www.agent200.com/tools/google-meet/framework/openclaw.md): Connect Google Meet to OpenClaw through Agent200's MCP server: managed OAuth, ready-made tools and one API key.

## FAQ

### Who handles the Google Meet OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Google Meet.

### Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Google Meet connection, never another user's. It cannot reach anything the user or Google Meet has not authorized.

### Can I limit what my agent can do in Google Meet?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

## Related connectors

- [Slack](https://www.agent200.com/tools/slack.md): Search conversations and post messages in the workspaces your users connect.
- [Microsoft Teams](https://www.agent200.com/tools/microsoft-teams.md): Read channels and chats, post messages and set up meetings in Microsoft Teams on behalf of each of your users.
- [Discord](https://www.agent200.com/tools/discord.md): Read channels, post messages and start threads in the Discord servers your users connect.
- [Zoom](https://www.agent200.com/tools/zoom.md): Schedule, update and review Zoom meetings and their cloud recordings on behalf of each of your users.

---

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