GCalendar MCP Server

MCP server implementation for Google Calendar integration

Local serverstdio

What is the GCalendar MCP MCP server?

GCalendar MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server implementation for Google Calendar integration.

What you get

A Model Context Protocol (MCP) server implementation that enables AI assistants like Claude to create and manage Google Calendar events.

  • 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

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Configuration and credentials

You will need 3 environment variables: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REFRESH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Node.js v18 or later - Google Cloud Console project with Calendar API enabled - OAuth2 credentials (Client ID and Client Secret)

Choosing this one

Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by tobedoit; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the gcalendar mcp mcp server does with a few real requests.

How to install the GCalendar MCP MCP server

{
  "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"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js v18 or later - Google Cloud Console project with Calendar API enabled - OAuth2 credentials (Client ID and Client Secret)
VariableDescriptionRequired
GOOGLE_CLIENT_IDConfiguration value read at startup.Optional
GOOGLE_CLIENT_SECRETCredential the server authenticates with.Yes
GOOGLE_REFRESH_TOKENCredential the server authenticates with.Yes

Frequently asked questions

It connects GCalendar MCP to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with GCalendar MCP directly.