create_event
Create a calendar event with specified details
LABSCO SUMMARY
It writes and never reads, so nothing here can look at what is already on the calendar.
The one tool creates an event: there is no list, no search, no update and no delete, which means the agent cannot check for a clash beforehand and cannot take back what it just created. What it does do in one call is the entire event — summary, start and end, attendees, location, description and reminders — so booking something does not turn into a sequence of follow-up edits.
What it is
A single-tool Google Calendar writer: one call creates an event with its times, guests, place and reminders. It authenticates with your own Google OAuth client rather than a hosted service.
What you get
- create_event, which creates a calendar event from a summary, a start time and an end time.
- Attendees, a location, a description and reminders carried on the same call rather than added afterwards.
Requirements
Node.js v18 or later, and a Google Cloud project with the Calendar API enabled. Three values go into the environment: the OAuth client ID and secret, and a refresh token for the Google account whose calendar is being written to — which means the one-time OAuth dance happens before this server is any use.
Setup effort
One command plus credentials — npx -y @tobedoit/google-calendar-mcp, then supply credentials
USE CASES
01
Booking something the moment it is agreed
Put the whole event in one call — time, guests, place, reminders — while the conversation that decided it is still open.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected. The single tool is create_event; nothing reads, lists, updates or deletes events.
Requires
- npx on PATH
- Node.js v18 or later
- GOOGLE_CLIENT_ID in your environment
- GOOGLE_CLIENT_SECRET in your environment
- GOOGLE_REFRESH_TOKEN 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 one tool definition that rides along on every turn
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @tobedoit/google-calendar-mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"zmes-calendar": {
"command": "npx",
"args": [
"-y",
"@tobedoit/google-calendar-mcp"
],
"env": {
"GOOGLE_CLIENT_ID": "<YOUR_GOOGLE_CLIENT_ID>",
"GOOGLE_CLIENT_SECRET": "<YOUR_GOOGLE_CLIENT_SECRET>",
"GOOGLE_REFRESH_TOKEN": "<YOUR_GOOGLE_REFRESH_TOKEN>"
}
}
}
}
