mcpbeat Sign in

Google Calendar MCP Server

local only

Google Calendar MCP runs on your own machine — the client starts it, so there is no endpoint to ping.

Google Calendar MCP server: list, read, create, update and delete events and calendars.

—
Installs / week
npm · @renzo.johnson/google-calendar-mcp
—
Stars
on GitHub
—
Last commit
from GitHub
—
License
language unknown

Nothing serious here today

Today is the operative word: we check Google Calendar MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

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.

run in your terminal
claude mcp add google-calendar-mcp -- npx -y @renzo.johnson/google-calendar-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "google-calendar-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@renzo.johnson/google-calendar-mcp"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.google-calendar-mcp]
command = "npx"
args = ["-y", "@renzo.johnson/google-calendar-mcp"]
.cursor/mcp.json
{
  "mcpServers": {
    "google-calendar-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@renzo.johnson/google-calendar-mcp"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "google-calendar-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@renzo.johnson/google-calendar-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: GOOGLE_APPLICATION_CREDENTIALS (Path to a service account key or authorized_user JSON file. Optional if you use gcloud Application Default Credentials or the OAuth variables), GOOGLE_OAUTH_CLIENT_ID (OAuth client ID. Set together with the client secret and refresh token), GOOGLE_OAUTH_CLIENT_SECRET (OAuth client secret), GOOGLE_OAUTH_REFRESH_TOKEN (OAuth refresh token with the Google Calendar scopes).

Alternatives to Google Calendar MCP

same job, measured the same way
G
Google Tasks MCP
by renzojohnson

Google Tasks MCP server: list, create, update, complete, move and delete tasks and lists.

local only
Google Calendar
by domdomegg

Allow AI systems to list, create, update, and manage Google Calendar events.

70 installs/wk local only
Gcal
by mintmcp

A MCP server that works with Google Calendar to manage event listing, reading, and updates.

answering
G
Google Chat MCP
by renzojohnson

Google Chat MCP server: read spaces and messages, send, edit and delete messages, create spaces.

local only
Calendar MCP
by deciduus

Google Calendar for LLM agents: find, create, update, move, delete events; free/busy; scheduling.

173 installs/wk local only
MCP Calendar
by infoinlet-marketplace

Google Calendar for AI agents — list/create/delete events and free-busy via OAuth token.

51 installs/wk local only
Google Calendar MCP
by mmedum

Google Calendar over MCP: calendars, events, recurrence and availability.

local only
Google Contacts MCP
by a1-x-tech

MCP server for the Google People API: search, create, update and delete contacts and groups.

216 installs/wk local only

Google Calendar MCP — questions

Answers built from our own checks of this server.

Why is there no uptime for Google Calendar MCP?
Google Calendar MCP runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @renzo.johnson/google-calendar-mcp.
How do I connect Google Calendar MCP?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls @renzo.johnson/google-calendar-mcp straight from npm; nothing to host, nothing to sign up for.