Skip to main content
Glama
README.md
# MCP Google Calendar Server 
 
![npm](https://img.shields.io/npm/v/%40tobedoit%2Fgoogle-calendar-mcp)
![license](https://img.shields.io/badge/license-MIT-green)

A Model Context Protocol (MCP) server implementation that enables AI assistants like Claude to create and manage Google Calendar events. 
 
## Features 
 
- Create calendar events with title, description, start/end times, and alert
- Support for adding event attendees 
- OAuth2 authentication with Google Calendar API 
- Full MCP protocol implementation 
- Debug logging for troubleshooting 
 
## Prerequisites 
 
- Node.js v18 or later 
- Google Cloud Console project with Calendar API enabled 
- OAuth2 credentials (Client ID and Client Secret) 
 
## Setup 
 
Paste Claude "claude_desktop_config.json"
```json
{
  "mcpServers": {
    "zmes-calendar": {
      "command": "npx",
      "args": [
        "-y",
        "@tobedoit/google-calendar-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "your_google_client_id",
        "GOOGLE_CLIENT_SECRET": "your_google_client_secret",
        "GOOGLE_REFRESH_TOKEN": "your_google_refresh_token"
      }
    }
  }
}
```

TDQS

B3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is singular and clear.

Naming Consistency5/5

The single tool follows a clear verb_noun pattern (create_event), and with no other tools to compare, consistency is inherently perfect.

Tool Count2/5

One tool is too few for a Google Calendar server, as it lacks essential operations like listing, updating, or deleting events, making it severely limited for typical calendar management tasks.

Completeness1/5

The tool set is severely incomplete; it only allows event creation without any way to view, modify, or manage existing events, leaving major gaps in calendar functionality.

Maintenance

ActivityInactive
ResponsivenessUnresponsive