What You Can Do
The things Auron can answer or act on from inside a Claude conversation.
Rather than exposing one fixed tool per feature, Auron in Claude exposes the same REST API described in its OpenAPI document through a small, general-purpose toolset. Claude looks up what's available, finds the right endpoint for what you asked, and calls it with your authorized token attached automatically.
In practice, that covers
Reading conversations, meetings, entities and records, knowledge, signals, and organization data, scoped to whatever was granted when you connected. Writing updates to records, and anything else your granted scopes allow, the same as if you'd made the change from the console or the app. And reasoning over real context: because Claude can pull real organizational data mid-conversation, it can answer questions grounded in what Auron actually knows instead of just what's in the current chat.
What it will not do
It won't reach past whatever scopes were granted at connection time, and it won't do anything Auron itself doesn't support through its API. Claude is a client of Auron's data here, not a separate system with its own rules.
Because the toolset tracks the API instead of a fixed feature list, what's available here grows as the API does, with no separate Claude-specific release needed.