Home · Setup · Cline

MCP Calendar in Cline

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.

events_list, free_busy, conflicts and next_event are read-only and safe to auto-approve; leave ics_import, event_export and ics_forget, which write or remove local data, behind a click.

What you get in Cline

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 Cline

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

Scope	Path
Cline CLI	`~/.cline/mcp.json`
The editor extension	`opened from the Cline panel, not by path; the documentation deliberately calls it the MCP settings JSON used by the extension`

If you also run Claude Desktop, the shortest path there is one click: calendar.mcpb from the bundle catalog opens as an extension, with no JSON and no terminal. Cline reads its own config, so here it is:

The config block:

{
  "mcpServers": {
    "calendar": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/calendar/dist/index.js"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

The node command above wants a built file. From a clone, once:

git clone https://github.com/theluckystrike/mcp-servers.git
cd mcp-servers && npm install
npm run build -w packages/mcp-license -w servers/calendar

That writes servers/calendar/dist/index.js, and its absolute path is the one argument the config needs.

The npm packages are not published yet, so the form below returns a 404 today. It is here because it is what the entry becomes the day the publish lands, with nothing else changed:

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

No full-app restart. The MCP settings actions include restarting an unresponsive server if its tools do not appear.

Nothing is published to npm yet, so the working install paths are the ones above: the .mcpb bundle from the bundle catalog, a clone and build, or the hosted URL.

No install: the hosted endpoint

The same server runs at https://mcp.zovo.one/mcp/calendar over MCP streamable HTTP, no install. Mint a free token with curl https://mcp.zovo.one/mcp/token, or use a Pro key. It has no filesystem, so a file comes back as a one-hour download link.

Write the transport in. Omitting type falls back to the legacy sse transport, which will not talk to this endpoint:

{
  "mcpServers": {
    "calendar": {
      "type": "streamableHttp",
      "url": "https://mcp.zovo.one/mcp/calendar",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Cline notes worth knowing first

Cline is the one client here with an unsafe transport default. `type` selects it, and omitting `type` falls back to the legacy sse transport, so a streamable HTTP endpoint needs it written in or you will debug a server that is fine. Local entries carry "disabled" and an "autoApprove" array.

Free: 2 calendars, windows up to 31 days, exports up to 50 events. Pro is $19 once, verified offline.

Questions

Where does the config live?

The CLI reads ~/.cline/mcp.json. For the extension, do not hunt for a path: MCP Servers icon, Configure tab, Configure MCP Servers. cline mcp opens a wizard, and cline config mcp --json is the non-interactive form.

The hosted endpoint will not connect.

Set the transport explicitly. Omitting type falls back to the legacy sse transport, so streamable HTTP needs "type": "streamableHttp" written in.

Should I auto-approve MCP Calendar's tools?

Approve the read-only ones and leave the writing ones behind a click: each entry carries an autoApprove array and a disabled flag.

MCP Calendar in detail · The same server in Windsurf and Claude.ai and Claude Desktop connectors · Every server in Cline · Guides · Cline docs · Buy Pro

Related guides & tools

Read a .ics calendar in Claude: free and busy, conflicts, and billable meetings · Find a meeting time across time zones without doing the arithmetic