April 1, 2026

Moose gains first-class AI agent integration with a new moose mcp stdio proxy, a VS Code onboarding extension, and the moose harness init scaffolding command. The query layer ships getModelSchema() for dynamic report-builder UIs, and the 514 CLI adds clickhouse seed, deployment redeploy, and deployment wait commands.

Moose

New Features

MCP proxy for AI agent integration (@LucioFranco) A new moose mcp command runs a stdio-based MCP proxy server that connects AI agents — such as Claude Code or Codex — to a running Moose dev server. The proxy forwards tool calls (like querying the data catalog or executing ClickHouse queries) over stdio, which is the standard transport for editor-integrated agents. Host and port are auto-detected from your project config.

For more info check out the moose mcp docs

VS Code onboarding extension (@callicles) A new "Fiveonefour" VS Code extension keeps the Moose and 514 CLIs installed and current. On every activation it runs the installer, detects CLI versions, and opens a Harness splash page with the current init command after a successful install or update. Supported on macOS, Linux, and VS Code Remote — WSL.

moose harness init scaffolding command (@callicles) New moose harness init command for creating Moose Harness projects. Supports both an interactive wizard (zero-arg) and a fully non-interactive arg-driven mode for CI/CD. Templates include the new typescript-agent template with typed query model tools, prebuild steps, and improved onboarding output.

# Interactive wizard
moose harness init
 
# Non-interactive
moose harness init my-project typescript-agent \
  --location ./my-project \
  --agent none \
  --no-lsp

Query model schema extraction with getModelSchema (@georgevanderson) A new getModelSchema() function extracts a JSON-serializable schema from any QueryModel, describing its metrics, dimensions, filters (with operators and optional distinct values), sortable fields, and defaults. Frontends can use this to dynamically build report-builder UIs, form controls, and filter panels without hardcoding model structure.

import { getModelSchema, getMooseUtils } from "@514labs/moose-lib"; // In a consumption API handler:const { client } = await getMooseUtils(); // Extract schema with distinct filter valuesconst schema = await getModelSchema(myQueryModel, { client: client.query }); // schema.metrics → [{ id: "totalOrders", label: "totalOrders" }, ...]// schema.dimensions → [{ id: "region", label: "region" }, ...]// schema.filters → [{ id: "status", operators: ["eq", "in"], values: [...] }]

Docs: Semantic Layer

Improvements

• Alternative container runtime support: moose dev now works with Finch, Podman, and nerdctl in addition to Docker. Temporal versions are baked into compose files to work around nerdctl's lack of env var substitution. (@LucioFranco) Docs: Dev Environment
• Read-only query clients: getMooseUtils({ readonly: true }) now enforces ClickHouse readonly=2 on all queries, preventing accidental writes from consumption APIs and testing utilities. (@LucioFranco)
• released typescript-agent template: Template that combines MooseStack and NextJS to build production ready analytics agents. (@callicles)

Bug Fixes

• Fix materialized view migration failures when source tables span multiple ClickHouse databases — the CLI now correctly normalizes backtick-qualified table names during infra map comparison. (@LucioFranco)
• Include the migrations/ directory in Docker builds, fixing deployment failures for projects using SQL migrations. (@phiSgr)

Fiveonefour Hosting

New Features

514 clickhouse seed command (@onelesd) Seed ClickHouse tables on preview branches from production or another source branch. Supports configurable row limits and WHERE clauses for targeted seeding.

# Seed from production with a row limit
514 clickhouse seed events --limit 10000
 
# Seed from a specific branch with a filter
514 clickhouse seed users \
  --from staging \
  --where "created_at > '2026-01-01'"
  --limit 10000

Docs: Branch Data Seeding

514 deployment redeploy command (@onelesd) Re-trigger a deployment from the CLI with a progress spinner. Useful for recovering from transient failures without pushing a new commit.

514 deployment wait command (@onelesd) Block until a deployment reaches a terminal state, with a progress bar showing elapsed time. Designed for CI/CD pipelines that need to gate on deployment completion.

Improvements

• 514 env list now auto-detects the current git branch when no --branch flag is provided. The --all flag is replaced with --platform for showing platform-managed variables (ClickHouse, Redis credentials). (@DatGuyJonathan)
• New guided project creation path for users building on existing ClickHouse, with step-by-step CLI installation and moose init --from-clickhouse instructions. (@groy-514)

Bug Fixes

• Fix incorrect build and deployment status display when viewing a new branch of an existing project. (@groy-514)
• Fix 514 link showing the organization slug instead of the display name in confirmation and success messages. (@DatGuyJonathan)
• Fix 514 auth login getting stuck when not already signed into Fiveonefour website. (@DatGuyJonathan)