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. You need CalendarSync Pro (the 7-day trial includes it), an API key, and Node.js 20 or later, because the server runs through npx.

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 sam@example.com 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 Pro or an active trial.

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", "https://www.calendarsync.app/downloads/calendarsync-mcp-0.1.0.tgz"],
      "env": {
        "CALENDARSYNC_API_KEY": "cs_live_your_key_here"
      }
    }
  }
}

Restart Claude Desktop. Open any chat and check the tools menu: the calendarsync_* tools should appear.

On Windows, if the tools do not appear, start npx through cmd instead and restart again:

{
  "mcpServers": {
    "calendarsync": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "https://www.calendarsync.app/downloads/calendarsync-mcp-0.1.0.tgz"],
      "env": {
        "CALENDARSYNC_API_KEY": "cs_live_your_key_here"
      }
    }
  }
}

Install (Claude Code)

One command adds the server with your key and makes it available in every project:

claude mcp add calendarsync -s user -e CALENDARSYNC_API_KEY=cs_live_your_key_here -- npx -y https://www.calendarsync.app/downloads/calendarsync-mcp-0.1.0.tgz

On Windows (not WSL), wrap npx in cmd /c:

claude mcp add calendarsync -s user -e CALENDARSYNC_API_KEY=cs_live_your_key_here -- cmd /c npx -y https://www.calendarsync.app/downloads/calendarsync-mcp-0.1.0.tgz

Run claude mcp list to check it connected.

Install (Cursor)

Add the same block to ~/.cursor/mcp.json for every project, or to .cursor/mcp.json in one project:

{
  "mcpServers": {
    "calendarsync": {
      "command": "npx",
      "args": ["-y", "https://www.calendarsync.app/downloads/calendarsync-mcp-0.1.0.tgz"],
      "env": {
        "CALENDARSYNC_API_KEY": "cs_live_your_key_here"
      }
    }
  }
}

Other MCP clients

Continue, Zed and other MCP clients follow the same pattern: register npx -y https://www.calendarsync.app/downloads/calendarsync-mcp-0.1.0.tgz as a stdio MCP server and pass CALENDARSYNC_API_KEY through the env.

Tools exposed

Tool	What it does
calendarsync_status	Sync health: healthy or degraded, active calendar count, sync pairs with errors, errors in the last 24 hours
calendarsync_list_connections	List your connected calendars with provider, email, status and last sync time
calendarsync_list_sync_pairs	List your sync pairs with mode, direction, status and the calendars on each side
calendarsync_trigger_sync	Run a sync for one active pair now
calendarsync_list_meetings	List meetings by day, date range, status or search text, without the AI notes and action items
calendarsync_get_meeting	Full meeting record including notes and action items
calendarsync_update_meeting	Mark a meeting done or dismissed, or replace its notes or action items
calendarsync_log_meeting	Log a meeting that has no calendar event
calendarsync_schedule_event	Create an event on one of your own connected calendars
calendarsync_pull_notes	Pull new Fireflies notes now instead of waiting for the 15-minute check

Security & privacy

Your API key lives only in your MCP config. Never commit it. The server sends it only to CalendarSync.
Requests are scoped to the key's owner. No cross-account reads.
Anything the tools read, such as meeting notes, action items and attendee names and email addresses, is sent to your AI app's model provider and handled under that provider's terms.
calendarsync_schedule_event creates a real event, and the calendar provider may email each attendee an invitation (Outlook calendars always do). The tool tells your AI to confirm the title, time, calendar and attendees with you before it creates anything.
100 requests per minute per account, shared by all your keys.
Tighter limits on the tools that do real work: one manual sync per pair per minute, 10 new events a minute and 200 a day, and one notes pull every 2 minutes. When a limit is hit, the error tells your AI how many seconds to wait.
Rotate anytime at Settings.

Need the raw API?

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

REST API Reference