Developer

Connect CalendarSync to Claude

Install the CalendarSync MCP server and your AI can read your meetings, surface notes, and schedule events for you. Works with Claude Desktop, Claude Code, Cursor, and any other Model Context Protocol client.

What you can ask

“What meetings do I have today?”
“Show me the notes from my 4pm meeting yesterday.”
“Schedule a 30-minute call with steffi@saltinvestments.com.sg tomorrow at 3pm.”
“Is any of my calendar sync erroring right now?”
“Mark my 4pm meeting as done and add an action item to send the proposal.”
“Pull my Fireflies notes now — the meeting just ended.”

Install (Claude Desktop)

Generate an API key at Settings → API Keys. Copy the cs_live_… value; you'll only see it once. Requires a Pro plan.

Open your Claude Desktop config file:

# macOS
~/Library/Application Support/Claude/claude_desktop_config.json

# Windows
%APPDATA%\Claude\claude_desktop_config.json

Add (or merge into) the mcpServers block:

{
  "mcpServers": {
    "calendarsync": {
      "command": "npx",
      "args": ["-y", "@calendarsync/mcp"],
      "env": {
        "CALENDARSYNC_API_KEY": "cs_live_your_key_here"
      }
    }
  }
}

Restart Claude Desktop. Open any chat, check the tools menu — thecalendarsync_* tools should appear.

Install (Claude Code)

claude mcp add calendarsync npx -- -y @calendarsync/mcp
# then set CALENDARSYNC_API_KEY in your shell env

Install (Cursor / Continue / Zed)

Same pattern — register npx -y @calendarsync/mcp as a stdio MCP server and pass CALENDARSYNC_API_KEY through the env.

Tools exposed

Tool	What it does
calendarsync_status	Account health (connection count, active pairs, recent errors)
calendarsync_list_connections	List connected calendars
calendarsync_list_sync_pairs	List sync pairs
calendarsync_trigger_sync	Manually trigger a sync pair
calendarsync_list_meetings	List meetings with filters (day, date range, search)
calendarsync_get_meeting	Full meeting record including notes + action items
calendarsync_update_meeting	Update status, remarks, action items
calendarsync_log_meeting	Log an ad-hoc meeting (no calendar event)
calendarsync_schedule_event	Create a calendar event on a connected calendar
calendarsync_pull_notes	Force a fresh notetaker pull

Security & privacy

Your API key lives only in your MCP config. Never commit it.
Requests are scoped to the key's owner. No cross-account reads.
100 requests per minute per key.
Rotate anytime at Settings.

Need the raw API?

All MCP tools are thin wrappers over the public REST API. Docs:

REST API Reference

What you can ask

“What meetings do I have today?”

“Show me the notes from my 4pm meeting yesterday.”

“Schedule a 30-minute call with steffi@saltinvestments.com.sg tomorrow at 3pm.”

“Is any of my calendar sync erroring right now?”

“Mark my 4pm meeting as done and add an action item to send the proposal.”

“Pull my Fireflies notes now — the meeting just ended.”

Install (Claude Desktop)

Generate an API key at Settings → API Keys. Copy the cs_live_… value; you'll only see it once. Requires a Pro plan.

Open your Claude Desktop config file:

# macOS
~/Library/Application Support/Claude/claude_desktop_config.json

# Windows
%APPDATA%\Claude\claude_desktop_config.json

Add (or merge into) the mcpServers block:

{
  "mcpServers": {
    "calendarsync": {
      "command": "npx",
      "args": ["-y", "@calendarsync/mcp"],
      "env": {
        "CALENDARSYNC_API_KEY": "cs_live_your_key_here"
      }
    }
  }
}

Restart Claude Desktop. Open any chat, check the tools menu — thecalendarsync_* tools should appear.

Tools exposed

Tool	What it does
calendarsync_status	Account health (connection count, active pairs, recent errors)
calendarsync_list_connections	List connected calendars
calendarsync_list_sync_pairs	List sync pairs
calendarsync_trigger_sync	Manually trigger a sync pair
calendarsync_list_meetings	List meetings with filters (day, date range, search)
calendarsync_get_meeting	Full meeting record including notes + action items
calendarsync_update_meeting	Update status, remarks, action items
calendarsync_log_meeting	Log an ad-hoc meeting (no calendar event)
calendarsync_schedule_event	Create a calendar event on a connected calendar
calendarsync_pull_notes	Force a fresh notetaker pull