F
licenseD
qualityD
maintenanceMCP server for interacting with Google Calendar, enabling reading events from public calendars and, with OAuth, creating, updating, and deleting events.
1
-
evite-mcp
by chrischall
Related Servers
Alternatives to evite-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for managing Google Calendar events.-
- AlicenseAqualityBmaintenanceMCP server for Apple Calendar and CalDAV providers. Enables listing, creating, updating, deleting events, and checking free/busy status with per-calendar write protection.6MIT
- AlicenseAqualityBmaintenanceAn MCP server for Apple iCloud Calendar over CalDAV, supporting list, search, create, update, delete, RSVP, and free-time finding without local macOS dependencies.7MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for MailCal that reads emails via IMAP, extracts calendar events (interviews, assessments, meetings, deadlines), and provides tools to list, sync, add, update, and delete these events.6-
- AlicenseAqualityBmaintenanceEnables creating events, invitations, and personalized guest links, and following RSVPs on InvitaAI from any MCP client.18MIT
TDQS
A3.9/5.0
Scored across 20 tools
Disambiguation4/5
Most tools target a distinct resource and action (events, guests, messages, photos), and descriptions clarify the boundaries. A few pairs could be confused—evite_send vs evite_send_message and evite_rsvp vs evite_rsvp_summary—but the descriptions are explicit enough to resolve the ambiguity.
Naming Consistency4/5
The evite_ prefix is consistent and most names follow verb_noun conventions like create_event, list_guests, and remove_guest. Deviations such as evite_rsvp, evite_send, evite_broadcast, and evite_rsvp_summary break the pattern slightly but remain readable.
Tool Count3/5
20 tools is on the heavy side for an MCP server, falling into the 16-25 range that feels bloated. Most tools do earn their place for the Evite domain, but a healthcheck tool and some overlapping messaging operations add unnecessary surface area.
Completeness4/5
The core event lifecycle is well covered: create, update, get, list, cancel, reinstate, duplicate, and send, plus guest management, RSVP, messaging, and templates. Minor gaps exist—photo upload has no listing/deletion, and message management lacks delete—but agents can still complete primary workflows.
Maintenance
ActivityActive
ResponsivenessResponsive