Aiven runs managed open-source data services — PostgreSQL, Kafka, ClickHouse, OpenSearch, Redis, and more — for many engineering teams. Connecting Aiven to clariBI surfaces your service inventory, schema, and health metrics into AI analyses.
Why connect Aiven
Aiven dashboards show service-level health well but cross-service questions ("which of our ClickHouse instances has the highest write throughput?") usually require multiple UI sessions or scripted CLI calls.
With Aiven connected, you can ask "Which services are running on Pro plans?", "What schemas exist in our analytics-pg-prod instance?", or "List PostgreSQL services by region" and the AI engine pulls the answer.
How the connection works
clariBI talks to Aiven through its hosted MCP server at https://mcp.aiven.live/mcp?read_only=true. 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 Aiven
U->>C: Click Authorize with Aiven
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 Aiven 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 Aiven cannot modify data on the vendor side.
The exact tool inventory depends on the Aiven features your account has access to. After connecting, try a few natural-language questions to see what Aiven data clariBI can pull.
Data flow during analysis
When you ask a question that maps to Aiven, 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 Aiven
U->>C: Ask a question about managed data-service inventory and schema
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 Aiven card.
- Click Authorize with Aiven.
- Sign in to Aiven 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 + PKCE flow scoped read-only via the ?read_only=true query parameter on the MCP endpoint. clariBI cannot create, modify, or delete Aiven services through this connection. Disconnect from Aiven account settings or from clariBI Settings.
Troubleshooting
| Error | Cause | Fix |
|---|---|---|
| "Permission denied" on service operations | The OAuth token only granted read scopes — by design. | No fix needed; clariBI is read-only against Aiven by contract. |