Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Run end-to-end ML experiments from natural language (XGBoost, LightGBM, Optuna).
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": {
"ml-lab": {
"command": "uvx",
"args": [
"mcp-ml-lab"
]
}
}
}Run this in your terminal
claude mcp add ml-lab -- uvx mcp-ml-labPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ml-lab": {
"command": "uvx",
"args": [
"mcp-ml-lab"
]
}
}
}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": {
"ml-lab": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-ml-lab"
]
}
}
}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 8, 2026
The registry name was verified with the GitHub account rohithraju-ops, 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.0) reached the registry 5 months 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, Tethered Trust
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ 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.
Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.
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.
Let AI agents run real ML experiments end-to-end.
An MCP server that gives Claude (or any MCP-aware AI agent) the ability to profile a CSV, define an ML task, tune XGBoost and LightGBM with Optuna, and produce a markdown report with feature importance — all from natural language.
The existing ML-related MCP servers wrap MLflow, ZenML, or Weights & Biases and expose them as read-only — agents can browse experiment history but can't actually *run* anything. mcp-ml-lab fills the gap: it lets agents execute the full experimentation loop from a user's natural-language request.
A user typing "train a model on titanic.csv to predict survival" should not need to know what XGBoost is, what cross-validation is, or how to write a hyperparameter search. The agent handles all of that — mcp-ml-lab is the tools layer that makes it possible.
pip install mcp-ml-lab
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": { "ml-lab": { "command": "mcp-ml-lab" } } }
Restart Claude Desktop. The five tools below are now available.
Try these in Claude Desktop with mcp-ml-lab connected:
| Tool | What it does |
|---|---|
inspect_data | Profile a CSV — shape, dtypes, nulls, summary stats, class balance |
define_task | Register an ML task (CSV + target + classification/regression) |
run_experiment | Train one or more models, optionally tuning with Optuna |
get_results | Markdown report with metrics, hyperparameters, feature importance |
compare_runs | Side-by-side comparison of multiple experiments |
Each tool's full signature is in its docstring; they self-document to the LLM.
Claude Desktop ───MCP/stdio─── mcp-ml-lab server
│ ├── data.py CSV loading, schema inference, preprocessor ├── trainers/ Pluggable XGBoost + LightGBM adapters ├── search.py Stratified CV + Optuna TPE tuning ├── metrics.py Accuracy, F1, AUC, log loss ├── storage.py SQLite via SQLAlchemy 2.0 └── reporting.py Markdown report generation
All experiments and trials are persisted to ~/.mcp-ml-lab/store.db so an agent can refer back to runs across sessions.
Full design notes in ARCHITECTURE.md.
v0.1.0 ships classification with XGBoost and LightGBM. Planned for v0.2.0+:
Issues and PRs welcome.
git clone https://github.com/rohithraju-ops/mcp-ml-lab.git
cd mcp-ml-lab python -m venv .venv && source .venv/bin/activate pip install -e ".[dev]" pytest -v
Local debugging is easiest with the MCP Inspector:
npx @modelcontextprotocol/inspector mcp-ml-lab
MIT.