authenticate
authenticate tool for Google Calendar operations
LABSCO SUMMARY
Your calendar, on your own OAuth app.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
One command plus credentials — npm install -g @takumi0706/google-calendar-mcp, then supply credentials
USE CASES
01
Connecting your calendar
Run the authentication flow once to authorize the server against your Google account before any event operations.
02
Scheduling and adjusting events
Create an event, set its color, and update or move it later as plans change — all from the conversation.
03
Reviewing and clearing your schedule
List the events on your calendar to see what is coming, and delete the ones that fell through.
5 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
createEvent
createEvent tool for Google Calendar operations
deleteEvent
deleteEvent tool for Google Calendar operations
getEvents
getEvents tool for Google Calendar operations
updateEvent
updateEvent tool for Google Calendar operations
BEFORE YOU INSTALL
What to know first
Tools you get
5 tools when we connected. getEvent (singular) is an internal helper, not a tool; the real one is getEvents. The ten prompts the server advertises are not tools.
Requires
- npx on PATH
- GOOGLE_CLIENT_ID in your environment
- GOOGLE_CLIENT_SECRET in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g @takumi0706/google-calendar-mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"google-calendar": {
"command": "npx",
"args": [
"-y",
"@takumi0706/google-calendar-mcp"
],
"env": {
"GOOGLE_CLIENT_ID": "<YOUR_GOOGLE_CLIENT_ID>",
"GOOGLE_CLIENT_SECRET": "<YOUR_GOOGLE_CLIENT_SECRET>",
"GOOGLE_REDIRECT_URI": "http://localhost:4153/oauth2callback"
}
}
}
}
