Cronofy MCP by usefulapi
MCP server for Cronofy — read calendars, events and free/busy, and create, update or delete events.
- 1.11.1
- Version
- remote
- Transport
- 8
- Tools
Security review
Review passedReviewed 1d ago.
- tools: 8 tools scanned
- metadata: scanned
No findings.
Tools (8)
cronofy_get_account
Get the authenticated Cronofy account's details (id, email, name, default tzid, locale). API: GET /v1/account.
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_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_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}/events.
cronofy_delete_event
Deletes an event (by your event_id) from a real connected calendar. Destructive. API: DELETE /v1/calendars/{calendar_id}/events.