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

> Check availability and create, update or cancel events in your users' calendars.

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

## Instructions for AI agents

Connector: Google Calendar, through Agent200. In code: "google_calendar".
What it does: Check availability and create, update or cancel events in your users' calendars.
Page: https://www.agent200.com/tools/google-calendar/

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 Calendar's own page, through the authorization link Agent200 returns. Never ask a user for a Google Calendar 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_calendar_list_events, google_calendar_free_busy. Write tools: google_calendar_create_event. Name "google_calendar" 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-calendar/framework/claude/
   https://www.agent200.com/tools/google-calendar/framework/chatgpt/
   https://www.agent200.com/tools/google-calendar/framework/claude-code/
   https://www.agent200.com/tools/google-calendar/framework/muse/
   https://www.agent200.com/tools/google-calendar/framework/grok-bot/
   https://www.agent200.com/tools/google-calendar/framework/openai-dots/
   https://www.agent200.com/tools/google-calendar/framework/claude-duet/
   https://www.agent200.com/tools/google-calendar/framework/hermes-agent/
   https://www.agent200.com/tools/google-calendar/framework/openclaw/

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

## Google Calendar tools

- **List events** (`google_calendar_list_events`, read): Read events in a time range.
- **Find free time** (`google_calendar_free_busy`, read): Find when people are available.
- **Create an event** (`google_calendar_create_event`, write): Schedule an event and invite people.

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

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

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

Name the user, the model and the tools. The model decides which Google Calendar 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: "When am I free on Thursday afternoon?",
    tools: ["google_calendar"],
  });

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

(Conceptual example of the Agent200 SDK.)

## Example requests

- "When am I free on Thursday afternoon?"
- "Book 30 minutes with Sam next week"

## Guides: Google Calendar with your AI framework

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

## FAQ

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

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

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

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

## Related connectors

- [Gmail](https://www.agent200.com/tools/gmail.md): Read, search, draft and send email from each user's own Gmail account.
- [Outlook](https://www.agent200.com/tools/outlook.md): Work with mail and calendar in each user's Microsoft Outlook account.
- [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/
