Chronary/chronary-mcp

MCP server for Chronary — calendar tools for AI assistants.
Drops 50 calendar tools (manage agents, calendars, and events, request human Google/Microsoft setup, find meeting times, run scheduling proposals, configure availability rules, manage webhooks, iCal subscriptions, scoped keys, audit log, and usage) into any MCP-compatible client: Claude Desktop, Cursor, VS Code Copilot, Claude Code, Windsurf.
**One-click install via Smithery:** npx -y @smithery/cli mcp add chronary/agent-calendar --client claude (swap --client for cursor, vscode, claude-code, windsurf, …).
Prerequisites
1. A Chronary account — sign up at chronary.ai.
2. An API key from the console (starts with chr_sk_).
3. Node.js ≥ 18 on the machine where the MCP client runs.
Client configurations
All examples use npx -y @chronary/mcp, which downloads and runs the latest version on demand. No install step required.
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
**macOS / Linux:**
**Windows** (uses cmd /c because spawn can't resolve npx.cmd directly):
Restart Claude Desktop after saving.
Cursor
Edit .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (user-level):
**macOS / Linux:**
**Windows:**
VS Code Copilot
Edit .vscode/mcp.json (workspace) or run the **MCP: Open User Configuration** command for a user-level config. VS Code uses a different top-level key (servers) and requires an explicit type:
**macOS / Linux:**
**Windows:**
Claude Code
Edit .mcp.json at the project root, or ~/.claude.json for user-level:
**macOS / Linux:**
**Windows:**
Windsurf
Edit ~/.codeium/windsurf/mcp_config.json (%USERPROFILE%\.codeium\windsurf\mcp_config.json on Windows):
**macOS / Linux:**
**Windows:**
> **Windsurf limit:** Cascade enforces a hard cap of 100 total tools across all MCP servers and 20 tool calls per prompt. Chronary exposes 50; consider --tools filtering if you stack multiple servers.
Reducing context with --tools
Exposing all 50 tools uses LLM tokens on every request. For focused workflows, whitelist only what you need:
Pointing at a non-production API
For self-hosted Chronary instances or development against a local API:
Tools exposed
| Tool | Read-only | Destructive |
|------|-----------|-------------|
| list_calendars, get_calendar | ✓ | |
| create_calendar, update_calendar | | |
| delete_calendar | | ✓ |
| list_events, get_event | ✓ | |
| create_event, update_event, confirm_event | | |
| cancel_event, release_event | | ✓ |
| list_agents, get_agent | ✓ | |
| create_agent, update_agent | | |
| delete_agent | | ✓ |
| get_availability, find_meeting_time | ✓ | |
| get_calendar_context | ✓ | |
| list_proposals, get_proposal | ✓ | |
| create_proposal, respond_to_proposal, resolve_proposal | | |
| cancel_proposal | | ✓ |
| get_availability_rules | ✓ | |
| set_availability_rules | | |