Connect Chronary and your agent gets 54 tools, among them accept_terms, cancel_connection_link, cancel_event. It answers at https://api.chronary.ai/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.
Calendar API for AI agents: events, availability, Google/Microsoft setup, scheduling, and iCal.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
accept_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. P Inputs: tos_version |
cancel_connection_link | Cancel a pending human-calendar setup request. This invalidates the setup URL and does not disconnect an already completed Google or Microsoft connection. Inputs: connection_link_id |
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_ Inputs: event_id, calendar_id, occurrence_start |
cancel_proposal | Cancel an open proposal. Fires a proposal.cancelled webhook with reason="organizer_cancelled". Requires an org-level API key. Pro plan only. Inputs: proposal_id |
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. Inputs: calendar_id |
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. Inputs: event_id |
create_agent | Register your agent (AI assistant, human participant, or resource) with Chronary so it can own calendars, events, and webhooks. Inputs: name, type, description |
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_id Inputs: calendar_id, title, description, duration_minutes, buffer_minutes, window_days |
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 ag Inputs: name, agent_id, timezone, default_reminders |
create_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. The secret URL is returned only on first cre Inputs: calendar_id, capabilities, publication_policy |
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 availabi Inputs: calendar_id, title, start_time, end_time, description, all_day |
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-res Inputs: title, description, organizer_agent_id, participant_agent_ids, calendar_id, slots |
create_scoped_key | Create an agent-scoped API 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 canno Inputs: agent_id, label |
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 del Inputs: url, events |
delete_agent | Decommission an agent. This marks the agent as decommissioned and revokes all of its scoped API keys. Requires an org-level API key — agent-scoped keys cannot delete agents. Inputs: agent_id |
delete_booking_page | Delete (deactivate) a booking page. Its hosted URL stops resolving; already-booked events are unaffected. Inputs: booking_page_id |
delete_calendar | Delete a calendar (soft delete). Its events are no longer returned and it stops contributing to availability. Agent-scoped keys may only delete calendars owned by their agent. Inputs: calendar_id |
delete_ical_subscription | Delete an external iCal feed subscription. Events previously synced from the feed are no longer refreshed. Inputs: subscription_id |
delete_webhook | Permanently delete a webhook subscription. This frees its endpoint slot against the per-plan cap. Requires an org-level API key. Inputs: webhook_id |
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`/ Inputs: agents, agent_ids, start, end, start_time, end_time |
get_agent | Fetch a single agent by ID. An agent represents an AI assistant, human, or shared resource (e.g. a meeting room). Agent-scoped API keys may only read their own agent. Inputs: agent_id |
get_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 org-level API key (chr_sk_*); agent-scoped keys cannot read the org-wi Inputs: from, to, action, actor_key_prefix, cursor, limit |
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 Inputs: agent_id, start, end, start_time, end_time, duration |
get_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. Inputs: calendar_id |
get_booking_page | Fetch a single booking page by ID, including its public booking_url and settings. Inputs: booking_page_id |
get_calendar | Fetch a single calendar by ID, including its name, timezone, agent status, and default reminders. Agent-scoped keys may only read calendars owned by their agent. Inputs: calendar_id |
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 a Inputs: calendar_id |
get_connection_link | Poll a human-calendar setup request. Returns provider-neutral status and resulting connection ID when complete, but never replays the bearer setup URL or exposes human calendar data. Inputs: connection_link_id |
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 resolve Inputs: event_id, calendar_id |
get_ical_subscription | Get a single external iCal feed subscription by id, including its sync status, last sync time, and last error. Inputs: subscription_id |
get_proposal | Get a scheduling proposal by id, including its slots and per-participant responses. Requires an org-level API key. Inputs: proposal_id |
get_usage | Get the calling org's current-period usage and plan limits (agents, calendars, events, API calls, webhooks, availability queries, iCal subscriptions, proposals, scoped keys, holds, cross-calendar queries). Requires an org-level API key (chr |
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 org-level API key. Inputs: webhook_id |
list_agents | List all agents in your organization Inputs: type, status, limit, offset |
list_booking_pages | List booking pages in the org. Agent-scoped keys see only pages on their own agent's calendars. Inputs: limit, offset |
list_calendars | List calendars in the org. Org-level API keys see every calendar (agent-owned and shared); agent-scoped keys see only their own agent's calendars. Use this to discover calendar IDs before creating or listing events. Inputs: agent_id, include, limit, offset |
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_afte Inputs: calendar_id, agent_id, start_after, start_before, status, source |
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. Inputs: agent_id, status, limit, offset |
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. Inputs: status, organizer_agent_id, limit, offset |
list_scoped_keys | List all live (non-revoked) agent-scoped API keys for this org. Returns key metadata only (id, prefix, agent_id, label, created_at) — never the plaintext secret. Requires an org-level API key. |
list_webhook_deliveries, list_webhooks, release_event, resolve_proposal, respond_to_proposal, revoke_scoped_key, set_availability_rules, subscribe_ical, sync_ical_subscription, update_agent, update_calendar, update_event, update_ical_subscription, update_webhook
Every block below points at https://api.chronary.ai/mcp. Pick your client and copy.
claude mcp add --transport http chronary https://api.chronary.ai/mcp
{
"mcpServers": {
"chronary": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.chronary.ai/mcp"]
}
}
}{
"mcpServers": {
"chronary": {
"url": "https://api.chronary.ai/mcp"
}
}
}{
"servers": {
"chronary": {
"type": "http",
"url": "https://api.chronary.ai/mcp"
}
}
}{
"context_servers": {
"chronary": {
"url": "https://api.chronary.ai/mcp"
}
}
}{
"mcpServers": {
"chronary": {
"serverUrl": "https://api.chronary.ai/mcp"
}
}
}{
"mcpServers": {
"chronary": {
"url": "https://api.chronary.ai/mcp"
}
}
}name: Chronary
version: 0.0.1
schema: v1
mcpServers:
- name: Chronary
type: streamable-http
url: https://api.chronary.ai/mcp{
"mcpServers": {
"chronary": {
"httpUrl": "https://api.chronary.ai/mcp"
}
}
}{
"mcpServers": {
"chronary": {
"type": "http",
"url": "https://api.chronary.ai/mcp"
}
}
}{
"mcpServers": {
"chronary": {
"url": "https://api.chronary.ai/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.chronary.ai%2Fmcp&type=streamable_http&id=chronary&name=Chronary
It answered our last check on 17 October 2026 in 506 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by chronary.ai and served from api.chronary.ai, the vendor's own domain: https://api.chronary.ai/mcp.
54, as returned by the server's own tools/list on 7 September 2026: accept_terms, cancel_connection_link, cancel_event, cancel_proposal, clear_availability_rules, confirm_event, create_agent, create_booking_page, and 46 more.
It answered our last check on 17 October 2026 in 506 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.chronary.ai/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: ai.chronary. Endpoint host: api.chronary.ai. ARD identifier: urn:air:ai.chronary:mcp:mcp.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.