List every model in the SQLMesh project with its kind, columns, owner, and description.

Full detail for one model: rendered query, columns, kind, owner, tags, description.

Return the direct upstream and downstream model dependencies.

Fetch a bounded, optionally column-filtered preview of model data.

Return server, project, safety, and capability metadata.

Start a plan preview in the background and return a job ID.

Start a scheduled model run in the background. Requires confirm=true.

Return the current status and result of an asynchronous plan or run.

Cancel a queued job. Running SQLMesh operations cannot be interrupted safely.

Return all transitive upstream and downstream models affected by a change.

Summarize environment existence, snapshots, and current project drift.

Return recent dataveil audit events without exposing cell values.

Preview what a plan against an environment would change. Does not apply anything.

Returns a plan_id -- pass it to apply_plan to actually apply this exact plan.

Apply a previously-previewed plan. THIS CHANGES REAL DATA in the target warehouse.

Requires confirm=true. plan_id must come from a plan() call in this same session -- plans aren't kept across server restarts.

Column-level lineage: which upstream models/columns does this column depend on.

Run audits for a model (or all models if omitted). start/end bound the data checked.

Run unit tests for a model (or all tests if omitted).

Diff the current context against a target environment.

List every environment that exists in this project's state (e.g. prod, dev, ...).

Compare two tables or environments and return structured schema/row differences.

When comparing environments, pass select_models to choose the models to compare. SQLMesh's console output is suppressed because MCP clients receive the JSON result.

Check or format SQLMesh model and audit files.

The default check mode is read-only. Writing formatted files requires confirm=true and is never performed accidentally by an agent.

Execute scheduled/due model runs for an environment. THIS CHANGES REAL DATA.

Distinct from plan/apply_plan: this runs already-promoted models for their due intervals (what a cron trigger would do), rather than previewing or promoting structural changes. Requires confirm=true.

Aggregate-only profile of a model's columns: null rates, distinct counts, numeric stats, generalized string format signatures (e.g. 'ddd-dd-dddd'). Returns no raw rows or samples; see dataveil's README for its known limits.

The model must already be applied (see plan/apply_plan) -- dataveil reads from its current physical snapshot table.

Everything an agent needs to propose a data-cleansing plan for a model: the aggregate-only profile, a local sensitivity classification per column (PII:EMAIL, PII:SSN, PII:PHONE, ... or "none", each with a match_rate), and the closed operation vocabulary apply_cleansing_plan will accept.

This tool does not call an LLM or propose a plan itself -- it's the documented contract an agent (you) reasons over to build one. A plan is a list of {"operation", "column", "params", "rationale"} objects; "operation" must be a key in operation_vocabulary, and only the params listed for it are accepted. Pass the finished plan to apply_cleansing_plan.

Register a cleansing plan for later approval, instead of applying it directly. Only useful when this server requires plan approval (DATAVEIL_REQUIRE_PLAN_APPROVAL=true) -- otherwise apply_cleansing_plan already accepts a plan directly and this tool isn't needed.

Validates the plan against the operation vocabulary and the model's schema immediately -- a reviewer should never approve something that would fail at execution time. Read-only: nothing is applied here.

Returns a plan_id; pass it to approve_cleansing_plan, then to apply_cleansing_plan.

Mark a plan registered via register_cleansing_plan as approved.

This only records who approved it -- apply_cleansing_plan still requires confirm=true on top of this. Approval and confirm=true are two separate gates, not a substitute for each other.

Validate and apply a data-cleansing plan. THIS CHANGES REAL DATA in the model's current physical snapshot table. Requires confirm=true.

Default mode: pass plan directly, built from propose_cleansing_plan's output -- validated against the operation vocabulary and the model's schema before any step runs, same as always.

If this server requires plan approval (DATAVEIL_REQUIRE_PLAN_APPROVAL= true): pass plan_id instead, from a plan that was registered (register_cleansing_plan) and then approved (approve_cleansing_plan) by someone else. confirm=true is still required on top of that approval, not instead of it.

Note: this writes directly to the model's physical table, outside SQLMesh's own state tracking. A FULL-kind model is fully rematerialized on its next scheduled run/plan apply, which will silently undo the cleansing -- it was never folded into the model's SQL definition. Re-apply after any such rerun if the cleansing still applies.