Skip to main content

Google Workspace Calendar MCP server

Let an AI agent manage your team's calendars, schedule meetings, and find time slots across multiple calendars. This MCP server enables automated event creation, attendee management, room booking, and availability checking—perfect for reducing scheduling friction in busy organizations.

Setting up an MCP server

This article covers the standard steps for creating an MCP server in AI Gateway and connecting it to an AI client. The steps are the same for every integration — application-specific details (API credentials, OAuth endpoints, and scopes) are covered in the individual application pages.

Before you begin​

You'll need:

  • Access to AI Gateway with permission to create MCP servers
  • API credentials for the application you're connecting (see the relevant application page for what to collect)

Create an MCP server​

Find the API in the catalog​

  1. Sign in to AI Gateway and select MCP Servers from the left navigation.
  2. Select New MCP Server.
  3. Search for the application you want to connect, then select it from the catalog.

Configure the server​

  1. Enter a Name for your server — something descriptive that identifies both the application and its purpose (for example, "Zendesk Support — Prod").
  2. Enter a Description so your team knows what the server is for.
  3. Set the Timeout value. 30 seconds works for most APIs; increase to 60 seconds for APIs that return large payloads.
  4. Toggle Production mode on if this server will be used in a live workflow.
  5. Select Next.

Configure authentication​

Enter the authentication details for the application. This varies by service — see the Authentication section of the relevant application page for the specific credentials, OAuth URLs, and scopes to use.

Configure security​

  1. Set any Rate limits appropriate for your use case and the API's own limits.
  2. Enable Logging if you want AI Gateway to record requests and responses for auditing.
  3. Select Next.

Deploy​

Review the summary, then select Deploy. AI Gateway provisions the server and provides a server URL you'll use when configuring your AI client.

Connect to an AI client​

Once your server is deployed, you'll need to add it to the AI client your team uses. Select your client for setup instructions:

Tips​

  • You can create multiple MCP servers for the same application — for example, a read-only server for reporting agents and a read-write server for automation workflows.
  • If you're unsure which OAuth scopes to request, start with the minimum read-only set and add write scopes only when needed. Most application pages include scope recommendations.
  • You can edit a server's name, description, timeout, and security settings after deployment without redeploying.

Authentication​

Google Calendar uses OAuth 2.0 for authentication. Create OAuth credentials in Google Cloud Console with the redirect URI https://auth.aigateway.cequence.ai/v1/outbound/oauth/callback. The authorization endpoint is https://accounts.google.com/o/oauth2/v2/auth and token endpoint is https://oauth2.googleapis.com/token. Common scopes are https://www.googleapis.com/auth/calendar (full calendar access), https://www.googleapis.com/auth/calendar.readonly (read-only access), and https://www.googleapis.com/auth/calendar.events (event management only).

Available tools​

These tools let you manage calendars, events, attendees, and resources in Google Calendar.

ToolDescription
Create calendarCreate a new calendar with name and timezone
Update calendarModify calendar properties, description, and settings
Share calendarGrant edit or read-only access to other users
Create eventSchedule a new event with title, time, and attendees
Update eventModify event details including time, location, and description
Delete eventRemove an event from the calendar
List eventsRetrieve events for a date range with filtering
Add attendeesInvite participants to an event
Check RSVP statusView attendee responses to invitations
Create recurring eventSet up repeating events with complex recurrence patterns
Find available timeQuery multiple calendars to locate free slots
Manage remindersSet email, popup, or SMS notifications for events
Book resourcesSchedule conference rooms or equipment

Tips​

Use calendar.readonly scope for reporting and availability checking to minimize permissions—an agent doesn't need to modify calendars just to find open time slots.

Specify recurrence rules clearly (e.g., "every weekday at 9 AM except holidays") and include timezone information to avoid confusion across regions when creating recurring meetings.

Grant the agent access only to those calendars it actually needs if your organization uses resource calendars for rooms and equipment.

Double-check attendee email addresses and meeting duration before bulk-creating events to prevent scheduling conflicts or missed meetings.

Enable the calendar API's push notifications feature for production use to keep your MCP server in sync with manual changes made in the calendar UI.