jmap-calendar-mcp
Related Servers
Alternatives to jmap-calendar-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to connect to calendar servers and manage events and tasks, including listing calendars, querying timeframes, creating, updating, completing, and deleting items through tools.3,018 npmMIT
- AlicenseAqualityBmaintenanceEnables an agent to read and manage calendars across Nextcloud, iCloud, Google and any CalDAV server, merging every account into one sorted view. Exposes tools for listing and searching events, finding free time, and creating, updating or deleting events, with secrets kept out of the config.8394 npmMIT
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with Fastmail calendars via CalDAV, allowing them to view, create, update, and delete calendar events using natural language.62MIT
- FlicenseNot gradedqualityCmaintenanceEnables LLM agents to read, schedule, update, and delete calendar events and tasks on a self-hosted CalDAV server, and to query availability for free/busy slots.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to interact with Google Calendar through natural language, supporting listing, creating, and searching events across accessible calendars.418 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to view, create, update, search, and manage Google Calendar events, including multi-account support and availability checks.17 npmBusiness Source 1.1
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: listing calendars, finding events, creating events, and updating events. There is little risk of confusing list_calendars with event search, or create_calendar_event with update_calendar_event.
All tool names use a consistent snake_case verb_noun pattern: list_calendars, find_calendar_events, create_calendar_event, update_calendar_event. The convention is predictable across the entire set.
Four tools is a well-scoped set for a focused calendar MCP server, with each tool covering a distinct operation. It stays lean without feeling arbitrary.
The surface covers listing calendars, finding events, creating events, and updating events, but lacks a delete_event operation and lacks calendar management operations. These are notable lifecycle gaps, though the existing tools support core read/write workflows.