Chronary

Calendar API for AI agents: events, availability, Google/Microsoft setup, scheduling, and iCal.

Chronary is an MCP server that gives AI agents access to calendar functionality through a stdio transport. It is published on npm as @chronary/mcp at version 1.4.1 by ai.chronary, and its source is available on GitHub at Chronary/chronary-mcp.

According to the package description, the server covers the following functional areas: reading and managing calendar events, checking availability, setting up Google and Microsoft calendar integrations, scheduling operations, and working with iCal format data. This means an agent connected to Chronary can interact with calendar data across the two dominant enterprise calendar providers as well as the open iCal standard, without the agent needing to handle OAuth flows or provider-specific API details directly.

The server requires a single environment variable, CHRONARY_API_KEY, to authenticate against the Chronary service. Because no tool definitions were included in the supplied registry record, the exact set of callable tools is not documented here; consult the repository for the full tool manifest before building against specific tool names.

Chronary is a wrong choice if the agent runtime does not support stdio transport, if a self-hosted or purely open-source calendar backend is required (no license information is available), or if the target calendar system is neither Google, Microsoft, nor iCal-compatible.

Use cases

  • Query a user's calendar for available time slots before scheduling a meeting
  • Create or update calendar events on Google or Microsoft calendars from an agent workflow
  • Parse and consume iCal feeds within an automated scheduling pipeline
  • Set up calendar integrations for Google or Microsoft accounts via an agent
  • Check for scheduling conflicts across multiple calendars before confirming bookings

When to use it

  • The agent needs to read or write calendar events on Google or Microsoft calendars
  • The workflow requires availability checking before proposing or confirming meeting times
  • iCal format data must be produced or consumed programmatically
  • The agent runtime supports stdio transport

When not to use it

  • The agent runtime does not support stdio transport
  • A fully self-hosted or open-source calendar solution is required, as the server depends on the Chronary API and no license is provided
  • The target calendar system is not Google, Microsoft, or iCal-compatible
  • Fine-grained tool-level API documentation is needed before integration, as the published registry record does not include a tool list