# Usefulapi Cronofy MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.usefulapi%2Fcronofy
Registry id: `mcp-registry/io.usefulapi/cronofy`
Status: auth-required (checked 2026-10-27T02:12:12.090Z)

## Verdict

Usefulapi Cronofy MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 63 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (96/100) across 8 tools, costing an agent about 1,315 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 63 ms | 88% of MCP servers |
| p95 handshake latency | 374 ms | — |
| Checks in 30 days | 213 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 8 | — |
| Tool-list size for an agent | ~1,315 tokens | 61% of MCP servers |
| Days observed | 28 | — |

## Install

```json
{
  "mcpServers": {
    "usefulapi-cronofy-mcp-server": {
      "type": "http",
      "url": "https://cronofy.usefulapi.io/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http usefulapi-cronofy-mcp-server https://cronofy.usefulapi.io/mcp
```

## Tools (8)

- `cronofy_delete_event`: Deletes an event (by your event_id) from a real connected calendar. Destructive. API: DELETE /v1/calendars/{calendar_id}/events.
- `cronofy_get_account`: Get the authenticated Cronofy account's details (id, email, name, default tzid, locale). API: GET /v1/account.
- `cronofy_get_free_busy`: Read free/busy information across the account's calendars over a time window. Returns { pages, free_busy }. API: GET /v1/free_busy.
- `cronofy_get_userinfo`: Get the OpenID-style profile of the authenticated user (sub, email, Cronofy profile info). API: GET /v1/userinfo.
- `cronofy_list_calendars`: List all calendars the authenticated account can see (id, name, profile, readonly, primary). API: GET /v1/calendars.
- `cronofy_list_profiles`: List the connected calendar accounts/profiles (e.g. Google, Office 365) linked to this Cronofy account. API: GET /v1/profiles.
- `cronofy_read_events`: Read events across the account's calendars over a time window. Returns { pages, events }. API: GET /v1/events.
- `cronofy_upsert_event`: Creates or updates an event on a REAL connected calendar (upsert by event_id). This writes to the user's actual calendar. API: POST /v1/calendars/{calendar_id}/

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.