MCP Google Calendar Plus MCP Server

The ONLY comprehensive MCP server for Google Workspace - Calendar, Contacts, and Gmail management in Claude, Cursor, Windsurf

Local serverstdioGo

What is the MCP Google Calendar Plus MCP server?

The ONLY comprehensive MCP server for Google Workspace - Calendar, Contacts, and Gmail management in Claude, Cursor, Windsurf. Exposed over MCP by the mcp google calendar plus mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Complete Google Workspace integration for Claude Desktop and other AI agents using the Model Context Protocol (MCP). This server provides comprehensive management capabilities for Calendar, Contacts, and Gmail with OAuth2 authentication.

Its toolset

Everything the assistant can do here goes through one of these:

  • Authentication — The Authentication tool exposed by this server

Adding it to your client

mcp-google on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration

You will need 6 environment variables: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_OAUTH_CREDENTIALS, YOUR_CLIENT_ID, YOUR_CLIENT_SECRET, GOOGLE_CALENDAR_MCP_TOKEN_PATH. 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.

When to reach for it

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. MCP Google Calendar Plus's toolset — Authentication — is a fair guide to whether it matches your workflow. It is maintained by 199-biotechnologies; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • 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 mcp google calendar plus mcp server does with a few real requests.

Available tools

ToolWhat it does
AuthenticationThe Authentication tool exposed by this server.

How to install the MCP Google Calendar Plus MCP server

{
  "mcpServers": {
    "google-workspace": {
      "command": "npx",
      "args": ["-y", "mcp-google"],
      "env": {
        "GOOGLE_CLIENT_ID": "YOUR_CLIENT_ID.apps.googleusercontent.com",
        "GOOGLE_CLIENT_SECRET": "YOUR_CLIENT_SECRET"
      }
    }
  }
}

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

Configuration

VariableDescriptionRequired
GOOGLE_CLIENT_IDConfiguration value read at startup.Optional
GOOGLE_CLIENT_SECRETCredential the server authenticates with.Yes
GOOGLE_OAUTH_CREDENTIALSConfiguration value read at startup.Optional
YOUR_CLIENT_IDConfiguration value read at startup.Optional
YOUR_CLIENT_SECRETCredential the server authenticates with.Yes
GOOGLE_CALENDAR_MCP_TOKEN_PATHCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP Google Calendar Plus to Authentication.

Frequently asked questions

It connects MCP Google Calendar Plus to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Authentication) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Google Calendar Plus directly.