A
licenseNot graded
qualityNot graded
maintenanceMCP server that lets AI agents manage Google Calendar -- create events, check availability, and manage schedules.
MIT
@calmesh/mcp-server
by davidklemme
Related Servers
Alternatives to @calmesh/mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server for the Calendly API. Manage events, invitees, and schedule meetings directly via AI assistants.12283 npmMIT
- FlicenseNot gradedqualityDmaintenanceMCP server for a desktop calendar that allows AI agents to manage events, check schedules, and avoid conflicts via standard MCP tools.2-
- AlicenseBqualityDmaintenanceA Model Context Protocol (MCP) server that connects AI agents to Google Workspace (Gmail, Calendar, Drive, Docs, Sheets, and Slides).302MIT
- AlicenseAqualityCmaintenanceCalendar MCP server with atomic booking, conflict prevention, deterministic RRULE expansion, and TOON token compression for AI agents.1812MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for read-only Google Calendar integration, providing calendar access to AI assistants.-
TDQS
A3.6/5.0
Scored across 22 tools
Disambiguation3/5
Most tools are clearly separated by domain (events, bookings, polls, connections), but 'get_events' and 'get_event_details' both fetch events in a date range with different detail levels, and 'check_availability' and 'get_slots' both return free time slots but in different contexts. These overlapping boundaries could cause agents to select the wrong tool.
Naming Consistency4/5
All tool names follow a consistent calmesh_verb_noun snake_case pattern, which is easy to read and predict. However, read operations use a mix of 'list', 'get', and 'check' (e.g., list_calendars, get_events, check_availability), a minor inconsistency that slightly reduces predictability.
Tool Count4/5
With 22 tools covering calendars, events, bookings, polls, and connections, the count is high but justified by the breadth of functionality. It sits slightly above the ideal 3-15 range but is not excessive for the domain.
Completeness3/5
The tool surface covers most workflows, but there is no update_event tool, making it impossible to modify existing events, and no delete_calendar. Bookings and polls also lack update operations, forcing workarounds like delete-and-recreate. These gaps could hinder common tasks.
Maintenance
ActivityInactive
ResponsivenessNo issues