clariBI MCP Server

com.claribi/mcp-server

answering

clariBI is answering right now. Last checked 11 min ago. It exposes 26 tools.

AI business intelligence: sign up, ingest data, run analyses, generate reports from any MCP client.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 41 hours of history

41 hours agonow

100.0%

Uptime 24h

182 of 182 checks

Tools

read from the server

231 ms

Response time

average over 24h

open, no key

Access

streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp-server --transport http https://claribi.com/mcp/v1/

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://claribi.com/mcp/v1/"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mcp-server]
url = "https://claribi.com/mcp/v1/"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://claribi.com/mcp/v1/"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://claribi.com/mcp/v1/"
    }
  }
}

Available tools 26

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

forecast

create_forecast

Bind a forecast to a metric in your workspace. Stores the configuration, sets up the schedule, and resolves the source binding immediately so a bad source_id or metric_path errors out before any credits are spent. Run the forecast with run_forecast.

get_forecast

Fetch one forecast configuration by ID.

get_forecast_run

Fetch one run of a forecast by ID, or pass run_id="latest" for the most recent run. Returns the full forecast envelope: target series + 30-day projection, correlated drivers (with lag and bootstrap stability), anomalies, structural changes, and credit accounting.

get_forecast_trust

Returns per-past-run accuracy for a forecast. Each row compares a prior run's projection against the actuals that have materialized since. Use this to see whether your forecasts have been getting MORE or LESS accurate over time, or to spot when a backtest sMAPE was systematically optimistic vs. realised performance.

run_forecast

Run a forecast now. Reserves AI credits up front, dispatches the backtest + projection + correlation pipeline, and returns either the completed result inline (wait_seconds > 0 and the run finishes in time) or a run_id you can poll with get_forecast_run.

analysis

get_analysis_status

Check the status of a previously-dispatched run_analysis job. Returns the analysis result if completed.

run_analysis

Run a natural-language analytics question against your connected data sources. Consumes AI credits. Returns either the completed analysis result inline OR a job_id you can poll with get_analysis_status. If list_data_sources returns an empty list, ingest data first with upload_data_source (inline base64), ingest_url_data_source (public URL), or request_oauth_integration_url (Google / Meta / Jira / Confluence).

data

get_data_source_schema

Fetch the column schema for a data source. Useful before asking run_analysis about specific columns. The schema is derived from the preprocessing metadata clariBI extracted when the source was last synced. Poll this after upload_data_source / ingest_url_data_source until the returned status flips to "active" — that means preprocessing has finished and run_analysis will see the data.

list_data_sources

List the data sources connected to your clariBI organization. Returns id, name, source_type, status, last sync time, and the number of rows (when known).

billing

get_billing_status

Get the organization's billing status — tier, renewal date, and upgrade options.

checkout

create_checkout_session

Create a Stripe Checkout URL the user can open in a browser to upgrade their clariBI subscription. Payment cannot happen inside the LLM; this tool returns a URL.

dashboard

get_dashboard

Fetch one dashboard by ID. Includes widget definitions, the most recent refresh data, and the web URL.

dashboards

list_dashboards

List dashboards in your clariBI organization. Returns id, name, status, last refresh, and a URL you can open in a browser.

forecasts

list_forecasts

List metric forecasts in your clariBI organization. Each row covers one metric: its source binding, horizon, schedule, and the latest run status. Use get_forecast_run to fetch the full forecast result.

generate

generate_report

Create a new generated report in your clariBI organization. Returns the report id you can poll via get_report, plus a download URL once status reaches "completed".

ingest

ingest_url_data_source

Create a new data source by fetching a public URL on the server side. Handles CSV, TSV, JSON, Excel, TXT, and PDF. Private networks (RFC 1918, loopback, cloud metadata) are blocked. Returns the data_source_id once preprocessing has started. Use this for files larger than the 25 MB inline upload cap.

integration

check_integration_status

Poll an OAuth handoff initiated by request_oauth_integration_url. Returns the current status (pending, connected, failed, expired) and, when connected, the data_source_id you can pass to run_analysis.

pricing

check_pricing

List clariBI subscription tiers with prices, AI credits, data source limits, user limits, and headline features. No authentication required.

regenerate

regenerate_forecast_narrative

Re-run ONLY the AI narration step against an existing completed forecast run. Costs 1-2 AI credits (no engine work). Returns the new narration; the old one is overwritten in the run record. Refuses when the run is not yet complete or when narration_enabled=false on the forecast.

register_account

Begin clariBI account signup. Validates the email + organization name, emails a 6-digit verification code, and returns a pending_id. Call verify_email(pending_id, code) within 10 minutes to finish signup and receive an API key.

report

get_report

Fetch one generated report by ID.

reports

list_reports

List generated reports in your clariBI organization. Returns id, title, status, output format, and download URL.

request

request_oauth_integration_url

Initiate an OAuth handoff to a vendor integration (Google Ads, GA4, Search Console, Sheets, Drive, BigQuery, Meta Ads, Jira, Confluence). Returns an authorization URL the user opens in a browser. After the user clicks Allow, the connection is created and you can poll check_integration_status(handoff_id) to find out when the data is ready.

upload

upload_data_source

Create a new data source from an inline base64-encoded file (CSV, TSV, JSON, Excel, TXT, PDF). The file goes through the same validation and preprocessing as a web upload. Returns the data_source_id you can pass to run_analysis as soon as preprocessing completes (poll get_data_source_schema for readiness or pass wait_seconds to block here).

usage

get_usage

Get the organization's current AI credit usage, data source count, user count, and rate-limit headroom.

verify

verify_email

Complete clariBI signup by submitting the verification code plus a password. Returns an OAuth access_token for immediate use AND a long-lived MCP API key for persistent configuration. The new organization lands on the Trial tier (50 AI credits, 14 days).

Endpoints

URL	Transport	State	Latency	Checked
https://claribi.com/mcp/v1/	streamable-http	answering	209 ms	11 min ago
https://claribi.com/mcp/v1/sse	sse	answering	216 ms	11 min ago

clariBI — questions

Answers built from our own checks of this server.

What can clariBI do?

It exposes 26 tools, read directly from the server on our last check. Among them: check_integration_status, check_pricing, create_checkout_session, create_forecast, generate_report, get_analysis_status and 20 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is clariBI mostly used for?

Its tools cluster around forecast, analysis and data. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is clariBI working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 182 of 182 checks got a reply (100.0%), average response time 231 ms. The bar chart above shows every period we have measured.

Is clariBI still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect clariBI?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does clariBI need an API key?

No. clariBI completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 26 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is clariBI?

It answers our handshake in 231 ms on average, which is faster than 56% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.