Composio is the aggregator gateway that connects AI agents to 100+ SaaS tools through a single OAuth — GitHub, Slack, Notion, Linear, Google Sheets, and many more long-tail integrations. Connecting Composio to clariBI extends the catalog without requiring per-vendor wizards.
Why connect Composio
Some business data lives in tools clariBI has not yet added directly. Rather than wait for a dedicated catalog row, Composio gives the AI engine access immediately.
You can ask "Pull yesterday's Slack messages mentioning quota", "Read the launch checklist from my Notion page", or "Open issues in the engineering Linear project tagged P0" through one Composio connection.
How the connection works
clariBI talks to Composio through its hosted MCP server at https://connect.composio.dev/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 Composio
U->>C: Click Authorize with Composio
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 Composio 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 Composio cannot modify data on the vendor side.
The exact tool inventory depends on the Composio features your account has access to. After connecting, try a few natural-language questions to see what Composio data clariBI can pull.
Data flow during analysis
When you ask a question that maps to Composio, 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 Composio
U->>C: Ask a question about long-tail SaaS tool data (aggregator)
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 Composio card.
- Click Authorize with Composio.
- Sign in to Composio 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 Composio consent screen, and Composio re-authorises each downstream tool with its own OAuth or API-key flow inside the Composio dashboard. clariBI inherits whichever scopes you grant Composio for each underlying tool.
Troubleshooting
| Error | Cause | Fix |
|---|---|---|
| "Toolkit not connected" | You haven't connected the underlying SaaS tool inside Composio yet. | Open Composio dashboard, connect the tool you want to query, then re-run the analysis. |