cronofy
Server Details
MCP server for Cronofy — read calendars, events and free/busy, and create, update or delete events.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
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). |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!