Home · Setup · Claude Desktop

MCP Calendar in Claude Desktop

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.

The .ics file you exported has to reach Claude Desktop's sandboxed process, so give ics_import an absolute path under your home directory rather than a relative one, the same rule every path in this config follows.

What you get in Claude Desktop

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 Claude Desktop

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

Scope	Path
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`
Windows	`%APPDATA%\Claude\claude_desktop_config.json`

One click, with no JSON. Download calendar.mcpb from the bundle catalog and open it. Claude Desktop installs it as an extension and runs it on the Node runtime it ships with, so neither your PATH nor your node version comes into it, and there is no file to edit. Everything below is the manual route, for when you want the entry in the config file itself.

The config block, which needs both strings absolute:

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

If node came from nvm, asdf or homebrew, use the absolute path that which node prints rather than the bare word, because a stdio server started by this app inherits a limited PATH:

"command": "/Users/you/.nvm/versions/node/v22.14.0/bin/node"

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"]
    }
  }
}

Save, then completely quit Claude Desktop and start it again. A window reload is not enough.

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.

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

Claude Desktop notes worth knowing first

Two documented facts decide whether the entry works: every path in claude_desktop_config.json must be absolute, and a stdio server started here inherits only a limited, platform-dependent subset of environment variables. If node came from nvm or homebrew, paste what `which node` prints instead of the bare word. The .mcpb route avoids both: Claude Desktop ships a built-in Node.js environment.

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

Questions

Where is claude_desktop_config.json?

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. Windows: %APPDATA%\Claude\claude_desktop_config.json. There is no published Linux path. Settings, Developer, Edit Config opens the right copy and creates it if it does not exist.

I added it and MCP Calendar does not appear.

In order: did you fully quit and restart, not just close the window? Is every path absolute? And is the command resolvable, given the limited environment a stdio server inherits here? If node came from nvm, paste what which node prints.

Can I install it without editing JSON?

Yes. An .mcpb bundle, the format renamed from .dxt, opens with Claude and shows an installation dialog. One you built yourself goes in through Settings, Extensions, Advanced settings, Install Extension.

MCP Calendar in detail · The same server in Claude.ai and Claude Desktop connectors and Claude Code · Every server in Claude Desktop · Guides · Claude Desktop 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