Cronofy MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Other

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://cronofy.usefulapi.io/mcp

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

{
  "mcpServers": {
    "cronofy": {
      "url": "https://cronofy.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "cronofy": {
      "type": "http",
      "url": "https://cronofy.usefulapi.io/mcp"
    }
  }
}

https://cronofy.usefulapi.io/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• 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.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 14 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 8 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

• More stars than 0% of the other 32410 servers in this category
• Published to the registry more recently than 97% of the other 32410 servers in this category
• Basic checks equal to or better than 100% of the other 32410 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{