# How to connect Google Calendar to Grok Bot (no API keys) > Connect Google Calendar to Grok Bot with ClawLink in one click — 44 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/grokbot/google-calendar Grok Bot runs on its own cloud computer, so most Google Calendar guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Google Calendar setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Google Calendar actions from chat with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Grok Bot to set up ClawLink:** > Set up ClawLink for me and tell me when it's ready. > 1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait: `npx -y @useclawlink/cli login` > 2. I'll approve it in my browser, then reply "approved". > 3. When I say approved, connect the app: `npx -y @useclawlink/cli connect google-calendar` > 4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Grok Bot to Google Calendar. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect Google Calendar** — `npx -y @useclawlink/cli connect google-calendar`, then approve in the browser. 3. **Use it from chat** — ask Grok Bot in plain English. **The same CLI works from any agent with shell access:** ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect google-calendar # connect Google Calendar (browser OAuth) npx -y @useclawlink/cli actions google-calendar # list available actions npx -y @useclawlink/cli run google-calendar --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval: ```bash npx -y @useclawlink/cli login # prints an approval link, approve it in your browser npx -y @useclawlink/cli connect google-calendar ``` Pair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI. Verify the connection by asking Grok Bot: > Use Google Calendar to googlecalendar create event and walk me through the result in plain English. ### Using a different agent? The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Google Calendar is connected in the dashboard, that agent calls the same 44 Google Calendar tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Google Calendar MCP for Grok Bot Looking for a Google Calendar MCP server for Grok Bot? ClawLink connects Google Calendar to Grok Bot and exposes 44 Google Calendar tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using a different agent? The [OpenClaw Google Calendar integration](https://claw-link.dev/openclaw/google-calendar) and the [Hermes Google Calendar integration](https://claw-link.dev/hermes/google-calendar) connect the same ClawLink account the same way. ## What the Grok Bot Google Calendar integration can do 44 Google Calendar tools are ready for Grok Bot once the account is connected. The 30 below are the ones people reach for most; your agent can call all 44. ### 30 of 44 Google Calendar tools for Grok Bot | Tool | What it does | |---|---| | **Create event** `googlecalendar_create_event` | Create a Google Calendar event | | **Duplicate calendar** `googlecalendar_duplicate_calendar` | Duplicate a Google Calendar | | **Events get** `googlecalendar_events_get` | Get a Google Calendar event by event id | | **Events instances** `googlecalendar_events_instances` | List instances of a recurring Google Calendar event | | **Events list** `googlecalendar_events_list` | List events from a Google Calendar | | **Events move** `googlecalendar_events_move` | Move a Google Calendar event to another calendar | | **Find event** `googlecalendar_find_event` | Find a Google Calendar event | | **Find free slots** `googlecalendar_find_free_slots` | Find free time slots across calendars | | **Get calendar** `googlecalendar_get_calendar` | Get Google Calendar metadata by calendar id | | **Get current date time** `googlecalendar_get_current_date_time` | Get current date and time with timezone context | | **List calendar resources** `googlecalendar_list_calendar_resources` | List calendar resources (rooms/equipment) | | **List calendars** `googlecalendar_list_calendars` | List Google Calendars available to the connected account | | **Patch event** `googlecalendar_patch_event` | Patch a Google Calendar event | | **Quick add** `googlecalendar_quick_add` | Create a Google Calendar event from a natural language description | | **Update event** `googlecalendar_update_event` | Update a Google Calendar event | | **Acl get** `googlecalendar_acl_get` | Retrieves a specific access control rule for a calendar | | **Acl list** `googlecalendar_acl_list` | Retrieves the list of access control rules (ACLs) for a specified calendar, providing the | | **Calendar list get** `googlecalendar_calendar_list_get` | Retrieves metadata for a SINGLE specific calendar from the user's calendar list by its calendar | | **Colors get** `googlecalendar_colors_get` | Returns the color definitions for calendars and events | | **Events list all calendars** `googlecalendar_events_list_all_calendars` | Return a unified event list across all calendars in the user's calendar list for a given time | | **List buildings** `googlecalendar_list_buildings` | Lists all buildings for a Google Workspace customer account with full details including | | **Settings get** `googlecalendar_settings_get` | Return a single user setting for the authenticated user | | **Settings list** `googlecalendar_settings_list` | Returns all user settings for the authenticated user | | **Acl insert** `googlecalendar_acl_insert` | Creates an access control rule for a calendar | | **Acl patch** `googlecalendar_acl_patch` | Updates an existing access control rule for a calendar using patch semantics (partial update) | | **Acl update** `googlecalendar_acl_update` | Updates an access control rule for the specified calendar | | **Acl watch** `googlecalendar_acl_watch` | Watch for changes to ACL resources | | **Calendar list insert** `googlecalendar_calendar_list_insert` | Inserts an existing calendar into the user's calendar list, making it visible in the UI | | **Calendar list patch** `googlecalendar_calendar_list_patch` | Updates an existing calendar on the user's calendar list using patch semantics | | **Calendar list update** `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 the result in plain English. **Googlecalendar Duplicate Calendar** > Use Google Calendar to googlecalendar duplicate calendar and walk me through the result in plain English. **Googlecalendar Events Get** > Use Google Calendar to googlecalendar events get and walk me through the result in plain English. **Googlecalendar Events Instances** > Use Google Calendar to googlecalendar events instances and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Google Calendar working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Google Calendar app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Google Calendar through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Google Calendar. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Google Calendar actions to the runtime in a format your agent can reliably use. | 44 tools for Google Calendar are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Google Calendar to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Grok Bot users instead. You install the plugin once, connect Google Calendar in the browser, and the 44 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ### Connection succeeds but no tools appear Reconnect Google Calendar from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Google Calendar tools Google Calendar tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Google Calendar call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Google Calendar returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### OAuth finished in the browser but the account is still missing Try reconnecting Google Calendar and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a Grok Bot Google Calendar integration? Yes. ClawLink is the fastest way to connect Grok Bot to Google Calendar: link your Google Calendar account once in the browser and Grok Bot can call the Google Calendar API through 44 ready-made tools — no custom code or token handling. ### How do I connect Google Calendar to Grok Bot with ClawLink? Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal and approve the link it prints, then `npx -y @useclawlink/cli connect google-calendar` to authorize Google Calendar. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files or API keys to manage. ### How long does it take to connect Google Calendar to Grok Bot? About two minutes. Sign in, click Connect next to Google Calendar in the dashboard, authenticate, and Grok Bot can use it from the next chat message. ### Why use ClawLink instead of wiring Google Calendar up myself? The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Google Calendar working from chat. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ## Related - [Grok Bot Google Super integration](https://claw-link.dev/grokbot/google-super) — Unified access to multiple Google services in one integration - [Connect Google Drive](https://claw-link.dev/grokbot/google-drive) — Upload, search, and manage files - [Google Analytics](https://claw-link.dev/grokbot/google-analytics) — Connect Google Analytics properties through hosted Google OAuth