One protocol. Thirty vendors. Zero developer setup.
clariBI talks to Stripe, HubSpot, Linear, Notion, GitHub, Atlassian, PostHog, Klaviyo, Sentry, Vercel, Supabase, Airtable, Mixpanel, Amplitude, Intercom and 15 more — all through the open Model Context Protocol. One click to connect. Read-only. Tokens encrypted at rest.
Stripe
HubSpot
Linear
Notion
GitHub
Atlassian
HubSpotWhat is MCP, and why is it different?
The Model Context Protocol is an open standard that lets AI tools talk to external systems through a single, well-defined wire protocol. Instead of clariBI maintaining 30 bespoke clients — each with its own auth flow, rate limits, retries and edge cases — every MCP-capable vendor exposes its capabilities the same way. We add a vendor by adding a row, not by writing a client.
Vendors slot in fast
When a new vendor adds an MCP server, clariBI adds support in days — not quarters. The catalog is a list of rows, not a stack of clients.
One auth flow, every vendor
OAuth 2.1 with Dynamic Client Registration. clariBI registers itself with each MCP server. You click "Connect", you don't fill out a developer console.
AI sees the right tools
When you ask "What was MRR last quarter?", the AI engine picks the right Stripe tool, runs it, and shows you the answer. You don't choose endpoints — clariBI does.
Connect a vendor in three steps
No developer console, no API keys, no copy-pasting tokens. Pick a vendor, authorize on their screen, ask questions.
Pick from the catalog
Open /integrations or the in-product Data Sources page. Each MCP-enabled vendor shows a "Live via MCP" badge.
Authorize on the vendor's screen
You're redirected to Stripe (or HubSpot, or Linear, etc.). You approve read-only access. The vendor sends a token back to clariBI.
Ask questions, get answers
Type a question in Conversational Analytics. The AI engine picks the right MCP tool, runs it, and shows you the result with a chart.
The catalog today — 30+ vendors and growing
Every card below is a live MCP connection: click "Connect" in clariBI, authorize on the vendor, and you're ready to ask questions.
Payments & Finance
CRM & Customer Success
Product Analytics & Observability
PostHog
Mixpanel
Sentry
CloudflareProject Management & Knowledge
Linear
Atlassian
Asana
Notion
AirtableDeveloper Tools & Infrastructure
GitHub
Vercel
Supabase
NeonContent, Storage & Marketing
Box
Egnyte
Webflow
Wix
Cloudinary
Mailchimp
Shopify StorefrontThe catalog is alive — see the in-product Data Sources page or the /integrations directory for the current list.
Read-only by design. Encrypted by default.
Every MCP connection asks for the narrowest scope set the vendor exposes — read records, search, list, fetch. clariBI never asks for write, modify or delete, and the AI engine has no path to call a tool that isn't in the read-only allowlist for that vendor.
OAuth tokens are encrypted at rest with Fernet (AES-128-CBC + HMAC-SHA256). Decryption only happens server-side at request time, and tokens never reach the browser. Disconnecting a vendor purges its stored credentials in one transaction.
Read-only scopes only
clariBI requests only the read scopes the vendor exposes. Write scopes are blocked at the tool allowlist layer.
Encrypted credentials
Fernet (AES-128-CBC + HMAC-SHA256) at rest. Tokens stay server-side and never leave clariBI in clear form.
Per-organization isolation
Each organization's MCP connections are scoped to that organization. Cross-tenant access is structurally impossible.
One-click disconnect
Disconnecting a vendor purges its stored credentials in a single transaction. The vendor's data drops off the analysis surface immediately.
Frequently asked questions
What is MCP and why does it matter?
MCP — the Model Context Protocol — is an open standard for connecting AI tools to live external systems. clariBI uses it to connect to vendors like Stripe, HubSpot, Linear, Notion, GitHub and 25 more without writing or maintaining a custom client for each one. One protocol means new vendors slot in within days, not quarters.
Do I have to register a developer app to use an MCP integration?
No. clariBI uses OAuth 2.1 with Dynamic Client Registration, which means our platform registers itself with each MCP server automatically. You click "Connect Stripe" (or HubSpot, or Linear, etc.), authorize on the vendor's screen, and you're done. No developer console, no API keys, no copy-pasting tokens.
Can clariBI change my data through an MCP connection?
No. All MCP connections are read-only. clariBI requests scopes that let it list, search and read records, and nothing that lets it create, modify or delete. Your vendor remains the system of record.
How are credentials stored?
OAuth tokens are encrypted at rest with Fernet (AES-128-CBC + HMAC-SHA256) before they touch the database. Decryption only happens server-side at request time. Tokens never leave clariBI in clear form and are never exposed to the browser.
Which subscription tiers include MCP integrations?
MCP integrations are available on Trial, Starter, Professional and Enterprise. Free and Lite tiers can use native OAuth connectors and CSV uploads, but the MCP catalog requires Starter or higher (or an active trial). See pricing for the full feature matrix.
Is there a vendor I want that's not in the catalog yet?
If the vendor offers an MCP server, we can usually add it in a few days. Let us know which vendor you need and we'll prioritize it. If the vendor doesn't have an MCP server yet, you can still upload data via CSV or connect a SQL database in the meantime.
Learn more
Native & CSV integrations
OAuth connectors for Google Analytics, Meta Ads, Jira and your databases — plus the file-upload route.
Conversational analytics
Ask a question in plain English. clariBI picks the right MCP tool, runs it, and shows the answer.
Enterprise security
Encryption at rest, RBAC, audit logs, and the security model behind every connection.
Connect your first MCP vendor in under a minute
14-day free trial. No credit card. 50 AI credits, the full MCP catalog, and every native connector unlocked.