Calendar infrastructure for AI agents.

Chronary gives AI agents a native way to create, manage, and query calendars — one API key, full calendar CRUD, real-time webhooks, availability queries, and iCal feeds for human consumption. Purpose-built for the agentic era, with an MCP server, REST API, and SDKs in TypeScript, Python, Go, and a Go-based CLI.

Get started → · Sign in · Documentation · chronary.ai

First, grab an API key at console.chronary.ai/sign-up — then pick your tool below.

Windows: replace curl -fsSL … | bash with iwr -useb … | iex in any block.

1. Claude Code — install the plugin from inside the Claude Code REPL:

/plugin marketplace add Chronary/chronary-skills
/plugin install chronary@chronary
/reload-plugins

Run /plugins to confirm chronary is listed. (The doubled chronary@chronary is <plugin>@<marketplace> — both happen to be named chronary.) Installs four skills, three slash commands, and the MCP server config in one bundle.

2. Any AGENTS.md-aware agent (Codex, Aider, Devin, Gemini CLI, Amazon Q, Copilot, …) — drop our AGENTS.md into your project root:

curl -fsSL https://raw.githubusercontent.com/Chronary/chronary-skills/main/AGENTS.md -o AGENTS.md

Codex also reads ~/.codex/AGENTS.md for user-wide instructions.

3. Cursor / VS Code Copilot / Windsurf — one-liner installer copies the skill files into the right per-editor location:

curl -fsSL https://raw.githubusercontent.com/Chronary/chronary-skills/main/install.sh | bash -s -- cursor
# targets: cursor | vscode | windsurf | all

For live API calls from these editors, also configure the MCP server (block 4 below).

4. MCP clients (Claude Desktop, Cursor, Windsurf, VS Code) — add this to your client's MCP config file:

{
  "mcpServers": {
    "chronary": {
      "command": "npx",
      "args": ["-y", "@chronary/mcp"],
      "env": { "CHRONARY_API_KEY": "chr_sk_..." }
    }
  }
}

VS Code (.vscode/mcp.json) uses servers instead of mcpServers; everything else is identical.

Verify with npx -y @chronary/mcp --help. Full per-client setup (file locations, auto-approve patterns, troubleshooting) lives in chronary-skills.

The published surfaces — open these to install, file bugs, or read the source:

• chronary-go — Go SDK for native Go services.
• chronary-schemas — Zod schemas and TypeScript types shared by the SDK, webhooks, and OpenAPI spec.
• chronary-toolkit — Agent-framework adapters that wrap the SDK for popular AI frameworks.
• chronary-skills — Full reference for the Quickstart above (installers, plugin manifest, AGENTS.md, all skill files).
• homebrew-tap — Homebrew formula for the chronary CLI.

Most calendar APIs were built for human-driven calendar apps and assume an interactive sign-in flow. Chronary is built for agents:

• One API key, no OAuth dance. Programmatic agents authenticate with an org-scoped or agent-scoped API key. OAuth is reserved for bridging to user-owned Google or Outlook calendars when an agent needs to act on a human's behalf.
• Webhook-first event delivery. Every meaningful change emits an HMAC-signed webhook so downstream agents can react without polling.
• iCal feeds for humans. Calendars produced by agents render in any human calendar app via signed iCal subscription URLs — no separate bridging service needed.
• MCP-native. The same Worker that serves the REST API also exposes an MCP server, so any MCP-capable client (Claude Desktop, Cursor, Windsurf, VS Code) can drive Chronary directly.

• Website — chronary.ai
• Documentation — docs.chronary.ai
• Product and account support — support@chronary.ai
• Security and responsible disclosure — security@chronary.ai (see SECURITY.md)
• Privacy and DPA requests — privacy@chronary.ai
• Discord — Join the server

A note on these repos: most are read-only mirrors of an internal monorepo, populated by an automated release pipeline. Pull requests are not accepted on the mirrors — bug reports go to Issues on the surface where the bug surfaced. chronary-examples and chronary-skills are OSS-native and welcome PRs directly. See CONTRIBUTING.md for the full policy.