Chronary
Calendar API for AI agents: events, availability, Google/Microsoft setup, scheduling, and iCal
What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: plan a content calendar.Similar tools
Listed for the same task: plan a content calendarReviews
No review yet. Used Chronary? Be the first to help others choose.What it does
Chronary is an MCP server, a connector that lets an AI assistant use it as a tool. It can be used hosted (nothing to install) or installed locally.
From the publisher's description, Electra Index matched it to one capability: calendar management. That makes it a candidate for tasks such as plan a content calendar or book appointments online.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 12h ago (live check)Hosted endpoint
https://api.chronary.ai/mcpstreamable-http
Install package
- NPM
@chronary/mcpv1.7.0 · runs locally (stdio)
Required: Authorization, CHRONARY_API_KEY (get them from the publisher)
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"chronary": {
"url": "https://api.chronary.ai/mcp",
"headers": {
"Authorization": "<your Authorization>"
}
}
}
}Replace the values in <angle brackets>.
Live check
Electra Index connected to the hosted endpoint 12h agoONLINE Chronary answered an MCP connection on 17 Nov 2026 and introduced itself as chronary 1.0.0 (MCP protocol 2025-06-18).
65 tools offered to AI assistants
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 organizationcreate_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 agcreate_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 availabilist_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_aftelist_org_events· List events across all of the organization's calendars in one call, ordered by start time (an Agent key sees only its agent's calendars). Narrow with `calendar_ids`, `agent_id`, a `start_after`/`start_before` 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 resolveupdate_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 cget_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 thefind_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`/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_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.
Show 53 more
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 firlist_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· Start an immediate fetch of an external iCal feed instead of waiting for the next scheduled poll. Returns {"status":"syncing"} as soon as the fetch has started; call get_ical_subscription a few seconds later to read last_synced_at and last_pause_ical_subscription· Pause an external iCal feed subscription: scheduled polls skip it and manual syncs are refused until it is resumed. Busy blocks already imported stay. Pausing a paused feed changes nothing. Returns the subscription.resume_ical_subscription· Resume a paused or failing external iCal feed subscription: it returns to scheduled polling and its last_error is cleared. Resuming an active feed changes nothing. Returns the subscription.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 acreate_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-reslist_proposals· List scheduling proposals for the org. Filter by status (pending|resolving|confirmed|expired|cancelled; `resolving` is the brief state while a resolve creates the event) or organizer_agent_id. Requires an Organization key.get_proposal· Get a scheduling proposal by id, including its slots and per-participant responses. Requires an Organization 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 presolve_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 cancelledcancel_proposal· Cancel an open proposal. Fires a proposal.cancelled webhook with reason="organizer_cancelled". Requires an Organization key. Works on every plan, so an org that dropped to Free can still cancel proposals it made on Pro.set_availability_rules· Set or replace the availability rules on a calendar — buffer times before/after events and optional per-day working hours. When these rules are set, every availability query on this calendar automatically applies them (busy-block expansionget_availability_rules· Read the buffer times and working-hours rules configured on a calendar. Returns the rules row, or an error if none are set.clear_availability_rules· Remove the availability rules from a calendar, reverting to the default (no buffers, no working-hours mask). Returns the deleted row, or an error if none were set.create_scoped_key· Create an Agent key (chr_ak_*) that can only act on behalf of a single agent. Use this to self-provision or rotate per-agent credentials. The plaintext key is returned exactly once in the response — store it immediately, it cannot be retrielist_scoped_keys· List all live (non-revoked) Agent keys for this org. Returns key metadata only (id, key_prefix, agent_id, label, created_at, last_used_at, last_used_user_agent, created_via, created_by_key_prefix) — never the plaintext secret. Requires an Orevoke_scoped_key· Revoke an Agent key by ID. Revocation is permanent (cannot be un-revoked); the key stops authenticating within about a minute. Requires an Organization key.create_webhook· Create a webhook subscription so the org receives HTTP POST notifications when events occur (e.g. event.created, proposal.confirmed). The signing secret is returned ONCE in this response — store it to verify the HMAC-SHA256 signature on dellist_webhooks· List the org's webhook subscriptions with their subscribed event types and active state. Signing secrets are never returned. Requires an Organization key.get_webhook· Get a single webhook subscription by id, including its subscribed event types and active state. The signing secret is never returned. Requires an Organization key.update_webhook· Update a webhook subscription — change its delivery URL, the set of subscribed event types, or pause/resume it via active. At least one field must be supplied. Requires an Organization key.delete_webhook· Permanently delete a webhook subscription. This frees its endpoint slot against the per-plan cap. Requires an Organization key.list_webhook_deliveries· List delivery attempts for a webhook subscription, newest first, with per-status counts (pending/delivered/failed/dropped). Filter by status, event type, creation time, delivery id or test flag, and page with next_cursor. `dropped` deliveriget_webhook_delivery· Get one webhook delivery with its payload and every attempt, oldest first: HTTP status, duration, the first 2 KB of the response body and an error code (timeout, connection_error, tls_error, redirect_not_followed, unsafe_destination_url, nosend_test_webhook· Send a signed sample payload of one event type to a webhook endpoint, to check that it receives and verifies deliveries. The delivery is marked is_test, carries the X-Chronary-Test: 1 header, makes one attempt, does not count toward the monreplay_webhook_delivery· Send a failed or dropped webhook delivery again, as a new delivery with a new delivery_id. The stored payload goes out unchanged (same event id), signed with the endpoint's current secret, with an X-Chronary-Replay-Of header naming the origget_agent· Fetch a single agent by ID. An agent represents an AI assistant, human, or shared resource (e.g. a meeting room). Agent keys may only read their own agent.update_agent· Update an agent's name, description, metadata, or status (active/paused). Requires an Organization key — Agent keys cannot mutate agents.delete_agent· Decommission an agent. This marks the agent as decommissioned and revokes all of its Agent keys. Requires an Organization key — Agent keys cannot delete agents.list_calendars· List calendars in the org. Organization keys see every calendar (agent-owned and shared); Agent keys see only their own agent's calendars. Use this to discover calendar IDs before creating or listing events.get_calendar· Fetch a single calendar by ID, including its name, timezone, agent status, and default reminders. Agent keys may only read calendars owned by their agent.update_calendar· Update a calendar's name, timezone, agent status, default reminders, or metadata. Agent keys may only update calendars owned by their agent.delete_calendar· Delete a calendar (soft delete). Its events are no longer returned and it stops contributing to availability. Agent keys may only delete calendars owned by their agent.create_booking_page· Create a public booking page (a hosted scheduling link) for a calendar. Returns a booking_url to send to a human; when they pick a slot, a confirmed event is created on the calendar and an event.created webhook fires with a booking_page_idlist_booking_pages· List booking pages in the org. Agent keys see only pages on their own agent's calendars.get_booking_page· Fetch a single booking page by ID, including its public booking_url and settings.delete_booking_page· Delete (deactivate) a booking page. Its hosted URL stops resolving; already-booked events are unaffected.get_usage· Get the calling org's current-period usage and plan limits (agents, calendars, events, API calls, webhook deliveries, webhook endpoints, availability queries, iCal subscriptions, proposals, recurring events, booking pages, scoped keys, holdget_usage_history· Get the calling org's monthly usage totals for the last 1-12 UTC calendar months (default 6), oldest first, ending with the current partial month. Each month lists every monthly counter (api_calls, events, webhook_deliveries, availability_qget_audit_log· List audit-log entries for the calling org — mutating operations and auth-lifecycle events, newest first. Results are clamped to the plan's retention window. Requires an Organization key (chr_sk_*); Agent keys cannot read the org-wide auditaccept_terms· Re-accept the current Chronary terms of service on behalf of the calling org. Use this when responses carry the Chronary-Terms-Upgrade-Required header — a material ToS bump otherwise leaves MCP-only agents stuck without a console session. Pcreate_connection_link· Request human setup of Google Calendar or Microsoft Outlook for a Chronary calendar. Give setup_url to a human; the agent never receives OAuth credentials, provider calendar names, or event data. When the human finishes, the linked accountget_connection_link· Poll a human-calendar setup request. Returns provider-neutral status and, when complete, the ID of the resulting Connection (the human sees it under Human calendars in the Chronary console), but never replays the bearer setup URL or exposescancel_connection_link· Cancel a pending human-calendar setup request. This invalidates the setup URL and does not disconnect a Connection that was already completed; the human manages Connections under Human calendars in the Chronary console.get_billing· Get the org's plan, subscription status, renewal or cancellation date, any scheduled plan switch, upgrade options with pricing, and any pending upgrade request. Works even when the org is at its usage limit. Requires an Organization key (chrequest_upgrade· Ask your human to upgrade this Chronary account to the next plan up. Returns approval_url — give it to your human; only a human can pay. If reused=true a request is already pending — do not call again; poll get_upgrade_request at most onceget_upgrade_request· Check an upgrade request (pending, completed, declined, canceled, expired). Poll at most once a minute; after completed, wait ~15 seconds before retrying the call that hit the plan limit.cancel_upgrade_request· Withdraw a pending upgrade request (for example, if you no longer need the upgrade).
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Install package | @chronary/mcp | DECLARED | SRC-001 Official MCP Registry | 21h ago |
| Version | 1.7.0 | DECLARED | SRC-001 Official MCP Registry | 21h ago |
| Hosted endpoint | https://api.chronary.ai/mcp | DECLARED | SRC-001 Official MCP Registry | 21h ago |
| Package registries | npm | DECLARED | SRC-001 Official MCP Registry | 21h ago |
| Local install (package) | yes | DECLARED | SRC-001 Official MCP Registry | 21h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 21h ago |
| Website | https://docs.chronary.ai/mcp/overview | DECLARED | SRC-001 Official MCP Registry | 21h ago |
| Repository | https://github.com/Chronary/chronary-mcp | DECLARED | SRC-001 Official MCP Registry | 21h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 21h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 21h ago |
Change history
- VERSION16 Nov 20261.6.2 → 1.7.0
- VERSION13 Nov 20261.6.1 → 1.6.2
- VERSION13 Nov 20261.6.0 → 1.6.1
- VERSION12 Nov 20261.5.2 → 1.6.0
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Chronary still online?
Free alerts · no account▲ 0Do you run Chronary? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Chronary
How do I connect Chronary?
Use the hosted endpoint https://api.chronary.ai/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
Does Chronary need an API key or token?
Yes. The registry entry lists required values: Authorization, CHRONARY_API_KEY. Get them from the publisher.
What tools does Chronary offer?
When Electra Index connected on 17 Nov 2026, it listed 65 tools: create_agent, list_agents, create_calendar, create_event, list_events, list_org_events, get_event, update_event and more. The full list is in "Live check" above.
Is Chronary online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 12h ago.
What can I use Chronary for?
Based on its description, it is most relevant to: plan a content calendar, book appointments online, book travel, schedule meetings.