Setup Metabase Instance

Set Up a Local Metabase Instance

Read this entire skill file end-to-end before taking any action. Do not skim, do not stop at the first matching step, do not act on the summary alone. Prerequisite checks, launch sections, init gates, and post-setup handoff rules are scattered through the document; skipping ahead has repeatedly produced broken flows. Load the full text into context first, then start executing.

Follow these instructions exactly as written. Do not make assumptions, do not "be helpful" by overstepping, do not silently substitute "equivalent" actions for the ones specified. Every step, every verbatim message, every gate, and every prohibition is here because skipping or improvising on it has produced a known regression. If a step says "send this verbatim", send exactly that. If a step says "stop and wait", stop and wait. If a step says "do not call endpoint X", do not call X — even if the user asks you to. When in doubt, do less, not more.

When to Use

• User asks to start, launch, run, install, or set up a local Metabase instance.
• User asks to stop or check the status of a running Metabase instance.
• User needs a local BI/analytics dashboard for development, testing, or exploration.
• Trigger keywords: "metabase", "start metabase", "local metabase", "stop metabase", "metabase status".

Prerequisites

Network Access Required

This skill requires network access. All curl, java, and docker commands must be run outside the Codex sandbox. Request full network access or run outside the sandbox before attempting these commands. Do not run them inside the sandbox as they will fail.

Prerequisites Check (run in order, stop at first successful path)

1. Check for Java 21+

Expand PATH first to avoid the macOS stub at /usr/bin/java:

export PATH="/opt/homebrew/opt/openjdk/bin:/opt/homebrew/opt/openjdk@21/bin:/opt/homebrew/bin:/usr/local/opt/openjdk/bin:/usr/local/opt/openjdk@21/bin:/usr/local/bin:$PATH"
java -version 2>&1 | head -1

• If the output shows Java 21 or higher → use Section A (JAR). Keep this PATH export for all subsequent commands.
• If not found or version < 21 → check Docker (step 2).

Windows (PowerShell) note: On Windows hosts, check Java with java -version directly (no PATH export needed). If Java 21+ is installed and on PATH, proceed to Section A. If not, proceed to Docker.

2. Check for Docker

docker --version 2>&1

• If Docker is available: Use the Docker method (Section B).
• If neither Java 21+ nor Docker is available: Direct the user to install Docker:
  • macOS/Windows: Docker Desktop
  • Linux: Docker Engine
  • Tell them to re-run this skill after installing Docker.

Procedure

Section A: JAR Method (Java 21+)

A1. Check for existing Metabase directory

ls -la ./metabase 2>/dev/null

If ./metabase exists and contains files, ask the user:

A ./metabase directory already exists. Should I use it (preserving existing data) or remove it and start fresh?

If the user wants to start fresh:

rm -rf ./metabase

A2. Create directory and download JAR

mkdir -p ./metabase
curl -sL -o ./metabase/metabase.jar https://downloads.metabase.com/latest/metabase.jar

Tell the user this may take a minute (the JAR is ~400MB).

A3. Check if port 3000 is in use

lsof -i :3000 2>/dev/null | grep LISTEN

Windows (PowerShell) equivalent: Get-NetTCPConnection -LocalPort 3000 -ErrorAction SilentlyContinue

If the port is in use, ask the user:

Port 3000 is already in use. Would you like to use a different port?

• Suggest port 3001, 3002, etc.
• Store the chosen port as $PORT (default: 3000).

A4. Start Metabase in the background

Use the same PATH as in the Java prerequisite step when the agent uses a fresh shell (prepend the macOS Homebrew line again if unsure). Set JAVA_CMD=$(command -v java) after that export so you invoke the same binary you version-checked.

Prefer tmux for the JAR method when available. It is more reliable in Codex Desktop than plain nohup because it keeps the long-running Java process attached to a durable local session instead of depending on shell job-control behavior.

export PATH="/opt/homebrew/opt/openjdk/bin:/opt/homebrew/opt/openjdk@21/bin:/opt/homebrew/bin:/usr/local/opt/openjdk/bin:/usr/local/opt/openjdk@21/bin:/usr/local/bin:$PATH"
JAVA_CMD=$(command -v java)
PORT=${PORT:-3000}

if command -v tmux >/dev/null 2>&1; then
  tmux kill-session -t metabase-local 2>/dev/null || true
  tmux new-session -d -s metabase-local -c "$(pwd)/metabase" \
    "MB_DB_FILE=./metabase.db MB_JETTY_PORT=$PORT '$JAVA_CMD' -jar metabase.jar >> metabase.log 2>&1"
  echo "tmux:metabase-local" > ./metabase/metabase.pid
else
  (
    cd ./metabase
    MB_DB_FILE=./metabase.db MB_JETTY_PORT=$PORT \
      "$JAVA_CMD" -jar metabase.jar > metabase.log 2>&1 < /dev/null &
    echo $! > metabase.pid
  )
fi

Tell the user: "Metabase is starting in the background. I'll check when it's ready..."

Also mention:

• "View logs: tail -f ./metabase/metabase.log"
• If using tmux: "Attach to the session with tmux attach -t metabase-local"
• If using the direct background fallback: "The process ID is saved in ./metabase/metabase.pid"

Quick launch check — before polling for up to 2 minutes, verify the process/session hasn't already exited. If it has, inspect logs immediately and switch to Docker if the JAR launch is not recoverable:

sleep 2
if [ "$(cat ./metabase/metabase.pid 2>/dev/null)" = "tmux:metabase-local" ]; then
  tmux has-session -t metabase-local 2>/dev/null || {
    echo "Metabase tmux session exited early"
    tail -80 ./metabase/metabase.log
    exit 1
  }
else
  ps -p "$(cat ./metabase/metabase.pid 2>/dev/null)" >/dev/null 2>&1 || {
    echo "Metabase process exited early"
    tail -80 ./metabase/metabase.log
    exit 1
  }
fi

A5. Wait for Metabase to be ready

Poll the health endpoint every 5 seconds until it returns {"status":"ok"}:

curl -s http://localhost:$PORT/api/health

Keep polling until the response is {"status":"ok"}. Metabase usually starts within 30-60 seconds.

If the health check keeps failing after 2 minutes, check if the process is still running:

if [ "$(cat ./metabase/metabase.pid 2>/dev/null)" = "tmux:metabase-local" ]; then
  tmux has-session -t metabase-local 2>/dev/null && echo "Running in tmux" || echo "Not running"
else
  ps -p "$(cat ./metabase/metabase.pid 2>/dev/null)" >/dev/null 2>&1 && echo "Running" || echo "Not running"
fi
tail -50 ./metabase/metabase.log

Once healthy, tell the user: "Metabase is ready at http://localhost:$PORT"

Then proceed to Initialize Metabase (gates below).

Section B: Docker Method

B1. Check for existing Metabase directory

ls -la ./metabase 2>/dev/null

If ./metabase exists and contains files, ask the user:

A ./metabase directory already exists. Should I use it (preserving existing data) or remove it and start fresh?

If the user wants to start fresh:

rm -rf ./metabase

B2. Create directory for data persistence

mkdir -p ./metabase

B3. Check if port 3000 is in use

lsof -i :3000 2>/dev/null | grep LISTEN

Windows (PowerShell) equivalent: Get-NetTCPConnection -LocalPort 3000 -ErrorAction SilentlyContinue

If the port is in use, ask the user for an alternative port. Store as $PORT (default: 3000).

B4. Check for existing Metabase container

docker ps -a --filter "name=metabase-local" --format "{{.Names}} {{.Status}}"

If a container named metabase-local exists:

• If running: Ask if they want to stop it and start fresh, or keep using it.
• If stopped: Ask if they want to remove it and start fresh, or restart it.

To remove an existing container:

docker rm -f metabase-local 2>/dev/null

B5. Get the latest Metabase version

The latest tag on Docker Hub is often outdated. Get the actual latest version from GitHub:

curl -s https://api.github.com/repos/metabase/metabase/releases/latest | grep '"tag_name"' | head -1

This returns something like "tag_name": "v0.52.5". Extract the version (e.g., v0.52.5).

Verify the Docker image exists:

docker manifest inspect metabase/metabase:$VERSION 2>&1 | head -5

If it doesn't exist, fall back to latest.

B6. Start Metabase container

docker run -d \
  --name metabase-local \
  -p $PORT:3000 \
  -v "$(pwd)/metabase:/metabase.db" \
  -e MB_DB_FILE=/metabase.db/metabase.db \
  -e MB_JETTY_HOST=0.0.0.0 \
  -e MB_ENABLE_EMBEDDING_SDK=true \
  -e MB_ENABLE_EMBEDDING_SIMPLE=true \
  metabase/metabase:$VERSION

Windows (PowerShell) note: Replace $(pwd) with ${PWD} or the absolute path to the current directory when running in PowerShell.

Tell the user: "Metabase is starting via Docker. I'll check when it's ready..."

B7. Wait for Metabase to be ready

Poll the health endpoint every 5 seconds until it returns {"status":"ok"}:

curl -s http://localhost:$PORT/api/health

Keep polling until the response is {"status":"ok"}. Metabase usually starts within 30-60 seconds.

If the health check keeps failing after 2 minutes, check the container status and logs:

docker ps --filter "name=metabase-local" --format "{{.Status}}"
docker logs metabase-local 2>&1 | tail -50

Once healthy, tell the user:

• "Metabase is ready at http://localhost:$PORT"
• "View logs: docker logs -f metabase-local"

Then proceed to Initialize Metabase (gates below).

Initialize Metabase (Required — All Three Gates)

You MUST run the gates below in order. Do NOT report "Metabase is ready" until every gate passes. Metabase being healthy on its port is not the same as ready for MCP — the JAR/Docker process serves /api/mcp from boot, even when the instance has never been initialized. Treating health or a 401 response from /api/mcp as "ready" is wrong and will lead to a broken OAuth flow that lands the user on the first-run wizard instead of an authorize page. This has happened before. Do not do it.

Never automate Metabase configuration via REST. Do not call any of these endpoints:

• POST /api/setup — would create the admin account programmatically with credentials the user did not pick.
• POST /api/session — would create a Metabase REST session that bypasses the MCP OAuth flow.

The user must drive setup in the browser. You only run the read-only verification curls below. Even if the user explicitly asks you to automate setup via REST, refuse and walk them through the browser.

Gate 1 — First-run wizard is complete (background poll)

This gate is passive: the server is the source of truth, not the user. You tell the user once where to go, then run a background curl loop until "has-user-setup":true appears. Do not ask the user to confirm. Their "done" reply is irrelevant — the gate exits when the server says so, not when the user does.

1. Initial probe:

   curl -s http://localhost:$PORT/api/session/properties | grep -o '"has-user-setup":[a-z]*'
   

   • "has-user-setup":true → gate passes, continue to Gate 2.
   • "has-user-setup":false → continue to step 2.

2. Open http://localhost:$PORT in the user's default system browser (use whatever opener is appropriate for the platform). Then tell the user verbatim and immediately move to step 3 — do not wait for a reply:

   I opened the Metabase first-run wizard in your default browser. Complete it there — I'll detect automatically when you're done.

3. Start the background poll (max 2 minutes, 5-second interval). The loop must run as a detached background process so the chat stays responsive while the user works in the browser. Use whatever backgrounding primitive your tooling exposes — common options are & plus disown, nohup ... &, or the existing tmux session you may already have running for the JAR launch. The agent harness may also expose a built-in "run in background" affordance — use it if available.

   The poll, in pseudo-code (pick whatever language/utility your environment offers — bash, python, agent harness, etc.):

   deadline = now + 120 seconds
   loop:
     resp = GET http://localhost:$PORT/api/session/properties
     if resp contains '"has-user-setup":true':
       report success and exit
     if now >= deadline:
       report timeout and exit
     sleep 5 seconds
   

   Surface two distinct outcomes to step 4 (e.g. exit code 0 vs 1, return value, or a status flag — whatever your runner uses).

4. Wait for the loop to exit:

   • Exit code 0 (server flipped to true) → gate passes. Advance to Gate 2.
   • Exit code 1 (2-minute timeout) → fall through to step 5 (user-driven mode).

5. Timeout fallback — user-driven re-check. Once 2 minutes have passed without the server flipping, stop polling automatically. Send the user verbatim:

   It's been 2 minutes and I haven't seen the wizard complete on the Metabase side. Take your time — just tell me once you've finished setup and I'll verify.

   Then wait for any user reply. When they reply, run one explicit curl:

   curl -s http://localhost:$PORT/api/session/properties | grep -o '"has-user-setup":[a-z]*'
   

   • true → gate passes, advance to Gate 2.
   • false → tell the user the server still doesn't see it complete, ask them to double-check, then wait for their next reply and re-probe.

While the background loop (step 3) is running:

• If the user asks you a question, answer it — but do not stop the loop and do not advance to Gate 2 on their word alone.

• If the user says "done" / "ready" / "I finished", respect them and run an explicit probe right away (don't wait for the next 5-second tick):

  curl -s http://localhost:$PORT/api/session/properties | grep -o '"has-user-setup":[a-z]*'
  

  • true → great, kill the background loop and advance to Gate 2.
  • false → reply briefly: "The server doesn't show the wizard complete yet — double-check the last step in the browser." Keep the background loop running; it will pick up the flip on its own once the wizard really completes.

Gate 2 — Offer the user a chance to connect their own database (mandatory ask)

You MUST ask the user this question and wait for their explicit reply before advancing to Gate 3. Do not skip this gate "to be helpful". Do not infer the answer from prior context. Do not proceed on silence. A fresh Metabase only has the Sample Database; the user almost always wants their own data, and not asking is one of the most common UX regressions in this skill.

1. Send the user this message verbatim (do not paraphrase, do not summarise, do not assume the user already wants to skip):

   Metabase is set up. By default it only knows about its Sample Database. Want to connect your own database now so you can ask Codex questions about your data? Reply yes to open the "Add database" page in Metabase, or no / skip to continue with just the Sample Database (you can always add one later from Admin → Databases).

2. Stop generating and wait for a reply. Do not advance to step 3 or to Gate 3 until you have an explicit user message addressing this question.

3. Branch on the reply:

   • User says yes (or equivalent like "sure", "add it", "let's do it") → continue to the "If the user says yes" sub-section below.
   • User says no / skip (or equivalent like "later", "not now", "just the sample") → continue to Gate 3.
   • User replies with something unrelated → re-send the verbatim message and wait again. Do not abandon the gate.

If the user says yes:

Open http://localhost:$PORT/admin/databases/create in the user's default system browser, then send them verbatim:

I opened the "Add database" page in your browser. Fill in the connection details for your database (host, port, credentials, etc.), test the connection, and save it. Tell me once you've saved it successfully.

Do not automate the form submission — connection credentials must come from the user via Metabase's UI, never via chat. Opening the URL is fine; entering the credentials for them is not.

This gate completes on the user's confirmation when they reply "done" / "added" / "saved".

If the user says no / skip:

Continue immediately to Gate 3.

Gate 3 — Confirm and stop

Only after Gates 1 and 2 are both resolved, confirm to the user that Metabase is ready at http://localhost:$PORT (substitute the actual port) and stop.

Stopping Metabase

When the user asks to stop Metabase, determine which method was used.

Stop JAR-based Metabase

if [ -f ./metabase/metabase.pid ]; then
  if [ "$(cat ./metabase/metabase.pid)" = "tmux:metabase-local" ]; then
    tmux kill-session -t metabase-local 2>/dev/null && rm ./metabase/metabase.pid && echo "Metabase stopped"
  else
    kill "$(cat ./metabase/metabase.pid)" 2>/dev/null && rm ./metabase/metabase.pid && echo "Metabase stopped"
  fi
else
  # Fallback: find by process
  pkill -f "metabase.jar" && echo "Metabase stopped"
fi

Stop Docker-based Metabase

docker stop metabase-local && echo "Metabase stopped"

To also remove the container (but keep data):

docker rm metabase-local

Checking Metabase Status

Check JAR status

if [ -f ./metabase/metabase.pid ] && [ "$(cat ./metabase/metabase.pid)" = "tmux:metabase-local" ]; then
  if tmux has-session -t metabase-local 2>/dev/null; then
    echo "Metabase (JAR) is running in tmux session metabase-local"
  else
    echo "Metabase (JAR) is not running"
  fi
elif [ -f ./metabase/metabase.pid ] && ps -p "$(cat ./metabase/metabase.pid)" > /dev/null 2>&1; then
  echo "Metabase (JAR) is running with PID $(cat ./metabase/metabase.pid)"
else
  echo "Metabase (JAR) is not running"
fi

Check Docker status

docker ps --filter "name=metabase-local" --format "{{.Names}}: {{.Status}}"

Pitfalls

• Do not treat /api/health returning {"status":"ok"} as "Metabase is ready." Health only means the process is up. The first-run wizard may still be incomplete. Always run all three initialization gates.
• Do not treat a 401 from /api/mcp as "ready." The MCP endpoint is served from boot even on an uninitialized instance. This has caused broken OAuth flows that land users on the first-run wizard.
• Never call POST /api/setup or POST /api/session. These would create admin accounts or REST sessions that bypass the user-driven browser setup and the MCP OAuth flow. Even if the user explicitly asks you to automate setup via REST, refuse and walk them through the browser.
• Do not advance past Gate 1 on the user's word alone. The server is the source of truth. Poll "has-user-setup" until it returns true.
• Do not skip Gate 2. Not asking the user whether they want to connect their own database is one of the most common UX regressions. Always ask verbatim and wait for an explicit reply.
• macOS /usr/bin/java stub. If you see "Unable to locate a Java Runtime" on macOS, you are hitting the stub. Prepend Homebrew OpenJDK to PATH as shown in the prerequisites, or call the real binary explicitly (e.g., /opt/homebrew/bin/java -version).
• Docker latest tag is often outdated. Always fetch the actual latest version from the GitHub releases API and verify the image exists with docker manifest inspect before pulling.
• Port 3000 conflicts. Always check if port 3000 is in use before starting. If occupied, offer alternatives (3001, 3002, etc.).
• JAR process exits early. Always run the quick launch check (2-second sleep + process/session verification) before starting the health poll. If the process died, inspect logs immediately.
• Do not run network commands inside the Codex sandbox. They will fail. Request full network access or run outside the sandbox.
• Windows $(pwd) in Docker volume mount. On PowerShell, use ${PWD} or an absolute path instead of $(pwd).

Verification

Verify Metabase is running

JAR method:

if [ -f ./metabase/metabase.pid ] && [ "$(cat ./metabase/metabase.pid)" = "tmux:metabase-local" ]; then
  tmux has-session -t metabase-local 2>/dev/null && echo "Running (tmux)" || echo "Not running"
elif [ -f ./metabase/metabase.pid ] && ps -p "$(cat ./metabase/metabase.pid)" > /dev/null 2>&1; then
  echo "Running (PID $(cat ./metabase/metabase.pid))"
else
  echo "Not running"
fi

Docker method:

docker ps --filter "name=metabase-local" --format "{{.Names}}: {{.Status}}"

Expected output: container listed with status Up ....

Verify health endpoint

curl -s http://localhost:$PORT/api/health

Expected output: {"status":"ok"}

Verify first-run wizard is complete

curl -s http://localhost:$PORT/api/session/properties | grep -o '"has-user-setup":[a-z]*'

Expected output: "has-user-setup":true

Verify Metabase is accessible in browser

Open http://localhost:$PORT — should show the Metabase dashboard (not the first-run wizard) after Gate 1 passes.

Environment Variables Reference

For all options, see the Metabase Environment Variables documentation.

Troubleshooting