Connecting Google Calendar to Cursor (the real way)

Cursor has MCP support built in. Connecting Google Calendar to it takes about five minutes if you pick the right approach. This post covers the two real options: CalendarMCP (hosted, HTTP transport) and nspady/google-calendar-mcp (self-hosted, stdio). Use whichever fits your setup.

Option 1: CalendarMCP (HTTP transport, recommended)

Cursor supports HTTP MCP servers natively since v0.43. CalendarMCP runs as a hosted HTTP server, so there is no local process to manage and no OAuth setup in Google Cloud Console.

Step 1: Get your API key

Go to calendarmcp.ai, connect your Google account, and copy your API key from the dashboard. Takes two minutes.

Step 2: Add the MCP server to Cursor

Open your Cursor settings, go to MCP, and click Add new global MCP server. This opens ~/.cursor/mcp.json (or the project-level .cursor/mcp.json if you want it scoped to one repo).

Add this entry:

{
  "mcpServers": {
    "calendar": {
      "url": "https://calendarmcp.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer cmcp_your_api_key_here"
      }
    }
  }
}

Replace cmcp_your_api_key_here with your actual key. Save the file and restart Cursor Agent mode. The calendar tools show up in the tool list.

Step 3: Verify it works

Open a new Agent chat and type: "What do I have on my calendar today?" Cursor will call the list_events tool and return your events. If you get an auth error, double-check the API key has no extra whitespace.

Option 2: nspady/google-calendar-mcp (self-hosted, stdio)

If you want your Google credentials to stay on your machine and you are comfortable with a 25-minute setup, the nspady server is a solid open-source alternative. The downside: Cursor supports stdio MCP servers through a command launch config, so you run the process locally.

Setup

git clone https://github.com/nspady/google-calendar-mcp
cd google-calendar-mcp
npm install
# Set up Google Cloud project, enable Calendar API, download credentials.json
npm run auth

Then in ~/.cursor/mcp.json:

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

The main friction points: you need a Google Cloud project with the Calendar API enabled and an OAuth 2.0 desktop client created. The nspady README walks through it. Budget 25 minutes the first time. Also note that OAuth tokens expire every 7 days if your consent screen is in testing mode, which it will be unless you go through Google's verification process.

Which one to pick

Pick CalendarMCP if you want this working in five minutes, or if you use multiple Google accounts, or if you need batch operations (rename twenty events at once, find free time across calendars, etc.).

Pick nspady if you need your OAuth tokens to stay local and you are only managing one Google account.

What you can do once it is connected

With calendar access in Cursor Agent, you can build workflows that would otherwise require context-switching out of your editor:

• Ask the agent to check your calendar before scheduling a code review.
• Block focus time while you are deep in a feature branch.
• Have the agent create a calendar event for a deadline extracted from a ticket.
• Prompt it to check for conflicts before the agent books anything.

The agent treats your calendar as just another context. Same window, same thread, no app switching.

Troubleshooting

Tools not appearing: Cursor MCP requires a restart after editing mcp.json. Close and reopen the Agent panel.

Auth errors from CalendarMCP: Check that the Authorization header value starts with Bearer (with a space) followed by your key.

Stdio server not starting: Use the absolute path to the compiled dist/index.js. Relative paths break because Cursor launches the process from a different working directory.

Ready to connect? Head to calendarmcp.ai to get your API key and have your calendar in Cursor in five minutes.