Skip to content
Back to the index

chronary

chronary.aiInfrastructure

PulseGate's liveness check found it on 13 Sep 2026; it is registered on GitHub and PyPI and has been in the index since 26 Jun 2026. How this is checked

Chronary is a calendar for AI agents. It provides calendar infrastructure for agents to create calendars, manage events, query availability, and sync with human calendar apps through a REST API and an MCP server.

Inferred · not functionally tested

Open SourceApache-2.0WebCLIAPI
chronary preview
Visit chronary.ai

Overview

5 features

Purpose: Enables developers to integrate calendar-as-a-service functionality into Python applications easily.

Inferred · not functionally tested

Audience: python developers

Inferred · not functionally tested

Functions: scheduling, agents, collaboration, workflow_automation

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: unknown

Recorded constraints: pricing: open_source · license: Apache-2.0 · platforms: CLI, WEB · deployment: browser, cli, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: chronary.ai · github.com. These links do not verify the individual claims.

chronary sits in PulseGate's API design, testing & docs category. Inferred · not functionally tested: It enables developers to integrate calendar-as-a-service functionality into Python applications easily. Inferred · not functionally tested: chronary is an open-source project aimed at python developers. Basis unknown · not verified: The project is open source (Apache-2.0). Basis unknown · not verified: It ships for the web, the command line, and API.

It is developed by Chronary, and it first shipped in 2026. Development happens publicly on GitHub with 13 commits in the last 90 days. Inferred · not functionally tested: Among its 5 catalogued features are Calendar API client, event management, and authentication support. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Calendar API client
  • Event management
  • Authentication support
  • Python integration
  • Open source

Topics: Inferred · not functionally tested

Tags
calendar-apipython-librarycalendar-integration

JSON profile · Text profile · Access guide

Built with & integrations

Framework
Astro
Hosting
Cloudflare
AI providers
multiple
Connectors
MCPAPIwebhooknotion
Runs on
BrowserCLIAPI-only

Trust & compliance

License
Apache-2.0
Public signals
HTTPSOpen SourceGitHubActive maintenance

Indexing history

What PulseGate has recorded for this listing

Nothing recorded for this listing in this window.

Frequently asked questions about chronary

What does chronary do?
Inferred · not functionally tested: Chronary enables developers to integrate calendar-as-a-service functionality into Python applications easily. It is catalogued under API design, testing & docs on PulseGate.
Who should use chronary?
Inferred · not functionally tested: chronary is an open-source project built for python developers.
Does chronary have a free plan?
Basis unknown · not verified: Yes — chronary is open source under the Apache-2.0 license and free to use.
What platforms does chronary run on?
Basis unknown · not verified: chronary runs on the web, the command line, and API.
Is chronary still maintained?
PulseGate's liveness check found it on 13 Sep 2026. Its GitHub repository shows 13 commits in the last 90 days.
Who develops chronary?
chronary is developed by Chronary.
How long has chronary been around?
chronary first shipped in 2026.
Is chronary open source?
Basis unknown · not verified: Yes — chronary is open source under the Apache-2.0 license, developed on GitHub.

Similar projects

Closest matches by what these projects do