A Google Calendar MCP server lets an AI list your schedule, find free slots and create events. Google Calendar uses OAuth 2.0, so setup is mostly about creating credentials. Here are the two routes for Claude and Cursor.
You will need OAuth credentials
Whichever route you pick, Google requires OAuth. In the Google Cloud Console:
- Create (or pick) a project and enable the Google Calendar API.
- Configure the OAuth consent screen.
- Create an OAuth client ID (type: Desktop or Web) and note the client ID and client secret.
For a remote connector, add the client's redirect URI (e.g. https://claude.ai/api/mcp/auth_callback) under Authorized redirect URIs.
Option A — official remote connector
Google documents an official Calendar MCP server you add as a custom/remote connector in clients that support OAuth MCP. You paste the client ID and secret, authorise through Google, and you are done — no local process. Best when your client supports remote MCP.
Option B — local server via npx
Community servers run locally and handle OAuth on first use. A Workspace-wide example:
{
"mcpServers": {
"google-calendar": {
"command": "npx",
"args": ["-y", "@dguido/google-workspace-mcp"],
"env": {
"GOOGLE_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
"GOOGLE_CLIENT_SECRET": "your-client-secret",
"GOOGLE_WORKSPACE_SERVICES": "calendar"
}
}
}
}
On the first tool call, a browser opens for Google consent; the token is cached locally. See MCP config file location for where this goes.
Verify
Ask: "What's on my calendar tomorrow?" Real events back means OAuth and scopes are correct.
Common problems
access_denied/ consent screen error — the consent screen is not configured, or your account is not a test user on an unverified app. Add yourself as a test user.redirect_uri_mismatch— the redirect URI in your client does not match the one registered in Cloud Console.- Read but not write — you only granted read scopes; re-consent with calendar write scope.
- No tools in client — Node 18+ required; see Cursor MCP not working.
Security
Calendar access reveals a lot about you. Grant read-only scope unless the AI must create events, and treat the client secret like a password — see MCP security best practices.
Going further
Calendar pairs with Gmail/Drive for a personal-assistant stack. Browse the productivity category or a loadout.