Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Validate, lint, test-run and explain Open Lakehouse Contracts with LakeLogic, from any AI assistant.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"lakelogic": {
"command": "uvx",
"args": [
"lakelogic-mcp"
]
}
}
}Run this in your terminal
claude mcp add lakelogic -- uvx lakelogic-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"lakelogic": {
"command": "uvx",
"args": [
"lakelogic-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"lakelogic": {
"type": "stdio",
"command": "uvx",
"args": [
"lakelogic-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account LakeLogic, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.4) reached the registry 9 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, FactLot
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Cited CRE facts and deterministic calculators for agents: rent, CAM, debt sizing, IRR, parcel IDs.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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/
*"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.
| Tool | Answers |
|---|---|
validate_contract | Does it match the OLC model? Each error's location and problem |
lint_contract | Does it pass the lint checks? Governance findings, 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 fail, and why (Polars or DuckDB, on a local file) |
Details and inputs: Tools. A first run, start to finish: Walkthrough.
All clients need uv on your PATH. Start your assistant in the project that holds your contracts (or pass --root ).
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.
uvx downloads the package, as any install does.)_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.run_contract. Nothing is written to the contract's target.sample: 0 removes only the rows, so test with generated data if a file holds personal or confidential data.More: Safety and privacy.
To work on the server from a checkout, see Development.