Calendar AutoAuth

Calendar AutoAuth MCP Server enables a Google Calendar integration with automatic authentication inside your Claude Desktop environment. It lets you create, list, update, and delete events through natural language interactions, leveraging Google Calendar API with a streamlined OAuth flow and convenient credential storage.

How to use

You interact with the Calendar AutoAuth MCP Server through an MCP client in your environment. After you configure it, you can create events by providing a title, start and end times, a description, and a location. You can also retrieve, update, list within a time range, and delete events. All actions are performed against Google Calendar, with authentication handled automatically so you don’t need to reauthenticate for each operation.

To use it, ensure your MCP client is set up to connect to the calendar MCP server you configured. You will trigger actions like creating an event, listing upcoming events, updating event details, or removing events. The server handles Google OAuth2 authentication and stores credentials locally for ongoing use.

How to install

Prerequisites you need on your system before installing: Node.js and npm (or a compatible runtime for your setup). Ensure you have network access to install packages and to reach Google APIs.

Install via Smithery to add the MCP server for Claude Desktop automatically.

npx -y @smithery/cli install @gongrzhe/server-calendar-autoauth-mcp --client claude

Prepare Google Cloud credentials by creating a project, enabling the Calendar API, and generating OAuth 2.0 credentials. Save the JSON keys as gcp-oauth.keys.json and rename if needed.

Authentication can be performed globally or locally.

# Global authentication (recommended):
# First, place gcp-oauth.keys.json in the global config folder
mkdir -p ~/.calendar-mcp
mv gcp-oauth.keys.json ~/.calendar-mcp/

# Then authenticate from anywhere
npx @gongrzhe/server-calendar-autoauth-mcp auth

# Local authentication (credentials copied to global config)
# Place gcp-oauth.keys.json in your current directory
npx @gongrzhe/server-calendar-autoauth-mcp auth

What happens during authentication: the tool looks for gcp-oauth.keys.json in the current directory or in ~/.calendar-mcp/. If found in the current directory, it copies it to the global config. It then opens your browser to complete Google authentication and saves credentials to ~/.calendar-mcp/credentials.json. After authentication, credentials are stored globally and can be used from any directory; both Desktop app and Web application credentials are supported. For Web application credentials, ensure the redirect URI http://localhost:3000/oauth2callback is added.

Configure the MCP client in Claude Desktop to point to the calendar MCP server as shown.

Docker support

If you prefer using Docker, you can authenticate and run the server in a container. The following examples show how to authenticate and how to configure the MCP client to use Docker.

# Authentication with Docker
docker run -i --rm \
  --mount type=bind,source=/path/to/gcp-oauth.keys.json,target=/gcp-oauth.keys.json \
  -v mcp-calendar:/calendar-server \
  -e CALENDAR_OAUTH_PATH=/gcp-oauth.keys.json \
  -e "CALENDAR_CREDENTIALS_PATH=/calendar-server/credentials.json" \
  -p 3000:3000 \
  mcp/calendar auth

Usage from your MCP client via Docker (example configuration):

{
  "mcpServers": {
    "calendar": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-v",
        "mcp-calendar:/calendar-server",
        "-e",
        "CALENDAR_OAUTH_PATH=/gcp-oauth.keys.json",
        "-e",
        "CALENDAR_CREDENTIALS_PATH=/calendar-server/credentials.json",
        "-p",
        "3000:3000",
        "mcp/calendar",
        "auth"
      ]
    }
  }
}

Available tools

CreateEvent

Create a new Google Calendar event with a title, start and end times, optional description, and location.

ListEvents

List events within a specified time range, with optional limits and sorting.

UpdateEvent

Update the details of an existing event such as title, time, description, or location.

DeleteEvent

Delete an existing event by its ID.