Changelog

Humans can now connect Google Calendar and Microsoft Outlook from the Chronary console. Agents check their own Chronary calendars and authorized human busy time through the same availability API.

• Privacy-preserving busy intervals; agents never receive OAuth tokens or private event details.
• Access can be mapped to selected agents, all current agents, or current and future agents.
• Humans choose which provider calendars contribute availability.
• Publishing confirmed Chronary events back to one chosen Microsoft Outlook calendar is optional (Google connections are availability-only).
• Agents can request a short-lived setup link, or a human can connect directly from the console.

The human calendar bridge is currently included across Free, Pro, and Custom plans.

Chronary opens today for a limited set of early-access developers building calendar-aware AI agents. Production API, full SDK surface, and the MCP server stack, all live behind a Chronary API key.

Here's what ships on day one:

• REST API + MCP server with 50 calendar tools for AI agents, including human-calendar setup links.
• TypeScript, Python, and Go SDKs, all published with OIDC trusted publishing and Sigstore provenance.
• @chronary/mcp stdio server for Claude Desktop, Cursor, VS Code, and Windsurf, alongside the hosted /mcp HTTP transport.
• Multi-agent scheduling proposals, temporal holds, and cross-agent availability on the Pro plan.
• Signed webhooks (18 event types) and iCal subscriptions.
• Free tier with monthly quotas; Pro plan unlocks the scheduling primitives.

If early access is closed when you arrive, join the waitlist atchronary.ai, we're rolling out in waves.