MCP server for Cronofy — read calendars, events and free/busy, and create, update or delete events. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"cronofy": {
"url": "https://cronofy.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"cronofy": {
"type": "http",
"url": "https://cronofy.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Cronofy access token.
Use an OAuth access token for your Cronofy account, or a Personal Access Token for single-calendar use. Your token is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Cronofy access token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Cronofy connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
cronofy_get_account | read | Get account Get the authenticated Cronofy account's details (id, email, name, default tzid, locale). API: GET /v1/account. |
cronofy_get_userinfo | read | Get userinfo Get the OpenID-style profile of the authenticated user (sub, email, Cronofy profile info). API: GET /v1/userinfo. |
cronofy_list_calendars | read | List calendars List all calendars the authenticated account can see (id, name, profile, readonly, primary). API: GET /v1/calendars. |
cronofy_list_profiles | read | 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 | 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 | 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 | write | Create or update 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 | write | Delete event Deletes an event (by your event_id) from a real connected calendar. Destructive. API: DELETE /v1/calendars/{calendar_id}/events. |
cronofy_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
cronofy_request_feature | Request a missing feature Tell usefulapi that the user needs something the Cronofy tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
cronofy_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Cronofy tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
cronofy_cancel_subscription | Cancel the Pro subscription Cancel the caller's Cronofy Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run cronofy_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this Cronofy server only. Subscribe with cronofy_upgrade (it returns a Stripe Checkout link). Cancel any time with cronofy_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running cronofy_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Cronofy. The server calls the Cronofy API with your own Cronofy access, so it sees only the data that your account can see.
The login page asks for your Cronofy access token. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Cronofy access token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Cronofy API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Cronofy.
Yes, if you approve it. 2 of the 8 Cronofy tools can create or change data. The other 6 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Cronofy server only. Run cronofy_usage_status to see how many calls you used.
Ask the AI to run cronofy_upgrade: it returns a Stripe Checkout link. To cancel, run cronofy_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with cronofy_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.