chronary
MCP server by Chronary · mcp
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. Organization keys (chr_sk_) can use every tool; Agent keys (chr_ak_) are limited to their own agent and cannot use org-only tools such as create_agent or find_meeting_time. Scoped keys, cross…
Endpoint: https://api.chronary.ai/mcp
Verification: observed. Source: crawl.
Capabilities (71)
- create_agent
- list_agents
- create_calendar
- create_event
- list_events
- list_org_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
- pause_ical_subscription
- resume_ical_subscription
- get_calendar_context
- create_proposal
- list_proposals
- get_proposal