This MCP server for Google Calendar allows users to list, create, update, and manage calendar events through an OAuth proxy to Google.
From the registry: Allow AI systems to list, create, update, and manage Google Calendar events.
$ git clone https://github.com/domdomegg/google-calendar-mcp && cd google-calendar-mcp && npm install && npm run buildhttps://github.com/domdomegg/google-calendar-mcp$ GOOGLE_CLIENT_ID=<your-client-id> GOOGLE_CLIENT_SECRET=<your-client-secret> MCP_TRANSPORT=http npm startPlease install the `google-cal-mcp` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Google OAuth credentials** — Create OAuth 2.0 Web application credentials, enable Google Calendar API, add http://localhost:3000/callback as redirect URI (https://console.cloud.google.com/)
- **Clone and install** — Clone the repo and install dependencies Run: `git clone https://github.com/domdomegg/google-calendar-mcp && cd google-calendar-mcp && npm install && npm run build` (https://github.com/domdomegg/google-calendar-mcp)
- **Start the server** — Run with OAuth credentials in env; server listens on http://localhost:3000/mcp Run: `GOOGLE_CLIENT_ID=<your-client-id> GOOGLE_CLIENT_SECRET=<your-client-secret> MCP_TRANSPORT=http npm start`
Canonical MCP server config (HTTP transport):
- url: `http://localhost:3000/mcp`
Note: OAuth proxy to Google Calendar API; client handles OAuth via well-known endpoints on the same host. Override port with PORT=<port>.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.GOOGLE_CLIENT_IDrequiredClient ID for Google OAuthGOOGLE_CLIENT_SECRETrequiredClient Secret for Google OAuthAtlassian Rovo MCP Server