Find meeting slots inside everyone's working hours. It converts times between IANA zones with DST read from the ICU data in your Node build, ranks meeting slots where every participant is inside their own working hours, computes the daily overlap and clock changes, and writes .ics files.
Put it in the project config for the client you have standing calls with, save that client's contacts once, and the slot search in that workspace already knows the zones and working hours involved.
| You say | Tool |
|---|---|
| Find an hour next week for me in Warsaw, my client in New York and my designer in London. | find_meeting_slots |
| When are Warsaw and New York both at work? | overlap |
| Write me the .ics for Thursday 3pm Warsaw, 45 minutes. | ics_create |
Warsaw and New York on 09:00 to 17:00 days share 2 hours on 2026-09-10 and 3 hours on 2026-03-16, because the United States moves to daylight time on 8 March and Europe on 29 March. The overlap is computed on a real date, so it says so.
The file is .cursor/mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| This project only | <project>/.cursor/mcp.json |
| Every project | ~/.cursor/mcp.json |
{
"mcpServers": {
"timezone": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-timezone"]
}
}
}The Customize page shows the server and its tools once it has started.
The npm publish of @theluckystrike/mcp-timezone is pending; until then use the .mcpb bundle or a clone and build from the latest release.
There is no hosted endpoint for this one yet. MCP Timezone Planner runs locally over stdio with the config above, which is also the only form in which it reads and writes files on your own disk. Three of the servers in this collection are served at https://mcp.zovo.one/mcp/<name> over MCP streamable HTTP: time-tracker, price-tracker and invoice.
The current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.
Free: conversions, overlap, DST and business days unlimited; slots for 3 participants over 5 days, 5 contacts, 3 ics a month. Pro is $19 once, verified offline.
<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.
The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.
Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Timezone Planner pasting the config block above is the supported route.
MCP Timezone Planner in detail · The same server in Claude Code and VS Code · Every server in Cursor · Guides · Cursor docs