86 apps, one catalog: inside clariBI's MCP library

When this post first ran, the MCP catalog held about 30 vendors. Today it holds 86. This post is a tour of what is in it, how the pieces are grouped, which plan each one needs and what is still missing. If you want the background on the protocol itself first, read what MCP is and why clariBI uses it.

What "in the catalog" means

An app is in the catalog when the vendor runs its own MCP server and we have checked which of its tools only read data. That second part matters. clariBI uses read tools only (listing charges, deals, issues and so on). Tools that create, change or delete anything are filtered out before any call is made, so connecting an app never gives clariBI a way to change it.

Once an app is connected, clariBI reads it in two ways:

• On sync. clariBI calls the app's list tools, stores the rows and builds a dashboard for the source automatically. Those rows then feed dashboards, reports and forecasts like any other source.
• When you ask a question. In Ask clariBI, the question screen, it can also call the app's tools live and use the result in the answer.

The catalog is one of several ways to connect data. There are also 80 API connectors (Semrush, Zendesk, FRED and others) that use an API key, direct Google, Meta and Atlassian connections, databases and file uploads. The integrations overview shows all of them side by side.

The catalog by group

The grouping below is ours, to make the list readable. The plan in brackets is the lowest plan that can connect the app.

Payments, billing and spend

Stripe (payments, customers, subscriptions, invoices, disputes, payouts), PayPal (transactions and subscriptions), Square (payments, orders, customers, locations), Plaid (bank transactions and balances) and Ramp (cards, bills, reimbursements). All from the trial up. For most small businesses, Stripe is the first source to connect, because revenue questions start there.

CRM, sales and customer support

HubSpot, Attio and Intercom from the trial up. Pipedrive, Close CRM, Salesloft, Gong, Clay and Plain from Starter up. HubSpot covers contacts, companies, deals, tickets and marketing data; Gong reads call and deal data; Plain and Intercom read support conversations.

Email, forms and scheduling

Klaviyo from the trial up. Brevo, Ecomail, MailerLite, MailerSend, Mailchimp (through an Apify actor), Tally, Calendly and Cal.com from Starter up.

Product analytics, experiments and reliability

PostHog, Mixpanel, Amplitude, Statsig, DevCycle, Sentry, New Relic, Rootly, Cloudflare and Arcjet from the trial up. Axiom and Logfire (US and EU regions) from Starter up.

Projects, docs and design

Linear, Asana, monday.com, Notion, Airtable, the Atlassian server (Jira, Confluence and Compass), Canva, Lucidchart, Eraser, Box, Egnyte and Cloudinary, all from the trial up.

Developer platforms and databases

GitHub, Vercel, Supabase, Neon, Postman, Sanity, Webflow, Wix, Make and Hugging Face from the trial up. Aiven, InstantDB, Keboola, MotherDuck and Prisma Postgres from Starter up. dbt Cloud and Microsoft Dataverse need Professional.

Research, enrichment and web data

Explorium, DataForB2B, Generect, Clootrack, MetricSpot, AdButler, Pipeboard (Google Ads data), Apideck, 1stDibs and dm from the trial up. Apify, Exa, Tavily, Scrapfly, Composio, Two Minute Reports, Morningstar and Octagon from Starter up.

In total, 52 apps are available from the trial up, 32 more from Starter and 2 from Professional. The Free and Lite plans have no MCP access. The MCP integrations page keeps the current list with a page per vendor.

What is not in the catalog

Some gaps are worth knowing before you plan around the catalog:

• Shopify orders. Shopify Storefront reads a shop's public product catalog, not orders, customers or revenue. For sales data, use an order export or a sheet your store app keeps up to date.
• Salesforce and Slack. Neither is in the catalog today. Composio, an aggregator in the catalog, exposes Slack among many other tools, but it is a different connection with its own account.
• Accounting systems. There is no QuickBooks or Xero entry. Use exports.

If a vendor you need runs an MCP server that is not listed, Starter and higher plans can add a custom MCP server by URL with an API key or bearer token. Custom servers do not get an automatic dashboard.

A few vendors appear twice across the families. GitHub, Klaviyo and Mailchimp have both an MCP entry and an API connector, and you can use whichever suits your plan.

How to connect an app

1. Open Settings, then Integrations, and click Add Data Source.
2. Search for the vendor. MCP apps carry an MCP label.
3. Sign in or enter credentials. Most apps open the vendor's own sign-in window: you approve access and the window closes. clariBI registers itself with the vendor's server, so you do not create an app or copy client IDs. Some vendors ask for an API key instead, a few for an OAuth app's client ID and secret, and public servers need nothing.
4. If the vendor asks, pick an account, project or property. Name the source and save.

Credentials and tokens are encrypted before they are stored, and each connection belongs to one organization. An Owner or Administrator can disconnect an app, which erases the stored credentials and stops the sources built on it from syncing. The security model behind the MCP integrations goes into the details.

If a connection stops working later, the usual cause is a grant that was revoked or expired on the vendor's side. Connecting the vendor again with the same account fixes most of these; the help article on sync failures, expired access and rate limits covers the rest.

A first thing to try

Start a trial, connect Stripe from the catalog and wait for the first sync. Then open Ask clariBI and ask "What was revenue by month for the last six months?" The answer comes back as a chart and a table you can check against your Stripe dashboard. If it matches, add the next source you usually export by hand.