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
-
gcal-fast-mcp
by jeffmm
Related Servers
Alternatives to gcal-fast-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for Google Calendar that enables listing, creating, updating, and deleting events, quick-add from natural language, responding to invitations, and checking availability across multiple accounts.MIT
- AlicenseAqualityBmaintenanceA sample MCP server built with FastMCP that demonstrates basic tools and a Google OAuth integration for accessing Google APIs like Calendar.2MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for Google Calendar that enables managing calendar events, scheduling meetings, RSVPing, and checking availability through natural language.28 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA Google Calendar MCP server that enables listing, creating, updating, and deleting calendar events and calendars through natural language.7 npmISC
- FlicenseNot gradedqualityDmaintenanceAn MCP server that provides integration with Google Calendar, allowing users to list calendars and manage events. It enables searching, creating, and modifying calendar entries through tools designed for the Model Context Protocol.-
TDQS
A3.6/5.0
Scored across 9 tools
Disambiguation4/5
Each tool targets a distinct resource+action combination: calendars vs events are clearly separated, and get/list/create/update/delete are unambiguous. quick_add and check_availability are additional distinct operations. Only slight potential confusion exists between list_events and check_availability, though they serve different purposes (event detail vs busy windows).
Naming Consistency5/5
All tools follow a consistent verb_noun pattern: list_calendars, get_calendar, list_events, get_event, create_event, update_event, delete_event. quick_add and check_availability deviate slightly but are well-established domain terms that read naturally and don't break the overall pattern.
Tool Count5/5
Nine tools is well within the ideal 3-15 range. Each tool serves a meaningful purpose for a Google Calendar MCP server: full CRUD on calendars and events, plus two useful extras (NLP quick add and availability checking). No tool feels redundant or padding.
Completeness5/5
The surface provides full lifecycle coverage for both calendars (list, get) and events (list, get, create, update, delete). quick_add and check_availability round out common user workflows. Missing operations like moving events or managing reminders are minor and not core to basic calendar operations.
Maintenance
ActivityStale
ResponsivenessNo issues