MCP.so
Sign In

Calendar AutoAuth MCP Server

@MCP-Mirror

About Calendar AutoAuth MCP Server

Mirror of

Basic information

Category

Productivity

Transports

stdio

Publisher

MCP-Mirror

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "GongRzhe_Calendar-Autoauth-MCP-Server": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli",
        "install",
        "@gongrzhe/server-calendar-autoauth-mcp",
        "--client",
        "claude"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Calendar AutoAuth MCP Server?

A Model Context Protocol (MCP) server that integrates Google Calendar with Claude Desktop, using auto-authentication via OAuth2. It enables AI assistants to manage Google Calendar events through natural language interactions.

How to use Calendar AutoAuth MCP Server?

Install via Smithery (npx -y @smithery/cli install @gongrzhe/server-calendar-autoauth-mcp --client claude) or run npx @gongrzhe/server-calendar-autoauth-mcp auth after placing a gcp-oauth.keys.json file in ~/.calendar-mcp/. Then add a calendar entry to Claude Desktop’s mcpServers configuration. Docker usage is also documented.

Key features of Calendar AutoAuth MCP Server

  • Create calendar events with title, time, description, and location
  • Retrieve event details by event ID
  • Update existing events (title, time, description, location)
  • Delete events
  • List events within a specified time range
  • Simple OAuth2 flow with auto browser launch
  • Global credential storage in ~/.calendar-mcp/

Use cases of Calendar AutoAuth MCP Server

  • Schedule meetings and appointments via natural language in Claude Desktop
  • Update event details without leaving the chat interface
  • Query upcoming events within a date range
  • Remove cancelled events directly from a conversation

FAQ from Calendar AutoAuth MCP Server

Where should I place the OAuth keys file?

Place gcp-oauth.keys.json either in the current directory or in ~/.calendar-mcp/. The authentication process copies it to the global location if found locally.

What should I do if port 3000 is already in use during authentication?

Free port 3000 by stopping the process using it before running the authentication command.

What formats are accepted for the OAuth credentials file?

The file must contain either web (for Web application credentials) or installed (for Desktop app) credentials. For web applications, add http://localhost:3000/oauth2callback to the authorized redirect URIs.

Comments

More Productivity MCP servers