# Google_calendar (npm · @pipeworx/mcp-google_calendar)

Google Calendar MCP Pack

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-google-calendar/google-calendar-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-google-calendar/google-calendar-mcp)
- npm · `@pipeworx/mcp-google_calendar`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-google-calendar/pipeworx-mcp-google-calendar.md), [page](https://verifymcp.io/servers/pipeworx-io-google-calendar/pipeworx-mcp-google-calendar)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-google_calendar`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-google_calendar).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 662 tokens (~132/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Google_calendar MCP server?

Google_calendar runs locally as an npm package, launched with npx -y @pipeworx/mcp-google_calendar. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-google-calendar -- npx -y @pipeworx/mcp-google_calendar
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-google-calendar": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-google_calendar"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-google-calendar": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-google_calendar"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-google-calendar -- npx -y @pipeworx/mcp-google_calendar
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-google-calendar": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-google_calendar"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-google-calendar --command npx --arg -y --arg @pipeworx/mcp-google_calendar
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-google-calendar:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-google_calendar"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-google-calendar": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-google_calendar"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-google-calendar -t stdio -c npx -a -y @pipeworx/mcp-google_calendar
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-google-calendar": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-google_calendar"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 82, +26)

- [security improvement] Known CVEs: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-11-02 (score 56, −25)

- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [functional regression] Dependency health: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-31 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 80)

First indexed and scored.

## MCP tools (5)

### `gcal_list_events` (~166 tokens)

List calendar events with optional date filtering. Returns event summaries, start/end times, attendees, and locations. Use to view upcoming or past events.

Input parameters:

- `calendar_id` (string): Calendar ID (default: "primary" for the user's main calendar)
- `max_results` (number): Maximum number of events to return (default 10, max 250)
- `order_by` (string): Sort order (default: startTime). startTime requires singleEvents=true.
- `time_max` (string): Upper bound (exclusive) for event end time as RFC3339 timestamp
- `time_min` (string): Lower bound (inclusive) for event start time as RFC3339 timestamp (e.g., "2024-01-01T00:00:00Z")

### `gcal_get_event` (~75 tokens)

Get full details of a specific event by ID (e.g., "event_12345"). Returns summary, description, times, attendees, location, and video conferencing links.

Input parameters:

- `calendar_id` (string): Calendar ID (default: "primary")
- `event_id` (string, required): The ID of the event to retrieve

### `gcal_create_event` (~195 tokens)

Create a new calendar event with summary, start/end times, optional description, location, and attendee emails. Returns the created event ID.

Input parameters:

- `attendees` (array): List of attendee email addresses
- `calendar_id` (string): Calendar ID (default: "primary")
- `description` (string): Description or notes for the event
- `end` (string, required): End time as RFC3339 timestamp or date for all-day events
- `location` (string): Location of the event
- `start` (string, required): Start time as RFC3339 timestamp (e.g., "2024-06-15T10:00:00-07:00") or date for all-day events ("2024-06-15")
- `summary` (string, required): Title of the event
- `time_zone` (string): Time zone (e.g., "America/Los_Angeles"). Defaults to calendar's time zone.

### `gcal_list_calendars` (~43 tokens)

List all accessible calendars. Returns calendar IDs, names, time zones, and your access level for each. Use to identify which calendar to query or modify.

### `gcal_search_events` (~131 tokens)

Search events by keyword across summaries, descriptions, locations, and attendees. Returns matching event details and times. Use to find events by topic or participant.

Input parameters:

- `calendar_id` (string): Calendar ID (default: "primary")
- `max_results` (number): Maximum number of events to return (default 10, max 250)
- `query` (string, required): Free-text search query to match against event fields
- `time_max` (string): Upper bound for event end time as RFC3339 timestamp
- `time_min` (string): Lower bound for event start time as RFC3339 timestamp

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-google-calendar/pipeworx-mcp-google-calendar#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 82
- 2026-11-02: 56
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

### What is the Google_calendar MCP server?

Google_calendar is an MCP server listed in the public MCP registry as io.github.pipeworx-io/google_calendar. Google Calendar MCP Pack. This page covers its npm package (@pipeworx/mcp-google_calendar).

### Is the Google_calendar MCP server safe to use?

Google_calendar scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Google_calendar MCP server expose?

Google_calendar exposes 5 tools: gcal_list_events, gcal_get_event, gcal_create_event, gcal_list_calendars, gcal_search_events. Their descriptions and schemas cost roughly 610 tokens of context every time the server is loaded.

### Is the Google_calendar MCP server still maintained?

Google_calendar is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Google_calendar MCP server under?

Google_calendar declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-google_calendar
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-google_calendar
- Repository: https://github.com/pipeworx-io/mcp-google_calendar
- Website: https://pipeworx.io/packs/google_calendar
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-google-calendar/pipeworx-mcp-google-calendar.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-google-calendar/pipeworx-mcp-google-calendar.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-google-calendar/pipeworx-mcp-google-calendar