How to integrate Google Calendar MCP with Grok Build

Connect Grok Build to Google Calendar MCP. Create a meeting with the marketing team, list all events scheduled for next week, and more from your terminal, with authentication handled for you.

Google Calendar logoGoogle Calendar
Oauth2

Google Calendar is a time management service for scheduling meetings, events, and reminders. It streamlines personal and team organization with integrated notifications and sharing options.

47 Tools6 Triggers

How to integrate Google Calendar MCP with Grok Build

Grok Build is xAI's terminal coding agent. It runs on Grok 4.5, plans its work before it acts, and can run multiple sub-agents in parallel. It also reads Claude Code's MCP configuration, so any server you already have in a .mcp.json is picked up with no changes.

In this guide, I will show you how to connect your Google Calendar account to Grok Build through Composio, so it can create a meeting with the marketing team, list all events scheduled for next week, delete tomorrow’s canceled event from your calendar, and more without leaving the terminal. Composio holds the OAuth tokens for you, and Grok Build only calls the tools you approve.

For exact tool slugs and parameter tables, see the tool catalog in the Composio docs.

Also integrate Google Calendar with

Why use Composio over a standalone MCP server?

  • Read and write access. Composio's Google Calendar integration lets Grok Build take real actions like creating drafts, sending updates, and labeling records, not just reading data.
  • 1,700+ SaaS toolkits out of the box. One endpoint gives you a full catalog of pre-built connectors, from Gmail and Slack to Notion, Linear, and Salesforce.
  • One MCP server for every app. Wire up a single Composio server instead of maintaining a separate MCP entry for each app.
  • Smart, context-aware tool loading. Grok Build caps how many tools it holds in a single request. Composio loads only the tools a task needs, so you do not spend that budget on tools you are not using.
  • Cross-app automation. Chain actions across apps in one run. Pull a thread, summarize it in Notion, and post the highlights to Slack from a single prompt.

Prerequisites

  • Grok Build installed and signed in. Install with curl -fsSL https://x.ai/cli/install.sh | bash on macOS or Linux, or irm https://x.ai/cli/install.ps1 | iex on Windows PowerShell. On first launch Grok opens a browser to authenticate; for headless or CI use, set an XAI_API_KEY environment variable instead (create the key at console.x.ai).
  • Access to the Google Calendar account you want to connect.
  • The Composio MCP endpoint. Composio's server is remote and hosted, so there is nothing to run locally and no tunnel to set up.

Step-by-step: Connect Google Calendar to Grok Build

1. Install and verify Grok Build

Install the CLI, then restart your shell so the grok binary lands on your PATH:

bash
curl -fsSL https://x.ai/cli/install.sh | bash
which grok

On Windows, install with PowerShell instead: irm https://x.ai/cli/install.ps1 | iex. If which grok returns a path, you are set. Grok Build runs on Grok 4.5 by default; you can switch models inside the session with /model <name>.

2. Add the Composio server

Add Composio as a remote HTTP MCP server with the grok mcp add command:

bash
grok mcp add --transport http composio https://connect.composio.dev/mcp

You can also add and manage servers from inside a session. Run /mcps to open the extensions modal on the MCP tab, then add a new server and paste the Composio URL. Added this way, Grok auto-detects the name from the URL and lists the server as connect:

bash
https://connect.composio.dev/mcp
Grok Build /mcps extensions modal listing MCP servers Grok Build adding the Composio MCP server with its URL

Grok also reads Claude Code-style config, so an entry in ~/.grok/config.toml or a project .mcp.json works the same way.

3. Authenticate

Composio uses OAuth. In the /mcps modal, select the Composio server and press i to authenticate (Grok also triggers this browser flow automatically the first time it uses a Composio tool). Click Allow to authorize access. Grok stores the tokens under ~/.grok/mcp_credentials.json, and /mcps shows Composio as connected.

Grok Build prompting to authenticate the Composio MCP server Composio authorization screen with the Allow button for Grok Build

4. Start building

Ask Grok to work with your Google Calendar account through Composio. On the first Google Calendar action, Composio prompts you to connect the account through OAuth. Approve the scopes once, and Composio handles token refresh from there.

What you can do after connecting Google Calendar

  • Create a meeting with the marketing team
  • List all events scheduled for next week
  • Delete tomorrow’s canceled event from your calendar
  • Update the time for Friday’s project sync

Security + privacy notes (important)

  • Use least-privilege access. Grant only the Google Calendar scopes you actually need.
  • Review OAuth scopes before approving. Check that the requested scopes match what you expect Composio and Grok Build to do.
  • Keep write actions human-reviewed. Grok Build proposes a plan before it acts. Leave that approval step on for actions like sending messages or editing records.
  • Keep secrets out of version control. Your XAI_API_KEY and any tokens should never be committed. Use environment variables or a secrets manager.
TOOLS & TRIGGERS

Supported Tools and Triggers

Every Google Calendar action and event your agent gets out of the box.

Delete ACL Rule

Deletes an access control rule from a Google Calendar.

Get ACL Rule

Retrieves a specific access control rule for a calendar.

Create ACL Rule

Creates an access control rule for a calendar.

List ACL Rules

Retrieves the list of access control rules (ACLs) for a specified calendar, providing the necessary 'rule_id' values required for updating specific ACL rules.

Patch ACL Rule

Partially updates the role or scope of an existing Google Calendar access control rule.

Update ACL Rule

Updates an access control rule for the specified calendar.

Watch ACL Changes

Tool to watch for changes to ACL resources.

Batch Events

Execute up to 1000 event mutations (create/patch/delete) in one Google Calendar HTTP batch request with per-item status/results.

Remove Calendar from List

Removes a calendar from the user's calendar list, unsubscribing from it without deleting the calendar itself.

Get Single Calendar by ID

Retrieves metadata for a SINGLE specific calendar from the user's calendar list by its calendar ID.

Insert Calendar into List

Inserts an existing calendar into the user's calendar list, with optional display settings.

Patch Calendar List Entry

Updates an existing calendar on the user's calendar list using patch semantics.

Update Calendar List Entry

Updates a calendar list entry's display/subscription settings (color, visibility, reminders, selection) for the authenticated user — does not modify the underlying calendar resource (title, timezone, etc.

Watch Calendar List

Creates a push-notification channel for changes to the user's calendar list.

Delete Calendar

Deletes a secondary calendar that you own or have delete permissions on.

Update Calendar

Full PUT-style update that overwrites all calendar metadata fields; unspecified optional fields are cleared.

Stop Channel

Tool to stop watching resources through a notification channel.

Clear Calendar

Clears a primary calendar by deleting all events from it.

Get Color Definitions

Returns the color definitions for calendars and events.

Create a new calendar

Creates a new secondary Google Calendar with the specified title and optional settings.

Create Event

Creates a timed or all-day Google Calendar event and returns it under response_data, without conflict checking.

Delete event

Deletes an event from the specified calendar.

Create a calendar

Creates a new, empty Google Calendar with the specified title (summary).

Get Event

Retrieves a SINGLE event by its unique event_id (REQUIRED).

Import Event

Tool to import an event as a private copy to a calendar.

Get Event Instances

Returns instances of the specified recurring event.

List Events

Lists or incrementally synchronizes events from one calendar, defaulting to the connected user's primary calendar.

List Events from All Calendars

Lists and deduplicates events across selected calendars or the user's calendar list for a time range.

Move Event

Moves a default event to another calendar, changing its organizer.

Watch Events

Watch for changes to Events resources.

Find event

Finds events in a specified Google Calendar using text, time ranges, and event types.

Find free slots

Queries busy intervals and calculates free gaps for specified calendars, without filtering by meeting duration; the range is limited to 89 days, and calendar errors produce empty free slots marked unreliable.

Query Calendar Availability

Queries raw busy intervals for one or more calendars or groups over an exact time range.

Get Google Calendar

Gets canonical metadata for one Google Calendar, defaulting to the authenticated user's primary calendar.

Get current date and time

Gets the current date and time, allowing for a specific timezone offset.

Get Current Google Calendar User

Identifies the Google user connected to Calendar from the primary calendar resource.

List Buildings

Lists a page of buildings for a Google Workspace customer, including available addresses, coordinates, and floor names.

List Calendar Resources

Retrieves calendar resources (such as conference rooms) from a Google Workspace domain using the Admin SDK Directory API.

List Google Calendars

Lists calendars accessible through the connected user's CalendarList, returning IDs and user-specific metadata such as access role, color, visibility, selection, and reminders.

Patch Calendar

Partially updates (PATCHes) an existing Google Calendar, modifying only the fields provided.

Patch Event

Update specified fields of an existing event in a Google Calendar using patch semantics (array fields like `attendees` are fully replaced if provided); ensure the `calendar_id` and `event_id` are valid and the user has write access to the calendar.

Quick Add Event

Parses natural language text to quickly create a basic Google Calendar event with its title, date, and time, suitable for simple scheduling; does not support direct attendee addition or recurring events, and `calendar_id` must be valid if not 'primary'.

Remove attendee from event

Removes an attendee from a specified event in a Google Calendar; the calendar and event must exist.

Get Calendar Setting

Tool to return a single user setting for the authenticated user.

List Settings

Lists the authenticated user's calendar settings, returning a page of settings identified by their id fields.

Watch Settings

Watch for changes to Settings resources.

Update Google event

Replaces an existing Google Calendar event using its event ID and required start time.

FAQ

Frequently asked questions

Start with Google Calendar.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Google Calendar tool your agent needs.Free to start.

Start building