Google Calendar's Official MCP Server, Part of Workspace's Per-App Model

Google Calendar has its own dedicated, official MCP server, part of the same family as Gmail's and Drive's — Google documents configuration for all of them together at developers.google.com/workspace/guides/configure-mcp-servers, with each Workspace product getting its own focused server rather than one server trying to cover everything.

What an Agent Can Actually Do

Through the Calendar MCP server, a connected agent can list upcoming events, check availability, and schedule new meetings on the authenticated user's behalf — inheriting that user's existing calendar sharing and permission settings rather than a separate elevated grant.

Why Per-App Servers Instead of One Combined Server

Google's choice to ship Gmail, Calendar, and Drive as separate MCP servers (rather than one "Google Workspace" server) mirrors the same scope-discipline principle Swiggy applied with its three independent servers — an agent that only needs calendar access doesn't need to be granted email or file access just because they happen to come from the same vendor.

Community Alternatives

Community-built options like piotr-agier/google-drive-mcp bundle Calendar alongside Drive, Docs, Sheets, and Slides in a single self-hosted server — worth considering if you specifically want one combined server under your own infrastructure rather than Google's separate managed endpoints.