Connect clariBI to Claude Desktop via MCP

Claude Desktop supports the Model Context Protocol (MCP) natively. Connect it to clariBI and you can ask Claude to list your dashboards, run analyses, generate reports, and check usage without leaving the chat surface.

Prerequisites

• A clariBI account on the Trial, Starter, Professional, or Enterprise tier.
• Claude Desktop installed (the latest build supports streamable HTTP transport).

Step 1. Mint an MCP API key

1. Sign in to clariBI.
2. Open Developer Portal → MCP Server → Clients & Keys.
3. Type a descriptive name (e.g. Claude Desktop) and click + Mint MCP API key.
4. Copy the key shown in the green banner. It starts with claribi_mcp_ and is only displayed once.

Step 2. Edit Claude Desktop's config

1. In Claude Desktop, open Developer Settings → Edit Config.
2. Add a claribi entry under mcpServers:

{
  "mcpServers": {
    "claribi": {
      "url": "https://claribi.com/mcp/v1/",
      "headers": {
        "Authorization": "Bearer claribi_mcp_<paste-your-key-here>"
      }
    }
  }
}

3. Restart Claude Desktop.

Step 3. Test the connection

In a new conversation, ask Claude:

List my clariBI dashboards.

Claude will surface the list_dashboards tool and ask permission to call it. Approve, and the results appear inline.

What can Claude do?

• list_dashboards / get_dashboard: read your dashboards.
• list_reports / get_report: read your reports.
• list_data_sources / get_data_source_schema: inspect connected sources.
• run_analysis: ask plain-English questions of your data (consumes AI credits).
• generate_report: kick off report generation.
• get_usage / get_billing_status: check tier limits.
• create_checkout_session: get a Stripe upgrade URL Claude can hand you.

Switch to OAuth (optional but recommended for shared workspaces)

OAuth 2.1 with Dynamic Client Registration lets each user authenticate individually rather than sharing one API key. Claude Desktop initiates the flow automatically when you remove the headers block from the config and restart. You will be redirected to clariBI's consent screen on first use.

Troubleshooting

• "MCP server not responding": confirm the URL is exactly https://claribi.com/mcp/v1/ with the trailing slash.
• "401 Unauthorized": the key may have been revoked. Mint a new one in the developer portal.
• "403 Forbidden": your subscription doesn't include MCP server access. Trial, Starter, Professional, and Enterprise all do; Free and Lite do not.