Skip to content

Windsurf calendar ics reader events freebusy conflicts events_list

How to: Windsurf calendar ics reader events freebusy conflicts events_list

client:Windsurf transport:streamable-http tool:events_list

Add calendar ics reader events freebusy conflicts to Windsurf

  1. 01

    Open ~/.codeium/windsurf/mcp_config.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "calendar-ics-reader-events-freebusy-conflicts": {
      "serverUrl": "https://mcp.zovo.one/mcp/calendar"
    }
  }
}
  1. 02

    Save the file and restart Windsurf.

  2. 03

    Ask for something events_list does. Windsurf lists the server's tools on connect and calls events_list itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that calendar ics reader events freebusy conflicts's identifier in your config matches the one above exactly.

Global only — Windsurf has no per-project MCP config. Refresh Cascade after saving. Windsurf docs

Set these first

calendar ics reader events freebusy conflicts will not start until these are set, so events_list never becomes available.

  • MCP_LICENSE_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.