Sign up from an AI assistant

You can create a clariBI account without leaving your MCP client. The client calls two tools that need no account, register_account and verify_email, and ends up with a key it can keep using.

How it works

1. The client calls register_account with your email, an organization name and accept_terms: true (you agree to the terms and privacy policy).
2. clariBI emails you a 6-digit code. The signup request is valid for 10 minutes.
3. You give the code to the assistant, and choose a password of at least 8 characters.
4. The client calls verify_email with the pending_id, the code and the password.
5. clariBI creates your user and organization on the 14-day Trial and returns an access token valid for 1 hour plus an MCP API key for the client's configuration.

Requests

register_account

POST /mcp/v1/
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "register_account",
    "arguments": {
      "email": "alex@example.com",
      "organization_name": "Example Analytics",
      "first_name": "Alex",
      "last_name": "Doe",
      "accept_terms": true
    }
  }
}

The structuredContent of the result contains pending_id, next_step (verify_email) and expires_in_seconds.

verify_email

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "verify_email",
    "arguments": {
      "pending_id": "<pending_id>",
      "code": "428193",
      "password": "a-long-password"
    }
  }
}

On success structuredContent contains:

{
  "access_token": "claribi_mcp_tok_...",
  "token_type": "Bearer",
  "expires_in": 3600,
  "scope": "dashboards:read reports:read data-sources:read data-sources:write usage:read analysis:run forecasts:read",
  "mcp_api_key": "claribi_mcp_...",
  "mcp_api_key_id": "...",
  "user_id": "...",
  "organization_id": "...",
  "tier": "trial",
  "next_steps": ["Paste the mcp_api_key into your LLM client's MCP server config", "..."]
}

What the Trial includes

When the trial ends the organization moves to the Free plan: data and data sources stay, AI credits stop.

What still needs a browser

• Payment. create_checkout_session returns a Stripe Checkout link; you pay in the browser.
• Approving Google, Meta, Jira or Confluence access. The assistant can start it with request_oauth_integration_url, but you click Allow in the browser.
• Databases and API connectors that need credentials, and account settings. Sign in at claribi.com/app/login.

Files and public URLs can be loaded straight from the chat. See Loading data through MCP.

Abuse limits and privacy

• At most 5 signups per hour from one IP address, and one pending code per email address at a time (a new code after 60 seconds).
• After 5 wrong codes the request is locked; call register_account again.
• Email addresses with a + alias are refused.
• The answer does not reveal whether an email already has an account.
• The verification code is stored only as a hash.

Next

Put the key into your client: Claude Desktop, Cursor, or any client that follows MCP authentication.