It keeps the credentials in your hands: you register the OAuth app in your Google Cloud Console and the server runs the authorization-code flow with PKCE, so the token belongs to your app rather than a third party's. The tool set is deliberately small — the four event operations plus authenticate — which is all a calendar assistant actually needs, colors included.
A server bridging an AI client to the Google Calendar API: five tools to authenticate and to read, create, update and delete calendar events. Runs over stdio.
- getEvents reads events from your calendar, and createEvent, updateEvent and deleteEvent cover the full write cycle
- Event colors supported through a colorId parameter on create and update
- authenticate runs the Google OAuth2 flow — an authorization-code flow with PKCE (S256) — to connect your account
- Comprehensive event management over the Calendar API, driven by natural language rather than the Calendar UI
Your own Google OAuth2 credentials from the Google Cloud Console — GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET and GOOGLE_REDIRECT_URI (default http://localhost:4153/oauth2callback). Node.js 20 or newer, run as npx @takumi0706/google-calendar-mcp. TOKEN_ENCRYPTION_KEY is optional and auto-generated if not set; the auth server defaults to port 4153.
One command plus a key — npm install -g @takumi0706/google-calendar-mcp, then supply credentials