co.lumman/calendar
Multi Calendar
Is the Multi Calendar MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-13.
Outlook.com, Microsoft 365, Google, iCloud, Yahoo, AOL, CalDAV: free time, events, bookings, polls.
needs auth probed 2026-11-15 · unchanged since 2026-11-13 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"authentication_required","error_description":"Multi Calendar - Every calendar in one connector: http- Endpoint
- https://calendar.lumman.co/mcp (streamable-http)
- Host
- calendar.lumman.co
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://calendar.lumman.co/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server gwvrgdrmewwgkjovauzm.supabase.co, PKCE S256, grants authorization_code, refresh_token.
Scopes email.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/lumman-lab/multi-calendar
- Website
- https://lumman.co/mcp/multi-calendar
- Registry
- active, updated 2026-11-12 · registry entry
Compare this server with others.
More servers
Servers that mention calendar.
- CalendarMCP ai.calendarmcp/server · needs auth
- Calaf ai.calaf/calaf · needs auth
- Calfeed ai.calfeed/calfeed · needs auth
- Chronary ai.chronary/mcp · alive
- Contio MeetingOS ai.contio/meetingos · needs auth
- OmniSignal ai.omnisignal/omnisignal · needs auth
- Timothe's Growth Calendar ai.timothe/growth-calendar · needs auth
- ai.smithery/Funding-Machine-ghl-mcp-fundingmachine · not found
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.