# Configure the Google Calendar MCP Server

Connect Google's official hosted Calendar MCP server to a Dtwo gateway via OAuth.

## Overview

Google operates an official hosted MCP server for Calendar at `calendarmcp.googleapis.com` (currently in Developer Preview), exposing full event and calendar create, read, update, and delete tools. Access is authorized through OAuth via a Google Cloud OAuth client you register yourself.

## Prerequisites

To configure this MCP server you need to join the Google Workspace Developer Preview program and create a Google Cloud OAuth client. See [Google Workspace MCP Servers](/docs/mcp-servers-google-workspace) for instructions.

## 1. Configure Google Calendar

1. Go to <a href="https://console.cloud.google.com" target="_blank" rel="noopener noreferrer">console.cloud.google.com</a> and use the project picker near the top of the page to create a new project (or select an existing one). Then, with that project selected, open **APIs & Services** from the left navigation, click **+ Enable APIs and services**, search for "MCP", and enable the **Calendar MCP API**.

## 2. Add the MCP server to your gateway config

Go to your gateway in the Dtwo UI and open **Configuration → Advanced**. In the `mcp_servers` section add the following entry:

```yaml
  - name: google-calendar
    description: "Google's official hosted Calendar MCP server for events and calendars."
    url: https://calendarmcp.googleapis.com/mcp/v1
    transport_type: streamablehttp
    authentication:
      type: oauth
      grant_type: authorization_code
      scopes:
        - https://www.googleapis.com/auth/calendar.calendarlist.readonly
        - https://www.googleapis.com/auth/calendar.events.freebusy
        - https://www.googleapis.com/auth/calendar.events.readonly
      client_id: "<CLIENT_ID>"
      client_secret: "<CLIENT_SECRET>"
      authorization_url: "https://accounts.google.com/o/oauth2/v2/auth"
      token_url: "https://oauth2.googleapis.com/token"
      redirect_uri: "<CALLBACK_URL>"
```

Replace the placeholder values:

- `<CLIENT_ID>` and `<CLIENT_SECRET>` — come from the OAuth client you created when configuring [Google Workspace MCP Servers](/docs/mcp-servers-google-workspace).
- `<CALLBACK_URL>` — the same OAuth callback URL you set there, found in the Overview tab for your gateway in the Dtwo UI.

## 3. Deploy and verify

Save the configuration and deploy the gateway.

Then, in your AI client, ask it to authorize Google Calendar via the gateway. This opens the Google login screen — sign in as the user whose permissions the agent should inherit, and approve the consent prompt. Once authorized, confirm the server's tools appear and run a quick call to make sure the connection works.

If the tools don't appear after you authorize, refresh the tool list in your AI client — some clients don't pick it up automatically.

---

Having trouble? Email [support@dtwo.ai](mailto:support@dtwo.ai).