calendar-mcp
Related Servers
Alternatives to calendar-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA macOS-only MCP server that lets Claude read and create events in Apple Calendar, list calendars, and find free time using EventKit.624 npm2MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for accessing macOS Calendar events2MIT
- AlicenseNot gradedqualityDmaintenanceA local MCP server for CalDAV that gives Claude read access to your calendar, enabling planning, conflict checking, and schedule summaries.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Apple Calendar via native EventKit API with proper recurring event support.35 npm10MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude and other MCP clients to read, search, and plan events across every calendar account on a Mac, including finding free time, preparing meetings, and creating or moving events, with deletes and changes to shared events requiring user approval. All data stays local via EventKit, and every change can be undone.MIT
- AlicenseNot gradedqualityAmaintenanceA local MCP server that enables Claude to read and, where permitted, safely write Apple Calendar, Reminders, Contacts, Notes, Mail, and Music data on macOS over stdio without Full Disk Access. It includes guarded changes, activity logging, undo, and optional Music play history.1,196 npmMIT
TDQS
Scored across 7 tools
Each tool targets a distinct operation: fetching one event, listing by range, searching by text, listing calendars, and the create/update/delete lifecycle. The overlap between list_events and search_events is clearly resolved by different query methods and return semantics.
All tools follow a consistent verb_noun snake_case pattern: get/list/search/create/update/delete plus event/calendars. Pluralization is used sensibly for list operations, so there are no confusing deviations.
Seven tools is well-scoped for a calendar server. Each tool covers a distinct and necessary operation without redundancy, and there is no bloat or overly thin coverage.
The event lifecycle is fully covered with create, get, list, search, update, and delete, and calendar enumeration supports filtering and event retrieval. Calendar creation and modification are reasonably left out since calendars are typically account-managed, so there are no critical dead ends.