Cronofy MCP by usefulapi
Server Details
MCP server for Cronofy — read calendars, events and free/busy, and create, update or delete events.
- Status
- Healthy
- Uptime
- 70.7% over 54 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
TDQS
Scored across 8 tools
Each tool maps to a distinct resource/action, but get_account and get_userinfo are close enough to cause occasional misclassification. free_busy vs read_events are similar reads over calendars but clearly differentiated by availability vs event details.
All names share the cronofy_ prefix and verb_noun snake_case pattern, but retrieval verbs are mixed (get_account, list_calendars, read_events). This is a minor consistency break rather than a chaotic scheme.
Eight tools is well-scoped for a calendar connectivity server. Each tool covers a meaningful operation without redundancy or bloat.
The core lifecycle is covered: list calendars, read/upsert/delete events, free/busy, plus account and profile info. Minor gaps like direct single-event lookup or calendar management are workaround-able via read_events.
Available Tools
8 toolscronofy_delete_eventDelete eventDestructiveInspect
Deletes an event (by your event_id) from a real connected calendar. Destructive. API: DELETE /v1/calendars/{calendar_id}/events.
| Name | Required | Description | Default |
|---|---|---|---|
| event_id | Yes | YOUR event_id for the event to delete (sent in the JSON body). | |
| calendar_id | Yes | Calendar id the event lives on. |
cronofy_get_accountGet accountRead-onlyInspect
Get the authenticated Cronofy account's details (id, email, name, default tzid, locale). API: GET /v1/account.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
cronofy_get_free_busyGet free/busyRead-onlyInspect
Read free/busy information across the account's calendars over a time window. Returns { pages, free_busy }. API: GET /v1/free_busy.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | End of the window — date (yyyy-mm-dd) or ISO 8601 datetime. | |
| from | No | Start of the window — date (yyyy-mm-dd) or ISO 8601 datetime. | |
| tzid | Yes | REQUIRED time zone id for the response, e.g. "Etc/UTC". | |
| calendar_ids | No | Restrict to these calendar ids (sent as repeated calendar_ids[] params). | |
| include_managed | No | Include events created via the Cronofy API. Default false. |
cronofy_get_userinfoGet userinfoRead-onlyInspect
Get the OpenID-style profile of the authenticated user (sub, email, Cronofy profile info). API: GET /v1/userinfo.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
cronofy_list_calendarsList calendarsRead-onlyInspect
List all calendars the authenticated account can see (id, name, profile, readonly, primary). API: GET /v1/calendars.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
cronofy_list_profilesList profilesRead-onlyInspect
List the connected calendar accounts/profiles (e.g. Google, Office 365) linked to this Cronofy account. API: GET /v1/profiles.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
cronofy_read_eventsRead eventsRead-onlyInspect
Read events across the account's calendars over a time window. Returns { pages, events }. API: GET /v1/events.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | End of the window — date (yyyy-mm-dd) or ISO 8601 datetime. | |
| from | No | Start of the window — date (yyyy-mm-dd) or ISO 8601 datetime. | |
| tzid | Yes | REQUIRED time zone id for the response, e.g. "Etc/UTC" or "America/New_York". | |
| calendar_ids | No | Restrict to these calendar ids (sent as repeated calendar_ids[] params). | |
| only_managed | No | Return only events created via the Cronofy API. Default false. | |
| last_modified | No | Only events modified since this ISO 8601 datetime. | |
| include_deleted | No | Include deleted events. Default false. | |
| include_managed | No | Include events created via the Cronofy API. Default false. |
cronofy_upsert_eventCreate or update eventDestructiveInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| end | Yes | Event end — ISO 8601 datetime or a date (yyyy-mm-dd) string. | |
| tzid | No | Time zone id for the start/end, e.g. "America/New_York". | |
| start | Yes | Event start — ISO 8601 datetime or a date (yyyy-mm-dd) string. | |
| summary | Yes | Event title/summary. | |
| event_id | Yes | YOUR unique id for the event. Re-using it updates the same event. | |
| calendar_id | Yes | Target calendar id (from cronofy_list_calendars). | |
| description | No | Event description/body. | |
| location_description | No | Free-text location (sent as location.description). |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
8 tool updates
- Changed
cronofy_delete_event1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
cronofy_get_account1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
cronofy_get_free_busy1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
cronofy_get_userinfo1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
cronofy_list_calendars1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
cronofy_list_profiles1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
cronofy_read_events1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
cronofy_upsert_event1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
8 tool updates
- First observed
cronofy_delete_event - First observed
cronofy_get_account - First observed
cronofy_get_free_busy - First observed
cronofy_get_userinfo - First observed
cronofy_list_calendars - First observed
cronofy_list_profiles - First observed
cronofy_read_events - First observed
cronofy_upsert_event
Related MCP Connectors
MCP server for Nylas — read email, calendars, events and contacts, and send email or create events.
Streamable HTTP MCP server for Google Calendar and Sheets with OAuth login.
MCP server for Codat — companies, connections, invoices, bills and financial statements.
MCP server for Withings health data — sleep, activity, heart, and body metrics.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceMCP server for the Teamup Calendar API, enabling event management, calendar listing, and available slot search.-
- AlicenseAqualityBmaintenanceMCP server for Apple Calendar and CalDAV providers. Enables listing, creating, updating, deleting events, and checking free/busy status with per-calendar write protection.6MIT
- FlicenseDqualityDmaintenanceMCP server for interacting with Google Calendar, enabling reading events from public calendars and, with OAuth, creating, updating, and deleting events.1-
- FlicenseNot gradedqualityDmaintenanceMCP server for Google Calendar (single-user) using Service Account authentication. Provides tools to manage events, check free/busy, and find free slots.-
Glama MCP Gateway
Add one secure layer between your agents and this server.