Agent Frameworks

@chronary/toolkit exposes Chronary’s calendar tools in the exact shape each popular AI-agent framework expects — so you can give an agent its own calendar (create events, check and coordinate availability, find meeting times, run scheduling proposals) without hand-wiring HTTP calls or OAuth.

Install

npm install @chronary/toolkit @chronary/sdk

Then install the peer dependency for your framework (ai, @langchain/core, openai, @mastra/core, or @modelcontextprotocol/sdk) — see each framework page below.

Pick your framework

Vercel AI SDKcreateChronaryAISDKToolkit — tools for generateText / streamText

LangChaincreateChronaryLangChainToolkit — StructuredTools for bindTools / agents

OpenAIcreateChronaryOpenAIToolkit — function-calling tool defs

MastracreateChronaryMastraToolkit — tools for a Mastra Agent

How it layers

your agent code
       ↓
@chronary/toolkit/<framework>   ← adapts the tools to each framework's format
       ↓
@chronary/sdk                   ← typed HTTP client
       ↓
api.chronary.ai (REST)

Every adapter produces the same 50 Chronary tools — agents, calendars, events, human-calendar setup links, availability, cross-agent meeting-time search, scheduling proposals, availability rules, holds, webhooks, and iCal subscriptions. See the full list in the MCP Tools Reference (the toolkit and the MCP server expose the same surface).

toolkit vs. MCP vs. raw SDK

Use the toolkit when…

You’re building an agent in code with Vercel AI SDK, LangChain, OpenAI, or Mastra. The toolkit hands you ready-made tool definitions — no schema wiring.

Use MCP when…

Your agent runs inside an MCP client (Claude Desktop, Cursor, VS Code, Windsurf). Point it at @chronary/mcp or the hosted https://api.chronary.ai/mcp — see the MCP Overview.

Use the raw SDK when…

You want direct REST control (backends, cron jobs, webhooks) without a tool-calling layer. Use @chronary/sdk directly.