mcp-google-calendar

This MCP server provides calendar management capabilities via the MCP protocol. It exposes tools to create, list, update, and delete events in a Google Calendar. When run through a compatible MCP host or Dive Desktop, you can interact with your calendar directly from the MCP layer, enabling automation and integration with other MCP-enabled services.

To use it, install the server via the MCP host interface or run it through the npm/npx approach described in the installation guide. The server expects Google Cloud credentials and a target calendar configured in the environment variables. Once running, you can issue commands through your MCP client or through the Dive Desktop integration to create events, retrieve lists of events, modify details of existing events, or remove events from the specified Google Calendar. The server handles authentication using a Google service account credentials JSON provided via GOOGLE_CREDENTIALS_PATH, and you can specify the target calendar and time zone using the respective environment variables.

In Dive Desktop, you add an MCP Server and paste the provided JSON configuration. After saving, the calendar server becomes available to all connected MCP clients, allowing workflows that depend on calendar data to be orchestrated alongside other MCP resources.

Prerequisites:

• Node.js and npm installed on your system
• Access to run npm or npx commands

Installation steps:

1. Install the MCP Google Calendar server globally using npm (as shown in the README):

npm install -g @cablate/mcp-google-calendar

2. Prepare Google service account credentials as described (JSON file) and set the required environment variables when starting or configuring the MCP host:

• GOOGLE_CALENDAR_ID: your Google Calendar ID
• GOOGLE_TIME_ZONE: your preferred time zone (e.g., America/Los_Angeles)
• GOOGLE_CREDENTIALS_PATH: path to the downloaded credentials.json

3. Start the MCP server via your MCP host (e.g., using Dive Desktop integration) or by running through npx as shown in the usage example:

mcp-google-calendar

4. If using Dive Desktop, add the MCP Server and paste the configuration snippet from the README to register the server with the host.

Tips and notes:

• Ensure the Google service account has calendar access permissions for the target calendar.
• Keep credentials.json secure; do not commit it to source control.
• When using Dive Desktop, the calendar configuration should be kept under the mcpServers.calendar entry with enabled set to true.
• If you encounter authentication errors, verify that GOOGLE_CREDENTIALS_PATH points to a valid JSON file and that the service account has proper calendar permissions.
• The time zone (GOOGLE_TIME_ZONE) should align with the events you manage to avoid off-by-time issues.
• This MCP server focuses on calendar event CRUD operations and does not implement synchronization with other calendar sources unless extended in your MCP setup.
• If you need to support multiple calendars, consider adding additional entries with separate IDs and environment configurations.