Chronary
Calendar API for AI agents to manage events and scheduling.
View on GitHub Updated 2026-06-30
What is the Chronary MCP server?
Chronary enables AI systems to interact with calendars through a dedicated API. Agents can create, update, and query events while checking availability and setting up automated scheduling.
The server also supports webhook notifications for real-time updates and iCal feed generation or consumption, making it suitable for integration into agent-driven productivity tools.
Install & connect
Add this to your MCP client config. Pick your client below and copy.
{
"mcpServers": {
"mcp": {
"url": "https://api.chronary.ai/mcp"
}
}
}Package: @chronary/mcp (npm)
Example prompts
Once connected, try asking your AI client:
“Check my availability for next Tuesday afternoon and suggest meeting times.
“Create a new event called Project Sync with the team for 2pm tomorrow.
“Set up a webhook to notify me of any calendar changes this week.
“Export my upcoming events as an iCal feed for the next 30 days.
Configuration
Environment variables this server needs.
| Variable | Required | Description |
|---|---|---|
CHRONARY_API_KEYsecret | Yes | Chronary API key — org key (chr_sk_...) or agent-scoped key (chr_ak_...). Request access at https://chronary.ai. |
Security & permissions
Runs locally via stdio and requires the CHRONARY_API_KEY environment variable to authenticate with the calendar service; it can access and modify calendar data tied to that key.
What you can do with Chronary
Automated Meeting Scheduling
An AI agent uses Chronary to find free slots, propose times, and book meetings across multiple calendars.
Event Monitoring with Webhooks
Receive instant notifications when calendar events are created, modified, or canceled to trigger downstream agent actions.
iCal Feed Integration
Generate or consume iCal feeds to sync calendar data between AI agents and external applications or users.
How to use Chronary
- 1Install the Chronary MCP server package in your environment.
- 2Obtain a valid CHRONARY_API_KEY from the calendar service provider.
- 3Set the CHRONARY_API_KEY environment variable before launching the server.
- 4Configure your AI client to connect via stdio transport to the Chronary server.
- 5Test connectivity by issuing a simple calendar query through your agent.
Chronary: pros & cons
Pros
- +Purpose-built API for AI agent calendar interactions
- +Supports both real-time webhooks and iCal standards
- +Lightweight stdio transport suitable for local agent setups
- +Focused feature set for events, availability, and scheduling
Cons
- –No publicly documented tools or parameters available
- –Requires external API key and corresponding calendar service access
- –Limited to stdio; not suitable for remote or distributed deployments
Did you find this helpful?
Frequently asked questions
CHRONARY_API_KEY must be set to authenticate requests to the calendar backend.
User reviews
Verified reviews from the community shape this listing's rating.
Loading reviews…
Similar MCP servers
Other ai & knowledge connectors worth a look.
