Chronary — Claude Code MCP server: calendars and scheduling
Hands your agent calendar access: events, availability and meeting-time search. Useful when scheduling calls straight from an AI chat.
claude mcp add mcp -e CHRONARY_API_KEY=<CHRONARY_API_KEY> -- npx -y @chronary/mcpWhat Chronary does
Chronary is an MCP server that wires a calendar API into your AI client. The agent gets 50 tools: it creates and cancels events, hunts for open slots, maintains availability rules, and manages webhooks plus iCal subscriptions. Some tools are flagged destructive — deleting a calendar, cancelling an event, revoking a key. Whether to ask for confirmation is up to the host.
It runs through npx -y @chronary/mcp, so there is no install step. You will need a Chronary account, an API key from the console starting with chr_sk_, and Node.js 18 or newer on the machine running the client. The key goes into CHRONARY_API_KEY.
All 50 tools burn tokens on every request. For a narrow workflow, the --tools flag keeps only the listed tools in context. Windsurf's Cascade caps you at 100 tools across every MCP server and 20 calls per prompt, so filtering stops being optional once you stack servers. On Windows, spawn cannot resolve npx.cmd — write the config with cmd /c npx ... instead.
What it helps with
- find a shared open slot across several attendees
- create a calendar event from an agent chat
- set availability rules for booking
- subscribe to an outside calendar over iCal and sync it
- check the audit log and API usage
Example prompts for the agent
- Find a time for a team meeting next week and create the event
- Show me everything on my calendar tomorrow
- Set availability rules so I only take meetings on Tuesdays and Thursdays
How to install Chronary
1Platform CLI
claude mcp add mcp -e CHRONARY_API_KEY=<CHRONARY_API_KEY> -- npx -y @chronary/mcpReplace <…> with your own values
2Platform CLI: remote server
claude mcp add --transport http chronary https://api.chronary.ai/mcp1Platform CLI: remote server
codex mcp add chronary --url https://api.chronary.ai/mcp2Platform CLI
codex mcp add chronary --env CHRONARY_API_KEY=<CHRONARY_API_KEY> -- npx -y @chronary/mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"chronary": {
"url": "https://api.chronary.ai/mcp"
}
}
}{
"mcpServers": {
"chronary": {
"command": "npx",
"args": [
"-y",
"@chronary/mcp"
],
"env": {
"CHRONARY_API_KEY": "<CHRONARY_API_KEY>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"chronary": {
"type": "http",
"url": "https://api.chronary.ai/mcp"
}
}
}{
"servers": {
"chronary": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@chronary/mcp"
],
"env": {
"CHRONARY_API_KEY": "<CHRONARY_API_KEY>"
}
}
}
}Replace <…> with your own values
1Platform CLI: remote server
gemini mcp add -t http chronary https://api.chronary.ai/mcp2Platform CLI
gemini mcp add -e CHRONARY_API_KEY=<CHRONARY_API_KEY> chronary npx -y @chronary/mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Chronary
How do I install Chronary in Claude Code?
Run claude mcp add mcp -e CHRONARY_API_KEY=<CHRONARY_API_KEY> -- npx -y @chronary/mcp, replacing the key with your own from the Chronary console.
What does Chronary do?
It connects a calendar API to an AI client, so the agent can manage calendars, events and agents, search for meeting times, and handle availability rules, webhooks and iCal subscriptions.
What do I need to run Chronary?
A Chronary account, an API key starting with chr_sk_, and Node.js 18 or newer on the machine where the MCP client runs.
