LakeLogic MCP

mcp-name: io.github.LakeLogic/lakelogic-mcp

Help AI assistants check and test data contracts locally.

Validate Open Lakehouse Contracts (OLC), find governance gaps, explain rules and generate sample data. Test-run contracts with LakeLogic Core using Polars or DuckDB, then inspect accepted rows, failed rows and the reasons they failed.

Works with MCP-compatible assistants — Claude Code, Claude Desktop, Cursor and others. No LakeLogic account required.

OLC defines the contract. Core executes it. MCP gives your assistant access to those tools.

📖 Documentation: https://mcp.lakelogic.io/

Example

"Check orders.yaml, explain any findings, generate sample data and test it locally."

The assistant validates the contract, lints it, explains each finding, writes test data shaped by the contract, runs it, and reports which rows passed and why the others failed — real results from LakeLogic, not plausible-looking YAML.

Related MCP server: datapact

Tools

Details and inputs: Tools. A first run, start to finish: Walkthrough.

Install

All clients need uv on your PATH. Start your assistant in the project that holds your contracts (or pass --root <folder>).

Claude Code — as a plugin:

/plugin marketplace add LakeLogic/lakelogic-mcp
/plugin install lakelogic-mcp@lakelogic-mcp

or directly: claude mcp add lakelogic -- uvx lakelogic-mcp

Cursor: Add to Cursor

Claude Desktop, VS Code and other MCP clients — add to the client's MCP settings:

{
  "mcpServers": {
    "lakelogic": {
      "command": "uvx",
      "args": ["lakelogic-mcp", "--root", "/path/to/your/contracts/project"]
    }
  }
}

It is listed in the official MCP Registry as io.github.LakeLogic/lakelogic-mcp.

Safety and privacy

• Local. The server talks to your client over stdio; it opens no network connection itself, needs no account and sends no telemetry. (Installing with uvx downloads the package, as any install does.)

• Tool paths stay in your project. Every path you give a tool, and the _domain.yaml / _system.yaml that lint takes into account, must be inside the project folder. Files a contract itself names (a links: dataset, for example) are read by Core as written.

• Running a contract does what the contract configures. If a contract declares notifications or run-log delivery, LakeLogic Core may send them during run_contract. Nothing is written to the contract's target.

• Results reach your AI provider. Tool results go into the assistant's context: quarantined sample rows, failure reasons (which can quote your data) and the contract itself. sample: 0 removes only the rows, so test with generated data if a file holds personal or confidential data.

More: Safety and privacy.

Contributing

To work on the server from a checkout, see Development.