vibe-demo-accelerator

Vibe Demo Accelerator

Reusable accelerator for building customer demos on Databricks. Clone this repo once, point vibe at it, and have a fully deployed demo in 2-4 hours.

What's inside: Battle-tested backend wiring (Lakebase auth/retry, MAS SSE streaming, health checks, action cards) extracted from production demos. You get the hard infrastructure for free — vibe generates the customer-specific story, UI, and data model.

Stack: FastAPI + Delta Lake + Lakebase (PostgreSQL) + MAS Agent Bricks + Genie Space + Databricks Apps. 100% serverless.

Prerequisites

You must use this scaffold through Vibe agent (the Databricks enterprise Claude Code environment). Personal Claude Code subscriptions won't have the required plugins and internal MCP tools.

1. Vibe agent

Vibe is the Databricks Field Engineering wrapper around Claude Code. It provides the enterprise plugins (Salesforce, Glean, Slack, Jira, Google Workspace) and internal MCP servers that the /new-demo wizard uses for customer research.

# Install vibe (if not already installed)
# Follow instructions at: https://github.com/databricks-field-eng/vibe

# Verify it works
vibe agent

After installation, run vibe agent once and follow the setup prompts. This will:

• Create ~/.vibe/profile with your SA identity
• Install enterprise plugins to ~/.vibe/marketplace/
• Configure MCP servers for Glean, Slack, Jira, and Confluence in ~/.claude/mcp.json
• Set up Chrome DevTools MCP for UI testing

2. Databricks AI Dev Kit

The AI Dev Kit provides the Databricks MCP server — this is how vibe creates Genie Spaces, runs SQL, deploys apps, and manages Lakebase programmatically.

# Clone and install
git clone https://github.com/databricks-solutions/ai-dev-kit.git ~/ai-dev-kit
cd ~/ai-dev-kit
python -m venv .venv
source .venv/bin/activate
pip install -e databricks-mcp-server/

# Verify the MCP server can start
python databricks-mcp-server/run_server.py --help

The global MCP config (~/.claude/mcp.json) should already reference this after vibe setup. If not, add:

{
  "mcpServers": {
    "databricks": {
      "command": "~/ai-dev-kit/.venv/bin/python",
      "args": ["~/ai-dev-kit/databricks-mcp-server/run_server.py"],
      "env": { "DATABRICKS_CONFIG_PROFILE": "DEFAULT" }
    }
  }
}

3. Databricks CLI

The CLI is used for workspace authentication and direct operations (Lakebase psql, app deployment, resource management).

# Install (if not already installed)
brew install databricks/tap/databricks

# Authenticate with a workspace
databricks auth login https://fe-sandbox-serverless-<name>.cloud.databricks.com --profile=<name>

# Verify
databricks current-user me --profile=<name>

You'll create a workspace-specific profile during the /new-demo wizard (Phase 2). If you don't have a workspace yet, the wizard will guide you through creating one via FEVM.

4. Verify everything

Run these checks before starting your first demo:

# Vibe agent starts and shows enterprise plugins
vibe agent
# You should see fe-databricks-tools, fe-salesforce-tools, etc. in the skill list

# Databricks CLI is authenticated
databricks current-user me --profile=<your-profile>

# AI Dev Kit MCP server exists
ls ~/ai-dev-kit/databricks-mcp-server/run_server.py

What each component provides

Component	What it gives the scaffold	Without it
Vibe agent	Enterprise plugins (Salesforce, Glean, Slack), internal MCP servers, SA identity	Phase 1 research is limited to web search only — no Salesforce UCO lookup, no internal Slack/Glean search
AI Dev Kit	Databricks MCP tools (execute_sql, create apps, manage Genie/MAS)	Phase 8 deployment must be done manually via CLI commands
Databricks CLI	Workspace auth, Lakebase psql, app deployment, resource management	Can't authenticate or run deployment commands

Quick Start

1. Clone the scaffold (one-time)

git clone https://github.com/databricks-field-eng/vibe-demo-accelerator.git ~/vibe-demo-accelerator

Pull updates anytime with git pull.

2. Open vibe in the scaffold directory

cd ~/vibe-demo-accelerator
vibe agent

Important: Open vibe from the scaffold directory — the /new-demo slash command lives in .claude/commands/ and is only visible when vibe is opened here.

3. Run the setup wizard

/new-demo

The wizard walks you through 9 phases (Phase 0-8) — from project setup to deployed app — all within a single command: