calendar-mcp
Related Servers
Alternatives to calendar-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol (MCP) server that allows Claude and other MCP clients to interact with Google Calendar. This server enables AI assistants to manage your calendar events, check availability, and handle scheduling tasks.MIT
- 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.5110 npm59MIT
- 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.118 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for Google Calendar integration in Claude Desktop, enabling AI assistants to manage Google Calendar events through natural language interactions.107 npm1ISC
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server that lets AI assistants interact with your personal Google Calendar using the Google Calendar API and OAuth 2.0.118 npmMIT
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol (MCP) server for Google Calendar integration with Claude Desktop. Create, update, delete, and manage calendar events with batch operations and enterprise-grade retry mechanisms.1MIT
TDQS
Scored across 23 tools
Most tools target distinct resource+action pairs, and descriptions proactively cross-reference potential confusions (create_event vs quick_add_event, move_event vs update_event, find_focus_time vs block_focus_time). A few genuine overlaps remain (suggest_reschedule's apply flag vs move_event, analyze_busyness vs time_audit), but they are clearly delineated in the text.
Strong verb_noun pattern throughout (find_events, create_event, update_event, delete_event, list_calendars, get_preferences, set_preferences). Minor deviations like quick_add_event, time_audit and schedule_mutual break the pattern slightly but remain readable and unambiguous.
23 tools is at the heavy end of the scale for a calendar server. Each tool is well-scoped and justified (event CRUD, focus time, preferences, analytics, cross-account conflict detection), but the surface is large enough that an agent must sift through several near-neighbors.
Covers event lifecycle (create/quick_add/find/update/move/delete), calendars (list/create), attendees (add/respond/status), free/busy, focus time, preferences and analytics. Minor gaps: no remove_attendee, no update_calendar or delete_calendar, which an agent would need for full calendar management.