- Home
- MCP servers
- MCP Google Calendar Server
MCP Google Calendar Server
- javascript
3
GitHub Stars
javascript
Language
5 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"tobedoit-gcalendar-mcp": {
"command": "npx",
"args": [
"-y",
"@tobedoit/google-calendar-mcp"
],
"env": {
"GOOGLE_CLIENT_ID": "YOUR_CLIENT_ID",
"GOOGLE_CLIENT_SECRET": "YOUR_CLIENT_SECRET",
"GOOGLE_REFRESH_TOKEN": "YOUR_REFRESH_TOKEN"
}
}
}
}This MCP server enables AI assistants to create and manage Google Calendar events by exposing a standardized, programmable interface. You can compose events with titles, descriptions, times, attendees, and alerts, all through the MCP communication model, making calendar management seamless from your assistant workflows.
How to use
You interact with the Google Calendar MCP server through an MCP client. Use the client to create events by providing the required event details such as title, start and end times, description, and attendees. You can also set alerts and manage attendees to invite others to the event. The server handles authentication with Google Calendar via OAuth2 and communicates with Google Calendar API to create, update, or fetch events. Use the MCP client to request actions like creating an event, updating an existing event, or listing upcoming events, and receive structured results that reflect the calendar state.
Practical usage patterns include: creating a new event with a specific time window and attendees, setting a reminder for attendees, updating event details after a meeting is scheduled, and querying upcoming events to keep your assistant’s context up to date. Your client should provide the necessary event fields and handle responses from the MCP server, including any OAuth-related authorization status or error messages from Google Calendar.
How to install
Prerequisites you need before starting:
-
Node.js v18 or later
-
Google Cloud Console project with Calendar API enabled
-
OAuth2 credentials (Client ID and Client Secret)
Follow these steps to configure and run the MCP server in your environment.
{
"mcpServers": {
"zmes-calendar": {
"command": "npx",
"args": [
"-y",
"@tobedoit/google-calendar-mcp"
],
"env": {
"GOOGLE_CLIENT_ID": "your_google_client_id",
"GOOGLE_CLIENT_SECRET": "your_google_client_secret",
"GOOGLE_REFRESH_TOKEN": "your_google_refresh_token"
}
}
}
}
Additional setup notes
The configuration snippet shown above is what you paste into yourClaude desktop or runner to register the MCP server under a unique key. Replace the placeholders with your actual Google OAuth credentials and refresh token before starting the server. Ensure your environment variables are securely stored and not exposed in logs.
Security and troubleshooting
-
Keep OAuth credentials confidential. Rotate client secrets as recommended by Google Cloud, and revoke tokens if you suspect compromise.
-
Enable debug logging during troubleshooting to capture detailed information about the MCP protocol interactions and Google Calendar API calls.
Notes and examples
This server supports creating events with essential fields and adding attendees. You can extend usage by combining MCP client actions, such as creating an event and then immediately querying upcoming events to confirm the creation.
Available tools
create_event
Create a Google Calendar event with title, description, start/end times, and optional alert.
add_attendee
Add one or more attendees to an existing event by email.
authenticate_oauth
Handle OAuth2 authentication flow to obtain access tokens for Google Calendar.
debug_logging
Log MCP protocol interactions and API calls for troubleshooting.