Google Calendar MCP Server with extensive support for calendar management
Strong foundation with 8 tools covering calendar operations. All tools have clear names starting with action verbs (list-, create-, update-, delete-, get-, manage-). All input schemas are present with types and descriptions. Tool descriptions are concise (40-80 chars) and actionable. Multi-account support throughout is well-designed. However, output schemas are not documented, LLMs cannot see what fields are returned or how to chain tools. Error handling guidance is absent. Security documentation for credential injection is not visible in provided code. Some parameter descriptions could be more specific about formats and constraints (e.g., 'RFC 3339 format' is stated but examples and edge cases are missing).
Create a new calendar event
Delete a calendar event
Get the current time in a specified timezone
Get details of a specific calendar event
Get free/busy information for calendars in a time range
List events from a calendar with filtering by time range and optional search terms
Manage Google account authentication. Actions: 'list' (show accounts), 'add' (authenticate new account), 'remove' (remove account).
Output schemas are not documented. LLMs cannot infer what fields are returned from list-events, create-event, get-event, or get-freebusy. This breaks tool chaining, an LLM cannot know whether a returned event includes attendee details, whether event_id or eventId is the key, or what structure free/busy info uses. Without documented output, agents waste tokens on follow-up introspection calls.
Error handling guidance is absent. Tools return raw API errors without recovery hints. For example, if create-event fails because a user email is invalid, the error should guide the LLM: 'Invalid attendee: [email protected], verify email is correct, or remove and add manually.' Raw errors like 'Invalid attendee email' provide no actionable next step.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 65 | 2026-07-28+ | v2 |
| 2026-03-09 | C | 61 | - | v1 |
Update an existing calendar event
Destructive tool (delete-event) has no confirmation or dry-run support. Agents can irreversibly delete calendar events with a single call. Pattern:confirmation-request recommends gating destructive operations behind a 'confirm' step or explicit 'mode: dry-run' parameter to prevent accidental deletions.
Parameter 'q' in list-events lacks format specification. The description says 'Optional search query to filter events' but does not explain: What syntax is supported? Can you use boolean operators? What fields are searched? Without clarity, LLMs guess and send queries that fail or return empty results.
Time parameters (timeMin, timeMax, startTime, endTime) are described as 'RFC 3339 format' but lack examples or default behavior. What happens if timeMin is omitted? Does the API default to 'now'? 24 hours ago? Will the tool fail silently? Agents should not guess, the description must state behavior explicitly.
Security: No visible documentation on how Google API credentials are handled. Code shows environment-variable config support (Dockerfile references /home/nodejs/.config/google-calendar-mcp), but the tool definitions do not declare 'requires auth' or scope requirements. Per pattern:scope-declaration, each tool should declare minimum required permissions (e.g., 'read:calendar', 'write:calendar', 'delete:calendar').