Google Calendar MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mcp-google-calendar -- npx -y @a1-x-tech/mcp-google-calendar

{
  "mcpServers": {
    "mcp-google-calendar": {
      "args": [
        "-y",
        "@a1-x-tech/mcp-google-calendar"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.mcp-google-calendar]
command = "npx"
args = ["-y", "@a1-x-tech/mcp-google-calendar"]

{
  "mcpServers": {
    "mcp-google-calendar": {
      "args": [
        "-y",
        "@a1-x-tech/mcp-google-calendar"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "mcp-google-calendar": {
      "args": [
        "-y",
        "@a1-x-tech/mcp-google-calendar"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: GOOGLE_CALENDAR_CLIENT_ID (Google OAuth2 client id (refresh-token flow).), GOOGLE_CALENDAR_CLIENT_SECRET (Google OAuth2 client secret (refresh-token flow). Treat it as a secret.), GOOGLE_CALENDAR_REFRESH_TOKEN (Google OAuth2 refresh token, exchanged for access tokens automatically. Treat it as a secret.), GOOGLE_CALENDAR_ACCESS_TOKEN (Static OAuth2 access token (~1h lifetime) — alternative to the refresh-token trio, mostly for testing.), GOOGLE_CALENDAR_OAUTH_PORT (Fixed port for the loopback listener of the in-chat login (127.0.0.1 + PKCE). Set it when the client runs over SSH port forwarding; otherwise a free port is picked per login.), GOOGLE_CALENDAR_API_BASE (API root override.), GOOGLE_CALENDAR_TIMEOUT_MS (Per-request timeout in milliseconds.), GOOGLE_CALENDAR_MAX_RETRIES (Retries on transient errors (429 always; 5xx/network for reads).). The author declared them in the registry entry; get the values from the project itself.