Hosted vs Self-Hosted Calendar MCP: Which Should You Choose?

When you want your AI agent to access Google Calendar, you have two real options: run a calendar MCP server yourself, or use a hosted one. Both approaches work. The right choice depends on what you actually care about.

This is an honest comparison. I will tell you when self-hosted is the better call.

Self-Hosted: Full Control, Real Friction

The most popular self-hosted option is nspady/google-calendar-mcp on GitHub, with over 1,100 stars. It is open source, runs locally, and your credentials never leave your machine.

What you get

• Complete control over your OAuth credentials
• No third-party service holds your tokens
• Free forever, no usage limits
• Modifiable: you can add custom tools or change behavior
• Works offline (local machine only)

What you give up

• Setup takes 20-30 minutes: GCP project, OAuth app, credentials.json, token management
• Only works with Claude Desktop, not Claude.ai or Claude Code (which need HTTP MCP)
• Your machine must be running for the server to respond
• OAuth tokens expire every 7 days unless you publish your consent screen
• No batch update operations
• No multi-calendar support (queries single calendar only)
• Blocked entirely if you use Google Advanced Protection
• You are responsible for updates and security patches

Hosted (CalendarMCP): Zero Setup, More Features

CalendarMCP is a hosted Google Calendar MCP server. You authenticate once via Google OAuth and get an API key. The server runs in the cloud and works with any HTTP-capable MCP client.

What you get

• Setup in about 2 minutes: connect, get key, add to client
• Works with Claude.ai, Claude Code, Cursor, and any HTTP MCP client
• Always available, no local server to keep running
• Auth managed automatically, no token expiry headaches
• Batch operations: update up to 50 events in a single call
• Multi-calendar support: query across all your calendars in one request
• Google Advanced Protection support via service accounts
• 10 tools covering the full Google Calendar API surface
• Machine-readable API docs at /api/docs for agent self-discovery
• Free to start

What you give up

• CalendarMCP holds your OAuth refresh token (scoped to Google Calendar only)
• You cannot modify the server code or add custom tools
• Dependent on CalendarMCP uptime (though Vercel infrastructure is reliable)
• Paid plans coming; free tier may eventually have rate limits

Feature Comparison

When to Use Self-Hosted

Choose self-hosted if any of these apply:

• You have a strong requirement that no external service holds your Google tokens
• You only use Claude Desktop and have no interest in Claude.ai or Claude Code
• You want to add custom calendar tools or modify the server behavior
• You are in an environment where outbound connections to hosted services are restricted

When to Use CalendarMCP

Choose hosted if any of these apply:

• You want it working in under 5 minutes
• You use Claude.ai, Claude Code, or any client that requires an HTTP MCP endpoint
• You want to use calendar tools from your phone or any device (not just your local machine)
• You need batch operations for bulk event updates
• You have Google Advanced Protection enabled
• You want multi-calendar support

The Bottom Line

Self-hosted is the right call for privacy-sensitive users who are comfortable with the setup overhead and only need Claude Desktop. For everyone else, hosted is the pragmatic choice.

The majority of users fall into the hosted camp. The setup is measured in minutes, not hours. The feature set is larger. And it works across every MCP client without a local server process to babysit.

If you change your mind later, switching is straightforward. The tools and prompts you use are the same either way.