How to build Vercel dashboards in Metabase

Vercel is a frontend cloud platform for deploying and hosting web applications, with builds, previews, and edge infrastructure. Metabase is where you turn those operational signals into shared, trustworthy dashboards. This guide covers two complementary paths: a lightweight MCP + CLI route that pulls live data with the Vercel MCP and loads a CSV into Metabase with the Metabase CLI, and a durable pipeline route that syncs Vercel rollups into a database so you can build dashboards anyone can read.

How do you connect Vercel to Metabase?

Most teams combine both routes: use MCP and CLI uploads for a fast first pass, then move recurring reliability reporting to a warehouse-backed model.

What can you analyze from Vercel data in Metabase?

• Deployment frequency and failures — built from deployments and the related builds, checks, projects data your sync exposes.
• Build duration trends — built from deployments and the related builds, checks, projects data your sync exposes.
• Preview vs. production activity — built from deployments and the related builds, checks, projects data your sync exposes.
• Project delivery health — built from deployments and the related builds, checks, projects data your sync exposes.
• Error and rollback correlation — built from deployments and the related builds, checks, projects data your sync exposes.

Which Vercel dashboards should you build in Metabase?

How do you use the Vercel MCP with the Metabase CLI?

Pair the Vercel MCP with the Metabase CLI for fast, hands-on analysis. MCP is useful for scoped lookups and summarized exports; the Metabase CLI's upload command loads CSV data into Metabase and creates a ready-to-query table and model.

Example workflow

• Ask the MCP server for the latest deployments with status, environment, and build duration.
• Export the result as CSV, keeping stable IDs, services, environments, severities, and timestamps.
• Run mb upload csv to load it into Metabase as a table and model, then build questions and dashboards on top.

Be honest about the limits

• MCP lookups are excellent for exploration, not scheduled reporting.
• A CSV upload is a snapshot; refresh it with mb upload replace or move to the pipeline for real history.
• Deployment timestamps and statuses are required for frequency and failure trends.
• mb upload csv needs an uploads database configured under Admin → Settings → Uploads.

How do you set up Vercel MCP and the Metabase CLI?

{
  "mcpServers": {
    "vercel": {
      "url": "https://mcp.vercel.com"
    }
  }
}

Only Vercel-approved clients (Claude, Cursor, ChatGPT, VS Code, and others) can connect; the OAuth grant carries your user's access, so scope it deliberately.

# 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 a deployments export — creates a table AND a model
mb upload csv --file vercel-deployments.csv --collection root

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

Can you generate a Vercel dashboard with AI?

Yes. Use the prompt below with any assistant that can run the Vercel MCP and the Metabase CLI. It works end to end: if Vercel tables already exist in Metabase it analyzes those; otherwise it pulls scoped, summarized data over MCP, loads it with mb upload csv, then builds the dashboard and caveats any metric that needs missing history.

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

Goal: Help engineering and operations leaders understand deployment frequency, build performance, preview flow, and release quality from Vercel data.

Step 1 — Find or load the data:
- First, check what already exists in Metabase (search for vercel tables and
  models). If durable Vercel data is already present — synced from a warehouse
  or uploaded earlier — use it and skip to Step 2.
- If nothing is there, pull a scoped, summarized export with the Vercel MCP:
  deployments, plus builds, checks, projects.
  Prefer aggregated or rollup views over raw events. 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 or column names. Inspect available fields, services,
environments, timestamps, and whether rollups or history exist before creating
duration or trend cards.

Important:
- Build on whatever data is present; don't claim Metabase connects natively to
  Vercel — it reads a database or CLI-uploaded tables.
- Never try to load the raw event firehose into Metabase; use rollups, entity
  tables, and incident- or group-grain data.
- Only compute durations (MTTA, MTTR, time-to-resolve) when the required
  timestamps exist.
- Exclude test, staging, or muted objects from headline reliability cards, and
  segment by environment where the field exists.
- A single CSV is a point-in-time snapshot: only build trend cards if there is a
  usable date column or multiple periods have been uploaded.

Dashboard title: Vercel Deployment Analytics Overview

Sections:
1. Executive summary: Production deploys last 30 days; Failed deploys; Median
   build duration; Active projects; Change failure rate.
2. Deployment health: Deploys by week and project; failed/canceled deploys.
3. Build performance: Median and p95 build duration by week and project.
4. Preview flow: Preview vs production deploys; time from preview to production.
5. Release quality: Rollbacks/redeploys; failed checks per deployment.

Filters: Date range, Service, Environment, Severity, Team, Status.

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.

How do you sync Vercel data into a database or warehouse?

For dashboards that need history and reliability, land Vercel rollups and metadata in a database first, then connect Metabase to that database.

Connector options

• Managed ETL — use a connector when one covers the objects you need.
• Custom pipeline — use the Vercel REST API for control over rollup grain, fields, and refresh cadence.
• MCP + CSV — use this for quick exploration and one-off slices.

Sync deployments, builds, and projects with the Airbyte Vercel source or scripts against the Vercel REST API; Fivetran covers it via a Connector SDK example rather than a managed connector.

Notes

• Decide the rollup grain first (hourly or daily per service/environment) — it drives warehouse cost and every trend card.
• Land raw entity tables first, then build clean Metabase models on top.
• Normalize project, environment, deploy status, build-duration, and deployed-at fields.

How should you model Vercel data in Metabase?

Core tables

Modeling advice

• Build a clean deployments model with common columns across tools, so multi-source dashboards don't fork definitions.
• Separate entity tables (services, monitors, policies) from time-series rollups and event-grain tables.
• Exclude test, staging, and muted objects from headline reliability metrics; keep environment as an explicit column.
• Use stable IDs for service, team, and incident joins; display names change.

Which Vercel metrics should you track in Metabase?

What SQL powers Vercel dashboards in Metabase?

These assume a cleaned analytical model in a warehouse (PostgreSQL dialect). Adjust table and column names to match your pipeline.

SELECT
  date_trunc('week', deployed_at) AS week,
  COUNT(*) AS deployments,
  COUNT(*) FILTER (WHERE status IN ('failed', 'rolled_back')) AS failed,
  ROUND(
    100.0 * COUNT(*) FILTER (WHERE status IN ('failed', 'rolled_back'))
    / NULLIF(COUNT(*), 0), 1
  ) AS change_failure_rate
FROM deployments
WHERE environment = 'production'
GROUP BY 1
ORDER BY 1;

SELECT
  date_trunc('week', deployed_at) AS week,
  percentile_cont(0.5) WITHIN GROUP (
    ORDER BY build_duration_seconds
  ) AS median_build_seconds,
  percentile_cont(0.95) WITHIN GROUP (
    ORDER BY build_duration_seconds
  ) AS p95_build_seconds
FROM deployments
WHERE status = 'success'
GROUP BY 1
ORDER BY 1;

SELECT
  date_trunc('week', deployed_at) AS week,
  COUNT(*) FILTER (WHERE environment = 'production') AS production_deploys,
  COUNT(*) FILTER (WHERE environment <> 'production') AS preview_deploys
FROM deployments
WHERE status = 'success'
GROUP BY 1
ORDER BY 1;

What are common mistakes when analyzing Vercel in Metabase?

Related

Related analytics

Related dashboards

Related integrations

FAQ