# Calendly (npm · @pipeworx/mcp-calendly)

Calendly MCP Pack — wraps the Calendly API v2 for scheduling data.

- Trust score: 83/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-calendly`
- 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-04.

- **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-calendly).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 697 tokens (~139/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**: 20/100
  - Stability observed for 6 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 Calendly MCP server?

Calendly runs locally as an npm package, launched with npx -y @pipeworx/mcp-calendly. 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-calendly -- npx -y @pipeworx/mcp-calendly
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-calendly -- npx -y @pipeworx/mcp-calendly
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-calendly --command npx --arg -y --arg @pipeworx/mcp-calendly
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-03 (score 83, +1)

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

### 2026-11-01 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 66, −15)

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

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

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 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)

### `current_user` (~67 tokens)

Get the current Calendly user for the supplied token. Returns the user URI and organization URI — call this FIRST, since list_scheduled_events and list_event_types require a user or organization URI.

Input parameters:

- `_apiKey` (string, required): Calendly personal access token (sent as Bearer token)

### `list_scheduled_events` (~210 tokens)

List scheduled meetings (events). Requires a user URI OR an organization URI (get them from current_user). Filter by status, time window, and paginate. Returns event URIs/UUIDs, names, start/end times, status, and locations.

Input parameters:

- `_apiKey` (string, required): Calendly personal access token (sent as Bearer token)
- `count` (number): Number of results per page (default 20, max 100).
- `max_start_time` (string): ISO 8601 timestamp; only events starting at/before this time.
- `min_start_time` (string): ISO 8601 timestamp; only events starting at/after this time.
- `organization` (string): Organization URI (from current_user). Provide user OR organization.
- `page_token` (string): Token from a previous response for the next page.
- `status` (string): Filter by event status.
- `user` (string): User URI (from current_user). Provide user OR organization.

### `get_event` (~80 tokens)

Get a single scheduled event by its UUID (the last path segment of an event URI). Returns full event details including name, times, status, location, and event membership.

Input parameters:

- `_apiKey` (string, required): Calendly personal access token (sent as Bearer token)
- `uuid` (string, required): Scheduled event UUID (last segment of the event URI).

### `list_invitees` (~129 tokens)

List the invitees of a scheduled event by event UUID. Returns invitee names, emails, status (active/canceled), timezone, and answers to booking questions.

Input parameters:

- `_apiKey` (string, required): Calendly personal access token (sent as Bearer token)
- `count` (number): Number of results per page (default 20, max 100).
- `page_token` (string): Token from a previous response for the next page.
- `status` (string): Filter invitees by status.
- `uuid` (string, required): Scheduled event UUID (last segment of the event URI).

### `list_event_types` (~158 tokens)

List bookable event types (meeting templates). Requires a user URI OR an organization URI (get them from current_user). Returns event type URIs, names, durations, scheduling URLs, and active state.

Input parameters:

- `_apiKey` (string, required): Calendly personal access token (sent as Bearer token)
- `active` (boolean): If true, only return active event types.
- `count` (number): Number of results per page (default 20, max 100).
- `organization` (string): Organization URI (from current_user). Provide user OR organization.
- `page_token` (string): Token from a previous response for the next page.
- `user` (string): User URI (from current_user). Provide user OR organization.

## Diagnostics

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

## Score history

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

## Common questions

### What is the Calendly MCP server?

Calendly is an MCP server listed in the public MCP registry as io.github.pipeworx-io/calendly. Calendly MCP Pack, wraps the Calendly API v2 for scheduling data. This page covers its npm package (@pipeworx/mcp-calendly).

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

Calendly scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 Calendly MCP server expose?

Calendly exposes 5 tools: current_user, list_scheduled_events, get_event, list_invitees, list_event_types. Their descriptions and schemas cost roughly 644 tokens of context every time the server is loaded.

### Is the Calendly MCP server still maintained?

Calendly is still listed as active in the MCP registry. We last reached this channel on 4 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 Calendly MCP server under?

Calendly 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-calendly
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-calendly
- Repository: https://github.com/pipeworx-io/mcp-calendly
- Website: https://pipeworx.io/packs/calendly
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-calendly/pipeworx-mcp-calendly.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-calendly/pipeworx-mcp-calendly.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-calendly/pipeworx-mcp-calendly