# Connect Google Calendar to your AI agent

> Yes — ClawLink is a hosted Google Calendar MCP server. 44 tools your agent can call from chat, with one-click hosted OAuth and nothing to run locally.

Web version: https://claw-link.dev/hub/google-calendar

ClawLink hosts a managed Google Calendar MCP server that exposes 44 tools to your AI agent. You connect Google Calendar in one click, and your agent can read, create, and update Google Calendar data from chat without you building or running a local MCP server.

## Quick facts

- 44 tools callable from chat
- One-click hosted OAuth
- Works with OpenClaw, Hermes, Claude Code, Cursor, Codex, and any MCP client
- No local server or config files

## Overview

The usual path is: build auth, handle token refresh, wire up the tools. With ClawLink you connect Google Calendar once and start using the real actions from the agent.

## Setup

Google Calendar uses OAuth. You connect it in the browser: click Connect, sign in, approve. ClawLink stores the token and refreshes it on its own. You never touch a key or wire up a redirect URL.

Authentication: hosted OAuth

## What you can do

- **Read and write from chat** — Query, create, and update Google Calendar items the moment a question comes up. No export step.
- **Go from insight to action** — The agent reads Google Calendar, sums up what matters, and helps you decide the next step.
- **Keep analysis close to the work** — Turning Google Calendar data into a follow-up task happens inside one flow.

## Google Calendar tools

44 Google Calendar tools, ready the moment you connect.

- `googlecalendar_create_event` — Create a Google Calendar event
- `googlecalendar_duplicate_calendar` — Duplicate a Google Calendar
- `googlecalendar_events_get` — Get a Google Calendar event by event id
- `googlecalendar_events_instances` — List instances of a recurring Google Calendar event
- `googlecalendar_events_list` — List events from a Google Calendar
- `googlecalendar_events_move` — Move a Google Calendar event to another calendar
- `googlecalendar_find_event` — Find a Google Calendar event
- `googlecalendar_find_free_slots` — Find free time slots across calendars
- `googlecalendar_get_calendar` — Get Google Calendar metadata by calendar id
- `googlecalendar_get_current_date_time` — Get current date and time with timezone context
- `googlecalendar_list_calendar_resources` — List calendar resources (rooms/equipment)
- `googlecalendar_list_calendars` — List Google Calendars available to the connected account
- `googlecalendar_patch_event` — Patch a Google Calendar event
- `googlecalendar_quick_add` — Create a Google Calendar event from a natural language description
- `googlecalendar_update_event` — Update a Google Calendar event
- `googlecalendar_acl_get` — Retrieves a specific access control rule for a calendar
- `googlecalendar_acl_list` — Retrieves the list of access control rules (ACLs) for a specified calendar, providing the
- `googlecalendar_calendar_list_get` — Retrieves metadata for a SINGLE specific calendar from the user's calendar list by its calendar
- `googlecalendar_colors_get` — Returns the color definitions for calendars and events
- `googlecalendar_events_list_all_calendars` — Return a unified event list across all calendars in the user's calendar list for a given time
- `googlecalendar_list_buildings` — Lists all buildings for a Google Workspace customer account with full details including
- `googlecalendar_settings_get` — Return a single user setting for the authenticated user
- `googlecalendar_settings_list` — Returns all user settings for the authenticated user
- `googlecalendar_acl_insert` — Creates an access control rule for a calendar
- `googlecalendar_acl_patch` — Updates an existing access control rule for a calendar using patch semantics (partial update)
- `googlecalendar_acl_update` — Updates an access control rule for the specified calendar
- `googlecalendar_acl_watch` — Watch for changes to ACL resources
- `googlecalendar_calendar_list_insert` — Inserts an existing calendar into the user's calendar list, making it visible in the UI
- `googlecalendar_calendar_list_patch` — Updates an existing calendar on the user's calendar list using patch semantics
- `googlecalendar_calendar_list_update` — Updates a calendar list entry's display/subscription settings (color, visibility, reminders

## Example prompts

- **Googlecalendar create event:** Use Google Calendar to googlecalendar create event and walk me through it.
- **Googlecalendar duplicate calendar:** Use Google Calendar to googlecalendar duplicate calendar and walk me through it.
- **Googlecalendar events get:** Use Google Calendar to googlecalendar events get and walk me through it.
- **Googlecalendar events instances:** Use Google Calendar to googlecalendar events instances and walk me through it.

## ClawLink vs. building it yourself

| | Manual | ClawLink |
|---|---|---|
| Connection | Build it yourself. You register a developer app with Google Calendar, set up redirect URLs, handle the consent screen, store and refresh access tokens, and redo the wiring when scopes change. | Hosted hosted OAuth. Connect once in the browser. ClawLink owns the lifecycle. |
| Maintenance | Token refresh, permission debugging, env config, every edge case. All yours. | ClawLink handles the plumbing. You focus on the workflow. |
| Time to first call | Days to weeks. Auth, storage, tool wiring, testing. Then the agent can act. | About two minutes from sign-up to the agent calling Google Calendar. |

## FAQ

### How do I connect Google Calendar to my AI agent?

Install ClawLink, open the dashboard, click Connect next to Google Calendar, and finish the hosted OAuth flow. Your agent can call Google Calendar from the next message. Two minutes, total.

### Is there a Google Calendar MCP server I can use?

Yes. ClawLink exposes Google Calendar as 44 tools your agent calls through a hosted MCP-compatible runtime. You don't run a local server or edit a config file. The tools are there the moment you connect.

### Do I need Google Calendar API credentials?

No separate API key. You sign in to Google Calendar through the normal OAuth flow and ClawLink handles the token after that.

### How much does it cost?

Your first integration is free, plus a 7-day trial of the full catalog. Paid plans unlock the rest of the library.

### Can I set this up from the terminal instead of the dashboard?

Yes. Run npx -y @useclawlink/cli login, then npx -y @useclawlink/cli connect google-calendar. The first opens a browser to sign in to ClawLink. The second opens a browser to authorize Google Calendar. No API keys to create. Works with OpenClaw, Hermes, Claude Code, Cursor, Codex, and any agent that runs shell commands.