Back to Browse

Lakelogic MCP Server

Developer ToolsModerate5.6MCP RegistryLocal
Free

Server data from the Official MCP Registry

Validate, lint, test-run and explain Open Lakehouse Contracts with LakeLogic, from any AI assistant.

About

Validate, lint, test-run and explain Open Lakehouse Contracts with LakeLogic, from any AI assistant.

Security Report

5.6
Moderate5.6Moderate Risk

lakelogic-mcp is a local stdio server for validating, linting, and running Open Lakehouse Contracts. Its file access is confined to the project root by resolving paths and checking containment, and it has no network calls, shell execution, or hardcoded secrets. Remaining findings are low-severity: broad exception handling, directory creation before output validation, and loosely pinned dependencies. Supply chain analysis found 5 known vulnerabilities in dependencies (0 critical, 5 high severity). Package verification found 1 issue.

7 files analyzed · 11 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

File System Write

Writes or modifies files on your machine. Check that this is expected for the tool.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-lakelogic-lakelogic-mcp": {
      "args": [
        "lakelogic-mcp"
      ],
      "command": "uvx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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

ToolAnswers
validate_contractIs this a legal OLC contract? Each error's location and problem
lint_contractIs it a good one? Governance findings from lakelogic lint, each with its fix
explain_ruleWhy does a lint rule exist? What it checks, why it matters, a failing and a fixed contract
contract_referenceHow is one part of a contract written? (anatomy, quality, materialization, …)
export_odcsThe contract as an Open Data Contract Standard document
generate_test_dataSynthetic data shaped by the contract, with a share of rows that deliberately break its rules
run_contractHow 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

Reviews

No reviews yet

Be the first to review this server!