Google Calendar
Expose Google Calendar read/write tools to your agent via Workspace service account and domain-wide delegation.
Overview
com.pulsemcp/google-calendar is a MCP server for the Build phase that integrates Google Calendar for Workspace via service account impersonation.
What is this MCP server?
- Service account auth with GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL and PEM private key
- GCAL_IMPERSONATE_EMAIL for domain-wide delegated user calendar access
- ENABLED_TOOLGROUPS toggles readonly vs readwrite tool sets
- Stdio transport through google-calendar-workspace-mcp-server on npx
- Version 0.0.11 with MCP schema 2025-09-29
- Tool groups: readonly and readwrite
- Three required service-account-related env vars
What problem does it solve?
Agents cannot plan around real meetings and deadlines when calendar data stays outside the MCP tool layer.
Who is it for?
Small teams on Google Workspace who want agent scheduling assist with centralized service-account auth.
Skip if: Personal Gmail-only calendars without Workspace delegation or builders avoiding Google admin console work.
What do I get? / Deliverables
After delegation setup, your agent accesses impersonated user calendars through grouped readonly or readwrite MCP tools.
- Calendar MCP tools scoped by ENABLED_TOOLGROUPS
- Agent access to impersonated Google Calendar data
Recommended MCP Servers
Journey fit
How it compares
Workspace calendar MCP connector, not a standalone calendaring app or ICS import skill.
Common Questions / FAQ
Who is com.pulsemcp/google-calendar for?
Builders on Google Workspace delegating calendar access to Claude Code, Cursor, or Codex via MCP.
When should I use com.pulsemcp/google-calendar?
When your agent must read or update a specific user calendar under domain-wide service account impersonation.
How do I add com.pulsemcp/google-calendar to my agent?
Run the stdio npx package, set service account and impersonate email env vars, configure ENABLED_TOOLGROUPS, and register in MCP settings.