Chronary
Calendar API for AI agents — events, availability, scheduling, webhooks, and iCal feeds.
https://api.chronary.ai/mcpCurrent observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- chronary
- Version
- 1.0.0
- Capability keys
- tools, prompts, resources
- Tool names
- create_agent, list_agents, create_calendar, create_event, list_events, get_event, update_event, get_availability, find_meeting_time, cancel_event, confirm_event, release_event, subscribe_ical, list_ical_subscriptions, get_ical_subscription, update_ical_subscription, delete_ical_subscription, sync_ical_subscription, get_calendar_context, create_proposal, list_proposals, get_proposal, respond_to_proposal, resolve_proposal, cancel_proposal, set_availability_rules, get_availability_rules, clear_availability_rules, create_scoped_key, list_scoped_keys, revoke_scoped_key, create_webhook, list_webhooks, get_webhook, update_webhook, delete_webhook, list_webhook_deliveries, get_agent, update_agent, delete_agent (first 40 recorded; the server may expose more)
Chronary is calendar-as-a-service for AI agents. Use these tools to give an agent its own calendars and events, request human-approved Google Calendar or Microsoft Outlook connections, check and coordinate combined availability, run multi-party scheduling proposals, place auto-expiring holds, manage availability rules, sync external iCal feeds, and configure webhooks. Typical flow: create_agent -> create_calendar -> create_event / get_availability / find_meeting_time. IDs are prefixed (agt_, cal_, evt_); timestamps are ISO 8601 (UTC recommended). When checking availability, always inspect availability_state and warnings before treating returned slots as complete. Human-calendar setup requires a human to open setup_url and consent; agents never receive provider credentials or calendar contents. Org keys (chr_sk_) can use every tool; agent-scoped keys (chr_ak_) are limited to their own agent and cannot use org-only tools such as create_agent or find_meeting_time. Temporal holds, cross
Reported Aug 17, 2026, 04:59 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 651ms
- respondsMCP initialize · 8s limit · HTTP 200 · 559ms
- respondsMCP initialize · 8s limit · HTTP 200 · 363ms
- respondsMCP initialize · 8s limit · HTTP 200 · 901ms