How to build Alguna billing dashboards in Metabase

# Alguna (remote via mcp-remote bridge)
claude mcp add alguna -- npx -y mcp-remote https://api.alguna.io/mcp \
  --header "Authorization: Bearer <YOUR_ALGUNA_API_KEY>"

{
  "mcpServers": {
    "alguna": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://api.alguna.io/mcp",
        "--header", "Authorization:Bearer ${ALGUNA_API_KEY}"
      ],
      "env": { "ALGUNA_API_KEY": "<YOUR_ALGUNA_API_KEY>" }
    }
  }
}

# Install the Metabase CLI
npm install -g @metabase/cli

# Log in (opens your browser; requires Metabase v62+)
mb auth login --url https://your-metabase.example.com

# Load an Alguna CSV export — creates a table AND a model
mb upload csv --file alguna-invoices.csv --collection root

# Refresh that same table later from a new export
mb upload replace <table-id> --file alguna-invoices.csv

Create a polished Metabase dashboard for Alguna billing analytics.
Work end to end: get the data into Metabase if it isn't there yet, then build.

Goal: Help finance and RevOps leaders understand committed and usage-based
revenue, invoicing, accounts receivable, and quote-to-cash from Alguna data.

Step 1 — Find or load the data:
- First, check what already exists in Metabase (search for Alguna tables and
  models). If durable Alguna data is already present — synced from a warehouse or
  uploaded earlier — use it and skip to Step 2.
- If nothing is there, pull it with the Alguna MCP server using a read-only API
  key: customers, quotes, contracts, subscriptions, usage measurements, and
  invoices. Write each result to a CSV, then load it with the Metabase CLI — run
  "mb upload csv --file <export>.csv" so each upload creates a table and a
  ready-to-query model. Use "mb upload replace <table-id> --file <export>.csv" to
  refresh an existing table instead of creating duplicates.

Step 2 — Inspect before querying:
Do not assume exact table names. Map the available raw tables into these
analytical concepts where possible: Customers, Quotes, Contracts, Subscriptions,
Products/Prices, Usage measurements (metering), Invoices, Invoice line items, and
Payments. Inspect the actual tables and column names first.

Important:
- Build on whatever data is present; don't claim Metabase connects natively to
  Alguna — it reads a database or CLI-uploaded tables.
- Separate committed recurring revenue (MRR/ARR) from usage-based (metered)
  revenue and overages; document the rating logic.
- For AR, compute DSO and aging from open invoices, not paid ones.
- Report revenue in a single reporting currency.
- Only build a card if its underlying column/metric exists in the data.
- A single CSV is a point-in-time snapshot: MRR movement and AR trends need
  history, so build trend cards only if a warehouse sync or multiple uploads
  provide it.

Dashboard title: Alguna Billing Overview

Sections:
1. Executive summary (KPI cards): Committed MRR; ARR; Usage revenue this month;
   Invoiced revenue; Accounts receivable; DSO.
2. Committed & usage revenue: Committed vs. usage split; Net new MRR; Usage
   revenue trend.
3. Invoicing & AR: Invoiced revenue; AR aging buckets; Overdue invoices.
4. Quote-to-cash: Quotes issued/accepted/win rate; Quote-to-cash cycle time;
   Bookings by pricing model.
5. Usage & metering: Metered usage over time; Customers near a committed
   threshold; Overage revenue.

Filters: Product, Pricing model, Customer segment, Currency, Date range.

Reuse the models Metabase auto-created from uploaded CSVs, or (for a warehouse)
create reusable models: modeled_alguna_contracts, modeled_alguna_usage,
modeled_alguna_invoices, and modeled_alguna_mrr (a monthly committed-MRR model).

Output: Build the dashboard if you have permission; otherwise provide the exact
questions, SQL, model definitions, and layout. Include caveats for any metric
that cannot be calculated from the available data. Reconcile totals against the
Alguna dashboard. Keep it practical, dense, and executive-readable. Avoid vanity
metrics.

Recurring commitment from active contracts.

-- Committed MRR/ARR from a monthly committed-MRR model
SELECT
  ROUND(SUM(committed_mrr), 2)       AS committed_mrr,
  ROUND(SUM(committed_mrr) * 12, 2)  AS committed_arr,
  COUNT(*)                           AS active_contracts
FROM modeled_alguna_mrr
WHERE month = date_trunc('month', CURRENT_DATE);

Open receivables bucketed by days past due.

-- AR aging from open invoices
SELECT
  CASE
    WHEN CURRENT_DATE - due_date <= 0  THEN 'current'
    WHEN CURRENT_DATE - due_date <= 30 THEN '1-30'
    WHEN CURRENT_DATE - due_date <= 60 THEN '31-60'
    WHEN CURRENT_DATE - due_date <= 90 THEN '61-90'
    ELSE '90+'
  END                                        AS aging_bucket,
  COUNT(*)                                   AS invoices,
  ROUND(SUM(amount_due) / 100.0, 2)          AS open_amount
FROM invoices
WHERE status IN ('open', 'overdue')
GROUP BY 1
ORDER BY MIN(CURRENT_DATE - due_date);

Rated metered consumption over the last year.

-- Metered usage revenue by month
SELECT
  date_trunc('month', measured_at) AS month,
  meter_name,
  ROUND(SUM(rated_amount) / 100.0, 2) AS usage_revenue
FROM usage_measurements
WHERE measured_at >= CURRENT_DATE - INTERVAL '12 months'
GROUP BY 1, meter_name
ORDER BY 1, usage_revenue DESC;