Google Calendar MCP ServerBLOCK
MCP integration for Google Calendar to manage events.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
A Model Context Protocol (MCP) server that provides Google Calendar integration for AI assistants like Claude.
I also built Cocal, the calendar integration I wanted for chat: a visual calendar inside Claude that shows your whole day around a proposed time, plus booking links and invites you manage from the conversation. It's hosted, so it works on desktop and mobile with no Google Cloud setup.
Real Cocal UI with sample calendar data. Click either screenshot to enlarge. Try Cocal →
Features
- Multi-Account Support: Connect multiple Google accounts (e.g., work, personal) and query them simultaneously
- Multi-Calendar Support: List events from multiple calendars in a single request
- Cross-Account Conflicts: Detect overlapping events across any combination of calendars
- Event Management: Create, update, delete, and search calendar events
- Recurring Events: Advanced modification capabilities for recurring events
- Free/Busy Queries: Check availability across calendars
- Smart Scheduling: Natural language understan
62203eb4d7d7OBSERVED · 2026-10-12Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add google-calendar-mcp --env CLAUDE_API_KEY=${CLAUDE_API_KEY} --env GOOGLE_APPLICATION_CREDENTIALS=${GOOGLE_APPLICATION_CREDENTIALS} --env GOOGLE_CALENDAR_MCP_TOKEN_PATH=${GOOGLE_CALENDAR_MCP_TOKEN_PATH} --env GOOGLE_OAUTH_CREDENTIALS=${GOOGLE_OAUTH_CREDENTIALS} -- npx -y @cocal/[email protected]{
"mcpServers": {
"google-calendar-mcp": {
"command": "npx",
"args": [
"-y",
"@cocal/[email protected]"
],
"env": {
"CLAUDE_API_KEY": "${CLAUDE_API_KEY}",
"GOOGLE_APPLICATION_CREDENTIALS": "${GOOGLE_APPLICATION_CREDENTIALS}",
"GOOGLE_CALENDAR_MCP_TOKEN_PATH": "${GOOGLE_CALENDAR_MCP_TOKEN_PATH}",
"GOOGLE_OAUTH_CREDENTIALS": "${GOOGLE_OAUTH_CREDENTIALS}"
}
}
}
}Exposed tools (13)
9 read · 3 write · 1 destructive. Blast radius: 1 tool can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
create-event | write | Create a new calendar event. eventLabelId (custom color) takes precedence over the legacy colorId. |
create-events | write | Create multiple calendar events in bulk. Accepts shared defaults (account, calendarId, timeZone) that apply to all events, with per-event overrides. Skips conflict and duplicate detection for speed. |
delete-event | destructive | Delete a calendar event. |
get-current-time | read | Get the current date and time. Call this FIRST before creating, updating, or searching for events to ensure you have accurate date context for scheduling. |
get-event | read | Get details of a specific event by ID. |
get-freebusy | read | Query free/busy information for calendars. Note: Time range is limited to a maximum of 3 months between timeMin and timeMax. |
list-calendars | read | List all available calendars |
list-colors | read | List available legacy color IDs for calendar events. Pass calendarId to also get that calendar |
list-events | read | List events from one or more calendars. Supports both calendar IDs and calendar names. |
manage-accounts | read | |
respond-to-event | read | Respond to a calendar event invitation with Accept, Decline, Maybe (Tentative), or No Response. |
search-events | read | Search for events in a calendar by text query. |
update-event | write | Update an existing calendar event with recurring event modification scope support. eventLabelId (custom color) takes precedence over the legacy colorId. |
Trust audit
BLOCKgrade D · trust 69/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | FAIL |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (6 observation(s))
- Network
- declared (3 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- found
Findings (22)
gaxios ~ axios
callback_url: started.callbackUrl!,
callback_url?: string;
'-----BEGIN PRIVATE KEY-----',
delete-event
.cursorignore
.release-please-manifest.json
console.log(`\nTotal token count: ${analysisReport.totalTokens.toLocaleString()}`);import { getCredentialsProjectId } from "../../auth/utils.js";import { CalendarRegistry } from "../../services/CalendarRegistry.js";import { validateAccountId } from "../../auth/paths.js";import { convertToRFC3339 } from "../../utils/datetime.js";import { isCalendarNotAccessibleError } from "../../utils/google-api-errors.js";expect(response.callback_url).toContain('oauth2callback');`GOOGLE_CALENDAR_API_BASE_URL` is for an egress proxy that originates TLS itself, e.g. `http://127.0.0.1:10255/tenant-a/calendar`. A path prefix is kept, so requests go to `<url>/calendar/v3/...`. Cal
This applies to the `auth` command and the `manage-accounts` tool. The HTTP transport's account page (`/accounts`) uses a single fixed callback, `http://<host>:<port>/oauth2callback` (for example `htt
To send Calendar API calls through an egress proxy that originates TLS itself, set `GOOGLE_CALENDAR_API_BASE_URL` to the proxy, e.g. `http://127.0.0.1:10255/tenant-a/calendar`. Requests go to `<url>/c
process.env.GOOGLE_CALENDAR_API_BASE_URL = 'http://127.0.0.1:10255/tenant-a/calendar';
expect(routed).toEqual(['Calendar API calls routed to http://127.0.0.1:10255 (GOOGLE_CALENDAR_API_BASE_URL)']);
@modelcontextprotocol/sdk, gaxios, google-auth-library, googleapis, open, zod, @anthropic-ai/sdk, @types/node
- Make changes to events: Full access
**Issue:** Calendar appearing in user's list doesn't guarantee full access.
Gates applied: no_behavioural_pass.
62203eb4d7d7full audit observations/trust-audit/mcp-server/nspady__google-calendar-mcp.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-12 | 62203eb4d7d7 | BLOCK | D | 69 | first audit |
Questions
What is the @cocal/google-calendar-mcp MCP server?
MCP integration for Google Calendar to manage events.
What tools does @cocal/google-calendar-mcp expose?
13 in total: 9 read-only, 3 that write, and 1 that can delete or overwrite (delete-event). Every one is listed on this page with its risk.
Is @cocal/google-calendar-mcp safe to connect to an agent?
No — not without reading the findings first. The audit graded it D (69/100) and found 1 critical or high issue in the source. Each one is listed on this page with the file and line it is on. Separately from the audit: 1 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does @cocal/google-calendar-mcp need?
It reads CLAUDE_API_KEY, GOOGLE_APPLICATION_CREDENTIALS, GOOGLE_CALENDAR_MCP_TOKEN_PATH, GOOGLE_OAUTH_CREDENTIALS, GOOGLE_SERVICE_ACCOUNT_KEY and OPENAI_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does @cocal/google-calendar-mcp run?
It speaks stdio and streamable-http, so it runs as a local process your client starts. It is published on npm as @cocal/google-calendar-mcp at 2.7.0.
How current is this page?
The grade is for one exact copy of the source (62203eb4d7d7), read on 2026-10-12. The repository is watched and re-audited when it changes.