cicadaCalendars as code

The bug that shows up on time. Declare calendars in YAML; plan, apply, and detect drift like infrastructure — with an MCP server so agents can too.

Get started

Reference

Declarative YAML DSL

Events, recurrence, attendees, conferencing, and reminders declared as code — a Kubernetes-style apiVersion/kind envelope, validated before anything touches a provider.

Plan / apply / drift

Desired vs recorded vs live state, diffed into ordered create/update/delete/replace operations. Apply is sequenced, idempotent, resumable, and never deletes what it didn't create.

MCP for agents, day one

cicada-mcp serves the same pure core over MCP stdio — agents read, preview, and reconcile calendars through a confirmation-gated plan.apply.

Provider-agnostic by construction

Ports-and-adapters: Google Calendar today (Meet included), more providers behind the same CalendarProvider port. Capabilities are checked at plan time, never silently dropped.