Skip to main content
Glama

MCP server for Google Calendar

Credentials

The credentials.json file is needed to authenticate againts the Google services. To generate the file, the following steps must be performed:

  1. Visit the Google Cloud Platform website

  2. Crete a new project (or use an existant one)

  3. Into the APIs & Services section, enable the Google Calendar API service

  4. Go to Credentials and generate a new credential as Service Account

  5. Copy the service account's email generated. It will be needed to share the calendar with it

  6. After the credential is created, a JSON file will be able to download. Place it into the root of this project and name it as credentials.json

Related MCP server: Google Calendar MCP Server

Calendar sharing

To interact with a calendar, it needs to be shared with the service account previously created to access it following these steps:

  1. Visit the Google Calendar website

  2. Into the sidebar, place on the target calendar, click the three dots (...) and then go to Settings and sharing

  3. Go the Shared with and add the email address for the service account copied previously when the credential was created

  4. Go to Integrate calendar and copy the Calendar ID value

Inspector

While developing, you can use the inspector to debug the server. To do this:

npm run inspector

Build MCP Server

Before adding the MCP server to the configuration file, you need to build it. The build process will create a Docker image that can be run in WSL.

npm run build
docker build -t mcpserver-googlecalendar .

Add MCP Server

To add the MCP server, add to the configuration file and paste the Calendar ID copied previously:

{
  "mcpServers": {
    "google-calendar": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "GOOGLE_CALENDAR_ID",
        "mcpserver-googlecalendar"
      ],
      "env": {
        "GOOGLE_CALENDAR_ID": "[CALENDAR_ID_HERE]"
      }
    }
  }
}

Available Tools

1 tool
get_calendar_eventsC

Get calendar events from Google Calendar. By default, it retrieves events from the last 3 months.

Inputs: startDate, endDate.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.

    Naming Consistency5/5

    A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns or conventions.

    Tool Count2/5

    One tool is too few for a Google Calendar server, as it severely limits functionality. A calendar domain typically requires CRUD operations (e.g., create_event, update_event, delete_event) and other features like listing calendars or managing attendees, making this server incomplete and impractical for most agent workflows.

    Completeness1/5

    The server is severely incomplete for a Google Calendar domain. It only provides read access to events, lacking essential operations such as creating, updating, or deleting events, managing calendars, or handling recurring events, which will cause frequent agent failures in typical calendar-related tasks.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides read-only access to the Google Calendar API v3. It enables users to list calendars, search for events, check free/busy availability, and retrieve calendar settings.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides integration with Google Calendar, allowing users to list calendars and manage events. It enables searching, creating, and modifying calendar entries through tools designed for the Model Context Protocol.
      -