Skipping interactive consent means no browser round trip and no refresh tokens to babysit, which suits a calendar that belongs to a team or a system rather than to a person. It also means access is granted by sharing the calendar with the service account, so the scope is whatever that calendar is, and revoking is a sharing change rather than a token revocation. Early version, small surface — four operations and nothing else.
A small MCP server for calendar management. It authenticates with a Google service account rather than an interactive OAuth flow, which means it is configured once with a credentials file and a calendar id and then simply works.
- Calendar events created from a conversation
- Existing events listed
- Events updated in place
- Events deleted
A Google Cloud service account with a JSON key, saved as `credentials.json` — the README walks through creating it in IAM & Admin. Three environment variables: `GOOGLE_CALENDAR_ID` for the target calendar, `GOOGLE_TIME_ZONE`, and `GOOGLE_CREDENTIALS_PATH` pointing at the key file. Install with `npm install -g @cablate/mcp-google-calendar` or run it through `npx -y @cablate/mcp-google-calendar` (0.0.3 in package.json). One thing to check before debugging a launch failure: the published package's bin entry is named `mcp-doc-forge`, while the README's CLI example calls `mcp-google-calendar`. MIT licensed.
One command plus a key — npx -y @cablate/mcp-google-calendar, then supply credentials