docs/ops/personal/michael/reflections/2026-01-14-calendar-mcp-gap

Reflection: Calendar MCP - Not Ready Yet

January 14, 2026

The Gap

Calendar MCP servers exist and work. But they're not usable for real multi-calendar setups because:

1. Privacy/Visibility Control

  • Personal calendar conflicts with business calendar
  • Want co-founder to know "there's a conflict" without seeing what it is
  • Need a visibility layer between raw calendar data and what Claude exposes
  • This middleware doesn't exist yet

2. Multi-Account Complexity

  • 3+ calendar accounts
  • Each needs separate OAuth setup
  • Pain in the ass to configure

3. Current Workaround is Fine

  • "Hey, just tell me when you're free" works
  • Scheduling requires conversation anyway
  • Low friction, high trust

What Would Make It Valuable

An intermediate app/layer that:

  • Aggregates multiple calendars
  • Exposes "busy/free" without details for certain calendars
  • Single OAuth instead of per-account
  • Lets you define visibility rules per calendar

Status

Waiting for ecosystem to mature. Not worth the setup friction now.

Daisy

v1

What do you need?

I can pull up the fundraise pipeline, CRM accounts, hot board, meeting notes — anything in the OS.

Sonnet · read-only