Multi-Account Google Calendar MCP
nspadyLABSCO SUMMARY
API-key auth is the constraint that decides whether this fits.
It reads a calendar with a key rather than an OAuth flow, which makes setup short and means the calendar must be shared or public. For a team calendar, a room schedule or a published events feed that is exactly right. For your own private calendar it will not work, and the README says OAuth is future work rather than a flag you can turn on. Recurring events and descriptions are also listed as not yet handled.
What it is
A small MCP server that connects to the Google Calendar API and returns the events on a date you name. It is built for the editor case — asking what today looks like without leaving Cursor — and validates its input with zod so a malformed date fails cleanly rather than silently.
What you get
- The calendar events for a specific date, read live from Google Calendar
- Schema validation on the input via zod, so a bad date is rejected rather than turned into an empty result
- Credentials kept in environment variables rather than in the source, with a documented
.mcpconfig block for wiring it into a client - A deliberately small surface — one calendar, read-only, no event creation
Requirements
A Google Calendar API key in GOOGLE_API_KEY and the calendar's ID or email in CALENDAR_ID, with the Google Calendar API enabled in your Google Cloud Console. Because it authenticates with an API key rather than OAuth, the calendar has to be public or shared appropriately — a private personal calendar will not be readable this way. There is no published package: clone, npm install, create the .env, and point your client at server.js. The README lists OAuth2 for multiple users, recurring events and event descriptions as future work, so treat those as absent today.
Setup effort
Build from source — git clone https://github.com/PranayChowdhury00/MCP_SERVER.git
USE CASES
01
Checking a day's schedule while you work
Ask for the events on a date from inside the editor rather than switching to a calendar tab.
02
Giving an assistant your team's calendar
Point it at a shared or public calendar ID, which is what the API-key auth path supports.
03
Planning around what is already booked
Pull the events for the day you are planning, so the assistant is scheduling around real commitments.
BEFORE YOU INSTALL
What to know first
Requires
- node on PATH
- GOOGLE_API_KEY in your environment
- CALENDAR_ID in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/PranayChowdhury00/MCP_SERVER.git
cd MCP_SERVER
npm installMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"myCalenderData": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_SERVER>/server.js"
],
"env": {
"GOOGLE_API_KEY": "<YOUR_GOOGLE_API_KEY>",
"CALENDAR_ID": "<YOUR_CALENDAR_ID>"
}
}
}
}<YOUR_PATH_TO_MCP_SERVER> is the full path of your clone, and <YOUR_GOOGLE_API_KEY> is your Google Calendar API key, and <YOUR_CALENDAR_ID> is the calendar's ID or email. The README's block gives just server.js, which is found only if the client starts inside the clone.
