A
licenseB
qualityD
maintenanceMCP server enabling Cursor to interact with Google Workspace services including Gmail, Calendar, Drive, Docs, Sheets, Slides, Chat, and People via natural language.
58
MIT
Google Calendar MCP
by AnByoungHyun
Related Servers
Alternatives to Google Calendar MCP
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityNot gradedmaintenanceGoogle Calendar integration in Cursor IDE. This server enables AI assistants to manage Google Calendar events through natural language interactions.5 npm5ISC
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables natural language interaction with Google Calendar, allowing users to view, create, update, and delete calendar events through context-aware operations.75 npm1MIT
- AlicenseNot gradedqualityNot gradedmaintenanceMCP server that lets AI agents manage Google Calendar -- create events, check availability, and manage schedules.MIT
- FlicenseDqualityDmaintenanceMCP server for interacting with Google Calendar, enabling reading events from public calendars and, with OAuth, creating, updating, and deleting events.1-
- AlicenseAqualityAmaintenanceA Model Context Protocol server that integrates Google Calendar with Claude Desktop, enabling users to manage calendar events (view, create, update, delete) through natural language.5106 npm59MIT
TDQS
B3.3/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a clearly distinct purpose with no ambiguity: create_event, get_event_detail, list_day_events, list_month_events, and update_event target specific actions on calendar events. The descriptions clarify their unique scopes, such as day vs. month listing, preventing misselection.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern (e.g., create_event, get_event_detail, list_day_events). There are no deviations in style or convention, making the set predictable and readable for agents.
Tool Count4/5
With 5 tools, the count is well-scoped for a Google Calendar server, covering core operations like CRUD and listing. It's slightly lean but reasonable, as each tool earns its place without feeling thin or excessive for the domain.
Completeness4/5
The tool surface provides strong coverage for event management, including create, read (get and list), and update operations. A minor gap is the lack of a delete_event tool, which agents might need to work around, but core workflows are well-supported.
Maintenance
ActivityInactive
ResponsivenessNo issues