Axiom is the observability platform many engineering teams use to centralise logs, traces, and metrics. Connecting Axiom to clariBI surfaces every dataset and APL query as a tool for incident analysis and reliability questions.
Why connect Axiom
Incident questions ("what changed between 13:42 and 13:58?") usually mean opening Axiom's console and writing APL by hand. With Axiom connected the AI engine writes APL itself, runs it, and summarises results.
You can ask "Top 10 error messages from the api-prod dataset last hour", "Compare request latency this week vs last week", or "Show traces with status >= 500 in the last 24h" and the AI engine routes through Axiom.
How the connection works
clariBI talks to Axiom through its hosted MCP server at https://mcp.axiom.co/mcp. Authentication uses an OAuth flow that clariBI registers itself for (no developer console setup on your side). Tokens stay encrypted server-side and never leave clariBI in clear form.
sequenceDiagram
actor U as You
participant C as clariBI
participant V as Axiom
U->>C: Click Authorize with Axiom
C->>V: Open OAuth authorization
V-->>U: Grant read access?
U->>V: Approve
V-->>C: Authorization code
C->>V: Exchange code for tokens
V-->>C: Access + refresh tokens
C->>C: Encrypt and store credentials
C-->>U: Connection ready
Available tools
clariBI exposes the read-only Axiom tools that the vendor's MCP server publishes at connection time. Write operations (create, update, delete, send, refund) are filtered out by a name-pattern blocklist before any tool reaches the analysis engine, so connecting Axiom cannot modify data on the vendor side.
The exact tool inventory depends on the Axiom features your account has access to. After connecting, try a few natural-language questions to see what Axiom data clariBI can pull.
Data flow during analysis
When you ask a question that maps to Axiom, the AI engine routes to the right tool, reads the result, and pairs the answer with a chart you can pin to a dashboard.
sequenceDiagram
actor U as You
participant C as clariBI
participant AI as AI engine
participant V as Axiom
U->>C: Ask a question about observability logs, traces, and metrics
C->>AI: Plan the analysis
AI->>V: Call the right tool
V-->>AI: Tool result
AI->>AI: Summarize and chart
C-->>U: Answer plus visual
Setting up the connection
- Open Data Sources in the clariBI sidebar.
- Click Add data source.
- Open the MCP Servers tab.
- Click the Axiom card.
- Click Authorize with Axiom.
- Sign in to Axiom in the popup window and grant the requested read scopes.
- Back in clariBI, give your data source a name.
- Click Finish.
Permissions and data access
OAuth scoping is granted at authorize time on the Axiom consent screen. clariBI requests read-only access to datasets and APL execution — no datasets can be created, modified, or deleted. Disconnect from Axiom settings or from clariBI Settings.
Troubleshooting
| Error | Cause | Fix |
|---|---|---|
| "Organization selection missing" | Your Axiom account has multiple organizations. | Pick one organization in Axiom before authorizing, or reconnect and select the right org on the consent screen. |