# Google Calendar (Official)

{% hint style="warning" %}
**Early Access** — Reach out to your Natoma representative for access.
{% endhint %}

**Type:** Official

**Source Type:** Remote URL

**Source:** <https://calendarmcp.googleapis.com/mcp/v1>

**Description:** Google Calendar MCP server is Google's official remote MCP integration for Calendar. It enables creating, listing, updating, and deleting events, managing calendars, and looking up free/busy information through OAuth.

***

## Setup

### Admin Setup (one-time)

1. In the [Google Cloud Console](https://console.cloud.google.com/), select the project that should own the OAuth client.
2. Navigate to **APIs & Services > Library**, search for **Google Calendar API**, and click **Enable**.
3. Navigate to **Google Auth Platform > Branding** and configure the OAuth Consent Screen (App name, support email, audience, contact email).
4. Under **Data Access > Add or Remove Scopes**, add (one per line):

```
calendar.calendarlist.readonly
calendar.events.readonly
calendar.events.freebusy
```

5. Navigate to **Google Auth Platform > Clients > Create Client** and select **Web application**.
6. Under **Authorized redirect URIs**, click **+ Add URI** and enter:

{% hint style="warning" %}
Use exactly this redirect URI — Google will reject the OAuth flow if it doesn't match.
{% endhint %}

```
https://api.natoma.app/mcp/server/callback
```

7. Click **Create** and copy the **Client ID** and **Client Secret**.

In Natoma, an admin adds **Google Calendar** under **Apps** and enters the **Client ID** and **Client Secret**.

### Authorize Your Connection

When prompted while creating the connection in Natoma, click **Authorize**.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.natoma.ai/apps/google-calendar-v2.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.