chronary-mcp

Chronary MCP is an MCP server for the Chronary Calendar API, designed to provide calendar-related tools for AI assistants. It provides 50 calendar tools to any MCP-compatible client (such as Claude Desktop, Cursor, VS Code Copilot, Claude Code, Windsurf), covering managing agents, calendars, and events, requesting manual Google/Microsoft setup, finding meeting times, running scheduling proposals, configuring availability rules, managing webhooks, iCal subscriptions, scoped keys, audit logs, and usage.

Usage:

• Prerequisites: A Chronary account (sign up at chronary.ai), an API key generated in the console (starting with chr_sk_), and Node.js ≥ 18 installed on the machine running the MCP client.
• One-click installation: Run npx -y @smithery/cli mcp add chronary/agent-calendar --client claude via Smithery (you can replace --client with cursor, vscode, claude-code, windsurf, etc.).
• Manual configuration: All examples use npx -y @chronary/mcp, which downloads and runs the latest version as needed, with no installation step required. Configuration file locations differ by client: For Claude Desktop, edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows); on Windows, use the cmd /c form; for Cursor, edit .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (user-level); for VS Code Copilot, edit .vscode/mcp.json (workspace) or run the MCP: Open User Configuration command, use the top-level key servers and require an explicit type; for Claude Code, editthe project root .mcp.json or the user-level ~/.claude.json; for Windsurf, edit ~/.codeium/windsurf/mcp_config.json (on Windows, %USERPROFILE%.codeium\windsurf\mcp_config.json). After saving, restart the MCP client.
• Reducing context: Exposing all 50 tools consumes LLM tokens on every request; you can use the --tools parameter to whitelist only the tools you need.
• Pointing to a non-production API: Supports self-hosted Chronary instances or development against a local API.
• Tool annotations: readOnlyHint, destructiveHint, and idempotentHint are exposed to MCP clients so the host can decide whether user confirmation is required.

Use cases: Users who need to integrate capabilities such as calendar management, meeting time finding, scheduling proposals, and availability rule configuration into AI assistant workflows.

Limitations: Windsurf's Cascade has a hard cap of 100 total tools across all MCP servers, and at most 20 tool calls per prompt; Chronary exposes 50 tools, so if multiple servers are stacked, consider using --tools filtering. No other limitations are currently provided.