Calendar AutoAuth MCP Server
by gongrzhe
A Model Context Protocol (MCP) server for Google Calendar integration in Cluade Desktop with auto authentication support. This server enables AI assistants to manage Google Calendar events through natural language interactions.
Last updated: N/A
What is Calendar AutoAuth MCP Server?
This is a Model Context Protocol (MCP) server designed to facilitate Google Calendar integration within the Claude Desktop environment. It provides auto-authentication capabilities, enabling AI assistants to seamlessly manage calendar events through natural language commands.
How to use Calendar AutoAuth MCP Server?
The server can be installed via Smithery or Docker. After installation, you need to authenticate with Google Calendar by creating a Google Cloud Project, enabling the Google Calendar API, and creating OAuth 2.0 credentials. Once authenticated, you can configure Claude Desktop to use the server for managing calendar events.
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
Full integration with Google Calendar API
Simple OAuth2 authentication flow with auto browser launch
Support for both Desktop and Web application credentials
Global credential storage for convenience
Use cases of Calendar AutoAuth MCP Server
Scheduling meetings and appointments through natural language commands
Retrieving event details using AI assistants
Updating event information via voice or text input
Deleting events using natural language
Listing events within a specific timeframe using AI assistants
FAQ from Calendar AutoAuth MCP Server
Where should I place the gcp-oauth.keys.json file?
Where should I place the gcp-oauth.keys.json file?
Place it either in your current directory or in the ~/.calendar-mcp/ directory.
What do I do if I get an 'Invalid Credentials Format' error?
What do I do if I get an 'Invalid Credentials Format' error?
Ensure your OAuth keys file contains either 'web' or 'installed' credentials. For web applications, verify the redirect URI is correctly configured.
What if port 3000 is already in use?
What if port 3000 is already in use?
Free up port 3000 before running the authentication process. You can find and stop the process using that port.
How are my OAuth credentials stored?
How are my OAuth credentials stored?
OAuth credentials are stored securely in your local environment (~/.calendar-mcp/).
What redirect URI should I use for Web application credentials?
What redirect URI should I use for Web application credentials?
Make sure to add http://localhost:3000/oauth2callback to your authorized redirect URIs.