MCP server for Cronofy — read calendars, events and free/busy, and create, update or delete events. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.
Turn on the Cronofy connector, then ask in plain words. The AI picks the tools.
For people and teams who manage connected Google or Office 365 calendars through Cronofy.
The AI reads events across all connected calendars over a time window and lists them in order.
The AI reads the busy times across your calendars for a time window and finds gaps long enough for the meeting.
The AI creates an event on one of your calendars, or updates an existing event by its event id. It writes to the real calendar.
Changes dataThe AI finds the event in a time window and deletes it from the calendar by event id.
Changes dataThe AI lists the calendars you can see and the connected calendar profiles, such as Google or Office 365.
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.
Team and Enterprise: an Owner adds the connector for the organization first.
No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
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"
}
}
} Run these commands. The second one opens the login page:
Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.
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.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Pro | $9/mo · $90/yr | 10,000 tool calls / month |
| Pro+ | $39/mo · $390/yr | 100,000 tool calls / month |
Each paid plan covers this Cronofy server only. Ask your AI to run cronofy_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with cronofy_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with cronofy_upgrade before then undoes the cancel. Or write to [email protected].
cronofy_get_accountcronofy_get_userinfocronofy_list_calendarscronofy_list_profilescronofy_read_eventscronofy_get_free_busycronofy_upsert_eventcronofy_delete_eventcronofy_usage_statuscronofy_request_featurecronofy_upgradecronofy_cancel_subscriptionSee what is on your calendars this week. Find open time for a meeting. Add or change a calendar event. Delete an event from a calendar. Check which calendars and accounts are connected. See what you can do for the details.
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.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
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 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Cronofy server only. Cancel any time: your paid plan then runs to the end of the paid period. Run cronofy_usage_status to see how many calls you used.
Ask the AI to run cronofy_upgrade and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run cronofy_cancel_subscription. Your paid plan 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, ChatGPT, Codex, 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.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.