MCP Server Overview

The clariBI MCP Server lets external LLM clients (Claude Desktop, Cursor, ChatGPT custom GPTs, and any spec-compliant agent) work with your clariBI workspace through the Model Context Protocol. Users can sign up, list dashboards, run analyses, and generate reports without leaving the chat surface.

What is MCP?

The Model Context Protocol is an open spec that lets LLM clients call structured tools and read structured resources from external servers. clariBI runs both halves of the protocol:

• Inbound integration: clariBI consumes vendor MCP servers (Stripe, HubSpot, Linear, and 25 more) as tools during AI analysis. Documented separately under data sources.
• Outbound server: clariBI itself acts as an MCP server. This is what this section documents.

What can my LLM client do?

Once connected, the LLM client can call these clariBI tools on the user's behalf:

• List and read dashboards.
• List and read reports.
• List data sources and inspect their column schemas.
• Run conversational analysis against connected data (consumes AI credits).
• Generate new reports.
• Check AI credit usage and billing status.
• Create a Stripe Checkout URL to upgrade the subscription.

Unauthenticated users get three public tools as well: register_account, verify_email, and check_pricing. A new user can sign up to clariBI entirely from inside their LLM client (see Sign up via LLM).

Quick start

Option A: API key paste

1. Sign in at claribi.com/app/login.
2. Open Settings > Developer > MCP Server and click Mint MCP API key.
3. Copy the key (starts with claribi_mcp_). It is shown once.
4. Paste it into your LLM client's MCP server config under Authorization: Bearer <key>.

Option B: OAuth 2.1

Spec-compliant clients can register dynamically. Point them at https://claribi.com/mcp/v1/ and the rest is automatic. The first request walks the user through a consent screen in their browser. See Authentication for details.

URL structure

Transports

Two transports are supported on the same URL:

• Streamable HTTP (current spec, version 2025-03-26): one URL, POST sends a JSON-RPC request, the response is either JSON or an SSE upgrade. Session continuity via the Mcp-Session-Id header.
• Server-Sent Events (legacy, version 2024-11-05): GET opens a long-lived event channel. Use this only if your client cannot speak streamable HTTP.

Tier gating

Outbound MCP access is included on Trial, Starter, Professional, and Enterprise plans. Free and Lite plans do not include it. register_account, verify_email, and check_pricing work without a subscription. See pricing.