Home · Setup · Windsurf

MCP Calendar in Windsurf

Read .ics calendars: events, free and busy, conflicts, exports. It imports a .ics export from Google, Apple or Outlook, expands recurring series correctly across DST, lists events, computes free and busy blocks, flags overlapping events across every imported calendar, exports a selection, and turns a meeting into a time entry.

Twelve tools against Cascade's 100-tool ceiling, and this one is read from a file you re-import occasionally rather than a service polled continuously, so it costs little to leave enabled.

What you get in Windsurf

You say	Tool
What is on my calendar next week and where am I free for two hours?	`events_list then free_busy`
Do any of my meetings clash this week?	`conflicts`
Log yesterday's Nova call as billable time.	`event_to_time_entry`

VTIMEZONE blocks in the file are ignored on purpose: every offset is computed from the ICU data inside Node from the TZID name, which is what keeps a weekly 10:00 Warsaw meeting at 10:00 local across the March clock change instead of drifting to 11:00.

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": {
    "calendar": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-calendar"]
    }
  }
}

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

The npm publish of @theluckystrike/mcp-calendar 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 Calendar 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: 2 calendars, windows up to 31 days, exports up to 50 events. 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 Calendar.

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 Calendar contributes 12 tools, so keep the enabled list short rather than counting servers.

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