Home · Setup · Windsurf

MCP Timezone Planner in Windsurf

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.

Eleven tools out of Cascade's ceiling of 100, no network calls and no account. Because mcp_config.json applies to every workspace, the contacts you save are reachable from whichever project you are in when a client emails.

What you get in Windsurf

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.

Install it in Windsurf

The file is mcp_config.json, and the key inside it is mcpServers.

Scope	Path
macOS, Windows and Linux	`~/.codeium/windsurf/mcp_config.json`

{
  "mcpServers": {
    "timezone": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-timezone"]
    }
  }
}

Save and reopen the MCP Servers list; Cascade picks it up without restarting the editor.

The npm publish of @theluckystrike/mcp-timezone is pending; until then use the .mcpb bundle or a clone and build from the latest release.

No install: the hosted endpoint

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.

Windsurf notes worth knowing first

Read this first: mcp_config.json applies to the legacy Cascade agent only. The Devin Local agent, the default for new tabs, takes its servers from the Devin CLI config files, so a correct entry here can still be invisible in a fresh tab. The other hard number is a cap: Cascade reaches at most 100 tools at once, and every enabled server spends from it.

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.

Questions

Where does Windsurf keep its MCP config?

~/.codeium/windsurf/mcp_config.json, under mcpServers. Reach it from the MCPs icon at the top right of the Cascade panel, or Devin Settings, Cascade, MCP Servers.

I edited the file and a new tab still cannot see MCP Timezone Planner.

That file applies to the legacy Cascade agent only. The Devin Local agent, the default for new tabs, reads its servers from the Devin CLI config files instead. Check which agent the tab runs.

How many servers can I load at once?

Cascade reaches at most 100 tools at any one time, and every enabled server spends from that single budget. MCP Timezone Planner contributes 11 tools, so keep the enabled list short rather than counting servers.

MCP Timezone Planner in detail · The same server in VS Code and Cline · Every server in Windsurf · Guides · Windsurf docs