Provider hosted
Tools: 54

Chronary

Chronary

Chronary is calendar infrastructure for AI agents — create calendars, manage events, and query availability via a REST API + MCP server. Free tier included.

https://chronary.ai/

Use in your AI tool

Connect straight to this server’s public endpoint.

Remote MCP URL
https://api.chronary.ai/mcp

Use on MCPBundles

We add this server to your workspace, walk through sign-in once, then open Studio with tools ready to run.

Last probed Sep 14, 2026 · api.chronary.ai

54tools discovered

Tools discovered (54)

Showing 25 of 54 from the live probe.

  • Create Agent

    Register your agent (AI assistant, human participant, or resource) with Chronary so it can own calendars, events, and webhooks.

  • List Agents

    List all agents in your organization

  • Create Calendar

    Create a calendar to hold events and track availability. Calendars are required before creating events — call this first when setting up a new agent. An agent can have multiple calendars (e.g. "Work", "Personal"). Org-level calendars (no agent_id) can be used as shared resources like meeting rooms.

  • Create Event

    Create a booking, appointment, meeting, hold, or any scheduled event on a calendar. The calendar_id comes from create_calendar or list_events. Once created, this event blocks the agent's availability during that time and appears in availability queries. Use status="hold" with hold_expires_at to tentatively reserve a slot that auto-releases on TTL.

  • List Events

    List events on a calendar or across an agent's calendars, including internally created events and externally synced events from iCal subscriptions (e.g. Google Calendar, Outlook). Provide `calendar_id` OR `agent_id`. Narrow with `start_after`/`start_before` (time window), `status`, and `source`.

  • Get Event

    Retrieve a single event by ID, including its title, times, status, location, reminders, and metadata. Works for both internally created events and externally synced iCal events. `calendar_id` is optional — if omitted the calendar is resolved from the event. Provide `calendar_id` to fail fast on cross-calendar typos.

  • Update Event

    Reschedule or edit an event — change its title, description, start/end times, location, status, reminders, or metadata. Use this to move an appointment to a new time or update its details. Provide only the fields you want to change. Holds cannot be edited via this tool (use confirm_event / release_event). External iCal events are read-only. `calendar_id` is optional — if omitted it is resolved from the event.

  • Get Availability

    Check when a single agent is free across its Chronary calendars and any human calendars authorized for that agent. This tool is fail-closed: always inspect `availability_state` and `warnings` before using slots. Accepts `start`/`end` or the `start_time`/`end_time` aliases.

  • Find Meeting Time

    Find slots when multiple agents are free across Chronary calendars and any human calendars authorized for each agent. This tool is fail-closed: always inspect `availability_state` and `warnings` before using slots. Accepts `agents`/`start`/`end` or their aliases.

  • Cancel Event

    Delete or cancel an event from a calendar. Use this to remove, cancel, or delete any scheduled event or appointment. The event is marked cancelled and excluded from future availability calculations. For a recurring series, pass `occurrence_start` to cancel just that one occurrence (the series continues); omit it to cancel the whole series. `calendar_id` is optional — if omitted the calendar is looked up from the event. Provide `calendar_id` to fail fast on cross-calendar typos.

  • Confirm Event

    Promote a held event to a confirmed booking. The event must currently have status="hold" and its hold_expires_at must not have passed. After confirmation, event.started and event.ended lifecycle webhooks fire at the scheduled times.

  • Release Event

    Manually release a held event before its hold_expires_at. The event must currently have status="hold". Frees the slot for other agents to book.

  • Subscribe Ical

    Link an external iCal feed (e.g. a human's Google Calendar) to an agent's calendar so external events appear in availability calculations. The target calendar must be owned by the specified agent — create the calendar with that agent_id first (org-level calendars without an agent_id cannot host external iCal subscriptions; create a dedicated per-agent calendar for sync targets).

  • List Ical Subscriptions

    List an agent's external iCal feed subscriptions (e.g. linked Google Calendar / Outlook feeds), including their sync status and last sync time.

  • Get Ical Subscription

    Get a single external iCal feed subscription by id, including its sync status, last sync time, and last error.

  • Update Ical Subscription

    Update an external iCal feed subscription — change its label or its feed URL. Changing the URL forces a full re-sync on the next poll.

  • Delete Ical Subscription

    Delete an external iCal feed subscription. Events previously synced from the feed are no longer refreshed.

  • Sync Ical Subscription

    Trigger an immediate sync of an external iCal feed subscription instead of waiting for the next scheduled poll. Returns once the sync has been queued.

  • Get Calendar Context

    Get a calendar's temporal context in a single call: the current event (if one is happening now), the next upcoming event, recent past events, a short upcoming window, and the owning agent's status (idle/working/waiting/error). Use this to answer "what is this agent doing right now?" without issuing multiple list_events queries.

  • Create Proposal

    Create a scheduling proposal — send a set of candidate time slots to one or more participant agents so they can accept, decline, or counter-propose. The organizer agent owns the proposal; once every participant responds, the system auto-resolves to the highest-scoring slot (or cancels if all decline). Requires an org-level API key. Pro plan only.

  • List Proposals

    List scheduling proposals for the org. Filter by status (pending|confirmed|expired|cancelled) or organizer_agent_id. Requires an org-level API key.

  • Get Proposal

    Get a scheduling proposal by id, including its slots and per-participant responses. Requires an org-level API key.

  • Respond To Proposal

    Submit a response (accept / decline / counter) on behalf of one participant agent to an open proposal. An "accept" requires the slot id from the proposal; a "counter" can suggest alternative slots. When all participants have responded the proposal auto-resolves — no separate resolve call needed in the normal flow. Requires an org-level API key. Pro plan only.

  • Resolve Proposal

    Force-resolve an open proposal using responses collected so far. Picks the highest-scoring slot among those accepted by the most participants and creates a confirmed calendar event. If every response was "decline", the proposal is cancelled instead. Use when you want to close out a proposal without waiting for every participant. Requires an org-level API key. Pro plan only.

  • Cancel Proposal

    Cancel an open proposal. Fires a proposal.cancelled webhook with reason="organizer_cancelled". Requires an org-level API key. Pro plan only.

Get your MCP into directories

A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.

Directory coverage for brands

Frequently Asked Questions

What is the Chronary MCP server?

Chronary is calendar infrastructure for AI agents — create calendars, manage events, and query availability via a REST API + MCP server. Free tier included.

How do I connect Chronary to my AI agent?

Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.

How many tools does Chronary provide?

MCPBundles probed 54 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.

What authentication does Chronary require?

Chronary may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.

Maintain this listing

Operate Chronary? Verify ownership to take over this directory entry.

Operate Chronary?

This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.

Claim this listing