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

> Read, search, draft and send email from each user's own Gmail account.

- Page: https://www.agent200.com/tools/gmail/
- Category: Email and calendar
- Authentication: Managed OAuth
- Identifier in code: `gmail`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-15

## Instructions for AI agents

Connector: Gmail, through Agent200. In code: "gmail".
What it does: Read, search, draft and send email from each user's own Gmail account.
Page: https://www.agent200.com/tools/gmail/

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 Gmail's own page, through the authorization link Agent200 returns. Never ask a user for a Gmail 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: gmail_search, gmail_get_message, gmail_get_thread, gmail_list_labels. Write tools: gmail_send, gmail_create_draft, gmail_modify_labels. Name "gmail" 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/gmail/framework/claude/
   https://www.agent200.com/tools/gmail/framework/chatgpt/
   https://www.agent200.com/tools/gmail/framework/claude-code/
   https://www.agent200.com/tools/gmail/framework/muse/
   https://www.agent200.com/tools/gmail/framework/grok-bot/
   https://www.agent200.com/tools/gmail/framework/openai-dots/
   https://www.agent200.com/tools/gmail/framework/claude-duet/
   https://www.agent200.com/tools/gmail/framework/hermes-agent/
   https://www.agent200.com/tools/gmail/framework/openclaw/

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

## Gmail tools

- **Search email** (`gmail_search`, read): Find messages with Gmail's search syntax.
- **Get a message** (`gmail_get_message`, read): Read a message with its headers and body.
- **Get a thread** (`gmail_get_thread`, read): Read every message in a conversation.
- **Send email** (`gmail_send`, write): Send a new message or a reply.
- **Create a draft** (`gmail_create_draft`, write): Save a message as a draft for the user to review.
- **Add a label** (`gmail_modify_labels`, write): Add or remove labels on a message.
- **List labels** (`gmail_list_labels`, read): List the user's labels.

## 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 Gmail

Each end user authorizes their own Gmail 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 Gmail account, once.
const connection = await agent200
  .user("user_123")
  .connect("gmail");

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 Gmail tools

Name the user, the model and the tools. The model decides which Gmail 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: "What did the finance team send me this week?",
    tools: ["gmail"],
  });

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

(Conceptual example of the Agent200 SDK.)

## Example requests

- "What did the finance team send me this week?"
- "Draft a reply to the latest message from Dana"
- "Label every invoice from last month"

## Guides: Gmail with your AI framework

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

## FAQ

### Who handles the Gmail 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 Gmail.

### 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 Gmail connection, never another user's. It cannot reach anything the user or Gmail has not authorized.

### Can I limit what my agent can do in Gmail?

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

## Related connectors

- [Outlook](https://www.agent200.com/tools/outlook.md): Work with mail and calendar in each user's Microsoft Outlook account.
- [Google Calendar](https://www.agent200.com/tools/google-calendar.md): Check availability and create, update or cancel events in your users' calendars.
- [Calendly](https://www.agent200.com/tools/calendly.md): Find open times, share booking links, and book, review or cancel meetings in Calendly on behalf of each of your users.
- [iCloud](https://www.agent200.com/tools/icloud.md): Search and send iCloud Mail, read and add calendar events, and look up contacts on behalf of each of your users.

---

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