Skip to main content

lakelogic-mcp

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

A local MCP server that lets AI assistants (Claude Code, Claude Desktop, Cursor and any MCP client) check the Open Lakehouse Contracts (OLC) they write, using LakeLogic itself instead of guessing.

  • Runs on your machine over stdio. No network, no account, no telemetry.
  • Never touches a platform. Two tools act locally: generate_test_data writes a data file and run_contract runs a contract on it with Polars or DuckDB. Nothing is written to a contract's target.
  • Reads and writes only inside the project folder it was started in.

Tools

Tool Answers
validate_contract Is this a legal OLC contract? Each error's location and problem
lint_contract Is it a good one? Governance findings from lakelogic lint, each with its fix
explain_rule Why does a lint rule exist? What it checks, why it matters, a failing and a fixed contract
contract_reference How is one part of a contract written? (anatomy, quality, materialization, …)
export_odcs The contract as an Open Data Contract Standard document
generate_test_data Synthetic data shaped by the contract, with a share of rows that deliberately break its rules
run_contract How many rows pass, how many are quarantined, and why (Polars or DuckDB, local only)

Install

Claude Code (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

Any other MCP client (VS Code, Claude Desktop, ...): run uvx lakelogic-mcp as a stdio server. It is also listed in the official MCP Registry as io.github.LakeLogic/lakelogic-mcp.

All of them need uv on your PATH.

Try it locally (development checkout)

cd C:\_Personal\_SaaS\lakelogic-mcp
uv venv .venv
uv pip install --python .venv\Scripts\python.exe "mcp>=1.2" pytest -e ..\open-lakehouse-contract -e ..\lakelogic
uv pip install --python .venv\Scripts\python.exe --no-deps -e .
.venv\Scripts\python.exe -m pytest

Register it with Claude Code

From the project whose contracts you want checked:

claude mcp add lakelogic -- C:\_Personal\_SaaS\lakelogic-mcp\.venv\Scripts\lakelogic-mcp.exe

Then ask, for example:

  • "Lint the contracts in this folder and fix what you find."
  • "Why is KEY-002 flagged on silver_trips.yaml?"
  • "Write a silver contract for orders and check it before you show me."

Claude Desktop / Cursor

Add to the client's MCP settings (claude_desktop_config.json, or Cursor's mcp.json):

{
  "mcpServers": {
    "lakelogic": {
      "command": "C:\\_Personal\\_SaaS\\lakelogic-mcp\\.venv\\Scripts\\lakelogic-mcp.exe",
      "args": ["--root", "C:\\path\\to\\your\\contracts\\project"]
    }
  }
}

Once published

uvx lakelogic-mcp            # Claude Code: claude mcp add lakelogic -- uvx lakelogic-mcp

Metadata

Release files for lakelogic-mcp 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for lakelogic-mcp 0.1.1
File Size Uploaded
lakelogic_mcp-0.1.1.tar.gz 19.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for lakelogic-mcp 0.1.1
File Interpreter ABI Platform
lakelogic_mcp-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 32.8 kB

Release files / lakelogic_mcp-0.1.1.tar.gz

Download URL lakelogic_mcp-0.1.1.tar.gz
Size 19.1 kB
Tags Source
SHA-256 checksum
How to use checksums
d999ee1a94b04adcde05591f0ef958c0fe1856aea158b3ddf50f0a7e3d47cab0
BLAKE2b-256 checksum
How to use checksums
bbf3097ec20b71bcf1074848c3f764e35a02745eb4e07af4872193d9f4dfcb95
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.

Transparency log

Release files / lakelogic_mcp-0.1.1-py3-none-any.whl

Download URL lakelogic_mcp-0.1.1-py3-none-any.whl
Size 13.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a4b545de69f0a6c1a38a3aede670c973368a8f17d172171fafa0bee6520edfe0
BLAKE2b-256 checksum
How to use checksums
5df397cd4384f0ab56df218347bbaae8ceb34ec4119cac775beb772f992ccffa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page