Google Calendar MCP Server with extensive support for calendar management
Google Calendar MCP Server with extensive support for calendar management. That is what the google mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
A Model Context Protocol (MCP) server that provides Google Calendar integration for AI assistants like Claude.
Installation goes through your MCP client rather than a global install: point it at Users on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
The server publishes 14 tools. What each one is for:
list-calendars — List all available calendarslist-events — List events with date filteringget-event — Get details of a specific event by IDsearch-events — Search events by text querycreate-event — Create new calendar eventsupdate-event — Update existing eventsdelete-event — Delete eventsrespond-to-event — Respond to event invitations (Accept, Decline, Maybe, No Response)get-freebusy — Check availability across calendars, including external calendarsget-current-time — Get current date and time in calendar's timezonelist-colors — List available event colorsmanage-accounts — Add, list, or remove connected Google accountsConfiguration is passed through the environment: GOOGLE_OAUTH_CREDENTIALS, ENABLED_TOOLS, GOOGLE_CALENDAR_MCP_TOKEN_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Google's toolset — list-calendars, list-events, get-event and 11 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| list-calendars | List all available calendars |
| list-events | List events with date filtering |
| get-event | Get details of a specific event by ID |
| search-events | Search events by text query |
| create-event | Create new calendar events |
| update-event | Update existing events |
| delete-event | Delete events |
| respond-to-event | Respond to event invitations (Accept, Decline, Maybe, No Response) |
| get-freebusy | Check availability across calendars, including external calendars |
| get-current-time | Get current date and time in calendar's timezone |
| list-colors | List available event colors |
| manage-accounts | Add, list, or remove connected Google accounts |
| Prerequisites | 1. A Google Cloud project with the Calendar API enabled 2. OAuth 2.0 credentials (Desktop app type) |
| Installation | Then add to Claude Desktop config using the local path or by specifying the path with the GOOGLE_OAUTH_CREDENTIALS environment variable. |
{
"mcpServers": {
"google-calendar": {
"command": "npx",
"args": ["@cocal/google-calendar-mcp"],
"env": {
"GOOGLE_OAUTH_CREDENTIALS": "/path/to/your/gcp-oauth.keys.json"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GOOGLE_OAUTH_CREDENTIALS | Configuration value read at startup. | Optional |
| ENABLED_TOOLS | Configuration value read at startup. | Optional |
| GOOGLE_CALENDAR_MCP_TOKEN_PATH | Credential the server authenticates with. | Yes |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.