🔔 VERSION UPDATE NOTICE 🔔 Version 2.0.0 moves to MCP protocol revision 2026-07-28 and implements PKCE on the OAuth flow. It requires Node.js 20 or newer. See the version history below for the full…
google-calendar-mcp is an MCP project maintained in the takumi0706/google-calendar-mcp repository. The maintainer describes its purpose as “🔔 VERSION UPDATE NOTICE 🔔 Version 2.0.0 moves to MCP protocol revision 2026-07-28 and implements PKCE on the OAuth flow. It requires Node.js 20 or…”. Read the project documentation for the complete scope.
The documented npm package is @takumi0706/google-calendar-mcp. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.
The example declares GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REDIRECT_URI. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.
Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| calendarId | optional): Calendar ID (uses primary calendar if omitted) |
| timeMin | optional): Start time for event retrieval (ISO 8601 format, e.g., "2025-03-01T00:00:00Z"). Empty strings, null, or undefined values are ignored |
| timeMax | optional): End time for event retrieval (ISO 8601 format). Empty strings, null, or undefined values are ignored |
| maxResults | optional): Maximum number of events to retrieve (default: 10) |
| orderBy | optional): Sort order ("startTime" or "updated"). Defaults to "startTime" if empty string, null, or undefined |
| event | Event details object containing fields to update (same structure as createEvent, all fields optional) |
| summary | required): Event title |
| location | optional): Event location |
| start | Start time object with: |
| dateTime | optional): ISO 8601 format (e.g., "2025-03-15T09:00:00+09:00") |
| date | optional): YYYY-MM-DD format for all-day events |
| timeZone | optional): Time zone (e.g., "Asia/Tokyo") |
| end | End time object (same format as start) |
| attendees | optional): Array of attendees with email and optional displayName |
| colorId | optional): Event color ID (1-11) |
| recurrence | optional): Array of recurrence rules in RFC5545 format (e.g., ["RRULE:FREQ=WEEKLY;BYDAY=MO,WE,FR"]) |
| eventId | required): ID of the event to delete |
{
"mcpServers": {
"google-calendar": {
"command": "npx",
"args": [
"-y",
"@takumi0706/google-calendar-mcp"
],
"env": {
"GOOGLE_CLIENT_ID": "your_client_id",
"GOOGLE_CLIENT_SECRET": "YOUR_GOOGLE_CLIENT_SECRET",
"GOOGLE_REDIRECT_URI": "http://localhost:4153/oauth2callback"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| GOOGLE_CLIENT_ID | Declared in the maintainer’s client configuration. | Check documentation |
| GOOGLE_CLIENT_SECRET | Declared in the maintainer’s client configuration. | Check documentation |
| GOOGLE_REDIRECT_URI | Declared in the maintainer’s client configuration. | Check documentation |
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.