Loading...
This MCP server allows Claude to interact with Google Calendar, enabling users to manage events, authenticate, and switch accounts via natural language.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
This MCP server allows Claude to interact with Google Calendar, enabling users to manage events, authenticate, and switch accounts via natural language.
This MCP server offers moderate safety due to its OAuth2 authentication and token encryption. However, the ability to create, update, and delete calendar events introduces risks if the server is misconfigured or credentials are compromised. It is safe when properly configured with strong environment variable management and used within the intended Claude Desktop environment. It is risky if exposed to unauthorized access or used with weak credentials.
Performance depends on the Google Calendar API's responsiveness. Large requests for events may take longer to process. Consider optimizing queries by specifying appropriate time ranges.
Using this server will incur costs associated with Google Calendar API usage, which is generally based on the number of requests made. Be mindful of the number of API calls, especially when automating tasks.
npx @takumi0706/google-calendar-mcp@1.0.7{
"mcpServers": {
"google-calendar": {
"command": "npx",
"args": [
"-y",
"@takumi0706/google-calendar-mcp"
],
"env": {
"GOOGLE_CLIENT_ID": "your_client_id",
"GOOGLE_CLIENT_SECRET": "your_client_secret",
"GOOGLE_REDIRECT_URI": "http://localhost:4153/oauth2callback"
}
}
}
}AUTH_PORTgetEventsRetrieves calendar events based on specified criteria like date range and maximum results.
Read-only operation, no modification of calendar data.
createEventCreates a new event in the user's Google Calendar.
Adds new data to the calendar, but doesn't modify existing events without explicit instruction.
updateEventModifies an existing event in the user's Google Calendar.
Changes existing calendar data, potentially leading to data loss or corruption if used incorrectly.
deleteEventDeletes an event from the user's Google Calendar.
Destructive operation that permanently removes calendar data.
authenticateRe-authenticates with Google Calendar, allowing switching between accounts.
Re-establishes authentication, but does not directly modify calendar data.
OAuth
hybrid
This MCP server offers moderate safety due to its OAuth2 authentication and token encryption. However, the ability to create, update, and delete calendar events introduces risks if the server is misconfigured or credentials are compromised. It is safe when properly configured with strong environment variable management and used within the intended Claude Desktop environment. It is risky if exposed to unauthorized access or used with weak credentials.
The server allows full read/write access to the user's Google Calendar, so caution is advised when granting autonomy. There is no dry-run mode or rollback support, making careful prompt engineering essential.
Production Tip
Ensure proper environment variable configuration and secure credential management for production use.
Use the `authenticate` tool to re-authenticate with the desired Google account.
Immediately revoke the compromised credentials in the Google Cloud Console and generate new ones.
Yes, you can specify the `calendarId` parameter to interact with different calendars. If omitted, it defaults to the primary calendar.
Check the server logs for error messages and consult the Google Calendar API documentation for troubleshooting.
Yes, version 1.0.5 and later support recurring events through the `recurrence` parameter in `createEvent` and `updateEvent`.
The server uses OAuth2 for authentication, AES-256-GCM for token encryption, and PKCE for enhanced security.
Set the `USE_MANUAL_AUTH` environment variable to `true`.