Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Google Calendar

by pulsemcpversion 0.0.13i★ –iRuns on your computer
Registry namecom.pulsemcp/google-calendar

Install

Overview

Description from the maker (original English)

MCP server for Google Calendar integration with service account support and domain-wide delegation.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Docs, sheets & office work
  • You need to fill in: GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL, GCAL_SERVICE_ACCOUNT_PRIVATE_KEY, GCAL_IMPERSONATE_EMAIL

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL, GCAL_SERVICE_ACCOUNT_PRIVATE_KEY, GCAL_IMPERSONATE_EMAIL, ENABLED_TOOLGROUPS

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "google-calendar": {
      "command": "npx",
      "args": [
        "-y",
        "google-calendar-workspace-mcp-server"
      ],
      "env": {
        "GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL": "your-value",
        "GCAL_SERVICE_ACCOUNT_PRIVATE_KEY": "your-value",
        "GCAL_IMPERSONATE_EMAIL": "your-value",
        "ENABLED_TOOLGROUPS": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add google-calendar --env GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL=your-value --env GCAL_SERVICE_ACCOUNT_PRIVATE_KEY=your-value --env GCAL_IMPERSONATE_EMAIL=your-value --env ENABLED_TOOLGROUPS=your-value -- npx -y google-calendar-workspace-mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "google-calendar": {
      "command": "npx",
      "args": [
        "-y",
        "google-calendar-workspace-mcp-server"
      ],
      "env": {
        "GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL": "your-value",
        "GCAL_SERVICE_ACCOUNT_PRIVATE_KEY": "your-value",
        "GCAL_IMPERSONATE_EMAIL": "your-value",
        "ENABLED_TOOLGROUPS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "google-calendar": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "google-calendar-workspace-mcp-server"
      ],
      "env": {
        "GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL": "your-value",
        "GCAL_SERVICE_ACCOUNT_PRIVATE_KEY": "your-value",
        "GCAL_IMPERSONATE_EMAIL": "your-value",
        "ENABLED_TOOLGROUPS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL required env
    Service account email address from Google Cloud Console.
  • GCAL_SERVICE_ACCOUNT_PRIVATE_KEY secret required env
    Service account private key in PEM format from Google Cloud Console.
  • GCAL_IMPERSONATE_EMAIL required env
    Email address of the user whose calendar to access via domain-wide delegation.
  • ENABLED_TOOLGROUPS env
    Comma-separated list of tool groups to enable (readonly or readwrite).

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain pulsemcp.com (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Docs, sheets & office worki

  • More stars than 0% of the other 2194 servers in this category
  • Published to the registry more recently than 14% of the other 2194 servers in this category
  • Basic checks equal to or better than 100% of the other 2194 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Google Calendar safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL, GCAL_SERVICE_ACCOUNT_PRIVATE_KEY, GCAL_IMPERSONATE_EMAIL

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.0.13) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Agent-Native Google Calendar - manage events, sync, and public booking

Runs in the cloud★ 7,620MITUpdated 2 months ago
Install

Excel MCP Server

by haris-musa

Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.

Runs on your computer★ 4,276MITUpdated 6 days ago
Install

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

Runs on your computer★ 847MITUpdated 4 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Google Calendar Workspace MCP Server

An MCP (Model Context Protocol) server for Google Calendar integration using service account authentication with domain-wide delegation. This server enables AI assistants to interact with Google Calendar to list events, create events, manage calendars, and query availability.

Features

  • List Events: View calendar events within a specified time range with filtering
  • Get Event Details: Retrieve complete information about specific events
  • Create Events: Create new calendar events with attendees, location, and descriptions
  • Update Events: Modify existing events (PATCH semantics - only provided fields are updated)
  • Delete Events: Remove events with optional notification to attendees
  • List Calendars: Discover available calendars
  • Query Free/Busy: Check availability and find busy time slots

Prerequisites

  1. Google Cloud Project with Calendar API enabled
  2. Service Account with domain-wide delegation
  3. Google Workspace Admin access to grant calendar permissions

Setup

1. Create a Google Cloud Service Account
  1. Go to Google Cloud Console
  2. Create or select a project
  3. Enable the Google Calendar API:
  • Navigate to "APIs & Services" > "Library"
  • Search for "Google Calendar API"
  • Click "Enable"
  1. Create a service account:
  • Navigate to "IAM & Admin" > "Service Accounts"
  • Click "Create Service Account"
  • Provide a name and description
  • Click "Create and Continue"
  • Skip granting roles (not needed for domain-wide delegation)
  • Click "Done"
  1. Create a key for the service account:
  • Click on the created service account
  • Go to "Keys" tab
  • Click "Add Key" > "Create new key"
  • Select "JSON" format
  • Download the key file
  1. Note the service account's Client ID (found in the service account details)
2. Enable Domain-Wide Delegation
  1. In the service account details, click "Show domain-wide delegation"
  2. Check "Enable Google Workspace Domain-wide Delegation"
  3. Save the changes
  4. Note the Client ID (you'll need this for the next step)
3. Grant Calendar Permissions in Google Workspace Admin
  1. Go to Google Workspace Admin Console
  2. Navigate to "Security" > "Access and data control" > "API Controls"
  3. Click "Manage Domain Wide Delegation"
  4. Click "Add new"
  5. Enter the service account's Client ID
  6. In the "OAuth Scopes" field, add:
   https://www.googleapis.com/auth/calendar
  1. Click "Authorize"
4. Configure Environment Variables

Extract the following from your downloaded JSON key file:

  • client_email: The service account email
  • private_key: The private key (including [PopNx MCP ตัดค่าที่หน้าตาเหมือนกุญแจออก])

Set these environment variables:

export GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL="your-service-account@your-project.iam.gserviceaccount.com"

export GCAL_SERVICE_ACCOUNT_PRIVATE_KEY="[PopNx MCP ตัดค่าที่หน้าตาเหมือนกุญแจออก]" export GCAL_IMPERSONATE_EMAIL="user@yourdomain.com"

Note: GCAL_IMPERSONATE_EMAIL should be the email address of the user whose calendar you want to access.

Installation

Using NPX (Recommended)
npx google-calendar-workspace-mcp-server
Using NPM
npm install -g google-calendar-workspace-mcp-server

google-calendar-workspace-mcp-server

Usage with Claude Desktop

Add this configuration to your Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{

"mcpServers": { "google-calendar": { "command": "npx", "args": ["google-calendar-workspace-mcp-server"], "env": { "GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL": "your-service-account@your-project.iam.gserviceaccount.com", "GCAL_SERVICE_ACCOUNT_PRIVATE_KEY": "[PopNx MCP ตัดค่าที่หน้าตาเหมือนกุญแจออก]", "GCAL_IMPERSONATE_EMAIL": "user@yourdomain.com" } } } }

Tool Groups

By default, all tools are enabled (read + write access). You can restrict the server to read-only operations by setting the ENABLED_TOOLGROUPS environment variable:

{

"mcpServers": { "google-calendar": { "command": "npx", "args": ["google-calendar-workspace-mcp-server"], "env": { "GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL": "...", "GCAL_SERVICE_ACCOUNT_PRIVATE_KEY": "...", "GCAL_IMPERSONATE_EMAIL": "...", "ENABLED_TOOLGROUPS": "readonly" } } } }

Available tool groups:

GroupTools Included
readwriteAll 7 tools (read + write) - included by default
readonlyRead-only tools: list_calendar_events, get_calendar_event, list_calendars, query_calendar_freebusy

When using only readonly, the write tools (create_calendar_event, update_calendar_event, delete_calendar_event) are not available.

Available Tools

list_calendar_events

Lists events from a calendar within an optional time range.

Parameters:

  • calendar_id (optional): Calendar ID (default: "primary")
  • time_min (optional): Start time in RFC3339 format
  • time_max (optional): End time in RFC3339 format
  • max_results (optional): Maximum events to return (default: 10, max: 250)
  • query (optional): Free text search query
  • single_events (optional): Expand recurring events (default: true)
  • order_by (optional): "startTime" or "updated"

Example:

List my events for the next week
get_calendar_event

Retrieves detailed information about a specific event.

Parameters:

  • event_id (required): The event ID
  • calendar_id (optional): Calendar ID (default: "primary")

Example:

Get details for event ID abc123
create_calendar_event

Creates a new calendar event.

Parameters:

  • summary (required): Event title
  • start_datetime OR start_date (required): Event start time
  • end_datetime OR end_date (required): Event end time
  • description (optional): Event description
  • location (optional): Event location
  • attendees (optional): Array of email addresses
  • calendar_id (optional): Calendar ID (default: "primary")

Example:

Create a meeting tomorrow at 2pm for 1 hour titled "Team Sync"
update_calendar_event

Updates an existing calendar event. Uses PATCH semantics - only the fields you provide will be updated; other fields remain unchanged.

Parameters:

  • event_id (required): The event ID to update
  • calendar_id (optional): Calendar ID (default: "primary")
  • summary (optional): New event title
  • description (optional): New event description
  • location (optional): New event location
  • start_datetime OR start_date (optional): New start time
  • end_datetime OR end_date (optional): New end time
  • attendees (optional): Updated array of attendee email addresses
  • send_updates (optional): "all", "externalOnly", or "none" - whether to send update notifications

Example:

Update event abc123 to change the title to "Team Standup"
delete_calendar_event

Deletes a calendar event.

Parameters:

  • event_id (required): The event ID to delete
  • calendar_id (optional): Calendar ID (default: "primary")
  • send_updates (optional): "all", "externalOnly", or "none" - whether to send cancellation notifications

Example:

Delete event abc123
list_calendars

Lists all calendars available to the authenticated user.

Parameters:

  • max_results (optional): Maximum calendars to return (default: 50, max: 250)

Example:

Show all my calendars
query_calendar_freebusy

Queries availability information for calendars.

Parameters:

  • time_min (required): Start time in RFC3339 format
  • time_max (required): End time in RFC3339 format
  • calendar_ids (required): Array of calendar IDs to check
  • timezone (optional): Time zone for the query

Example:

Check if I'm free tomorrow between 2pm and 4pm

Development

# Install dependencies

npm run install-all

Build the project

npm run build

Run in development mode

npm run dev

Run tests

npm test

Run integration tests

npm run test:integration

Run all tests

npm run test:all

Security Considerations

  • Private Key Security: Never commit your service account private key to version control
  • Least Privilege: Only grant the minimum required OAuth scopes
  • Key Rotation: Regularly rotate service account keys
  • Access Logging: Monitor service account usage in Google Cloud Console

Troubleshooting

Authentication Failed
  • Verify service account credentials are correct
  • Ensure domain-wide delegation is enabled
  • Check that the correct OAuth scope is authorized in Admin Console
  • Verify the impersonate email address is correct
Permission Denied
  • Ensure the calendar scope (https://www.googleapis.com/auth/calendar) is granted in Google Workspace Admin Console
  • Verify the impersonated user has access to the calendar
Calendar Not Found
  • Check that the calendar ID is correct
  • Verify the impersonated user has access to the calendar
  • Use list_calendars to discover available calendar IDs

License

MIT

Contributing

See CONTRIBUTING.md for guidelines.

Ask PopNx