Claude Google Calendar Connector: Setup and Use

Claude does not include a built-in Google Calendar connector in its default settings, but Google Calendar is accessible via the Google Calendar API, which several MCP servers support. With an authorized connection, Claude can read your schedule, help you prepare for meetings, and draft follow-up tasks. fenbs keeps the meeting brief, the accepted decisions, and the assigned follow-up tasks so the work does not disappear when the session ends.

The right connection route depends on whether you already use a Google Workspace connector in Claude and whether you want standalone calendar access or a broader Google connection.

Two routes to connect Google Calendar

Route 1: if you already have a Google Workspace or Google Drive connector set up in Claude, check whether it includes Google Calendar access. Some connectors cover the full Google Workspace suite, including Calendar events, and you may already have access without additional setup.

Route 2: install a dedicated Google Calendar MCP server. Several open-source servers use the Google Calendar API with OAuth 2.0 to let Claude read and, where you authorize it, create events. This route is more narrowly scoped, which is useful if you want calendar access without granting Claude access to your Drive or Gmail.

Setting up a Google Calendar MCP server

To connect a Google Calendar MCP server, you will need to authorize it through Google OAuth. The server will ask you to sign in to your Google account and approve specific scopes. The two most common scopes are read-only calendar access (calendar.readonly) and full calendar access (calendar). Choose read-only unless you specifically need the server to create or modify events.

Verify which Google accounts are connected. If you have personal and work Google accounts, confirm that the MCP server is authorized against the right one, especially if your work calendar is managed by your organization.

See Claude connectors explained for the general MCP connection setup. For the broader Google connector landscape, see Claude Microsoft 365 for a comparison with the Microsoft side of calendar and productivity access.

What Claude can do with calendar access

With Google Calendar access, Claude can read your upcoming events, summarize the week ahead, identify scheduling conflicts, pull attendees and descriptions for a specific meeting, and help you draft a pre-meeting brief. These tasks are genuinely useful for preparing before a busy day or before a complex negotiation.

Claude cannot attend meetings, take notes during calls, or automatically create events without being asked. Any event creation should be reviewed before it is confirmed.

Organizational Google accounts and access controls

If your Google Calendar is managed by your employer through Google Workspace, the organization may restrict which third-party apps can connect to it. Some organizations require administrator approval before an external app can read calendar data via OAuth.

If authorization fails or the MCP server cannot read your calendar, check with your Google Workspace administrator whether the app is blocked. You may need to submit an approval request before the connection can proceed.

Personal versus work Google calendars

Most people have at least two Google calendars: a personal one and a work one managed by their employer. These are separate Google accounts with separate OAuth authorizations. When you set up a Google Calendar MCP server, you authorize it against one Google account. Check which account you are authorizing before approving the OAuth request.

If your work and personal calendars are in different Google accounts, you may need to authorize the server twice, once for each, or choose the account most relevant to the sessions you plan to run. For work-related meeting preparation, authorize the work Google account. For personal scheduling, the personal account.

Keep the two separate unless you have a specific reason to combine them. A session that can see both your personal appointments and your work meetings is harder to manage and may surface private information in a work context.

Reviewing access before each session

Google Calendar contains more than your schedule. It may include private events, location data, notes, and meeting links. Before each calendar-connected session, consider whether those details are relevant to the task.

If you are preparing for a work meeting, work calendar access is relevant. If you are planning a project with no meeting component, calendar access may not add anything. Connect only what the session genuinely needs.

How to do this with fenbs

1. Create a free account at fenbs. Add a project for the recurring work that involves calendar review.
2. Write the standing rules for how Claude should handle calendar context, such as which calendar it should use and what it should not share, as Decisions and rules.
3. After each calendar-connected session, add the accepted decisions and assigned follow-up tasks to the project.
4. Save Where we left off with the current next step before closing the session.
5. Connect Claude over MCP from Integrations so the next session reads the project context and existing decisions before pulling calendar data.

fenbs does not connect to Google Calendar. It holds the decisions and follow-ups that result from calendar review so they survive beyond the session. For setup help with other Google connectors, see Claude research connectors.