Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
ROOT-based MCP server exposing root_python and root_cpp tools (stdio transport).
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": {
"root": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/omazapa/root-mcp:1.0.0"
]
}
}
}Run this in your terminal
claude mcp add root -- docker run -i --rm docker.io/omazapa/root-mcp:1.0.0Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"root": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/omazapa/root-mcp:1.0.0"
]
}
}
}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": {
"root": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/omazapa/root-mcp:1.0.0"
]
}
}
}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 omazapa, 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 (1.0.0) reached the registry 12 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Starreel
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.
Turn a script into a finished, downloadable short-drama episode — via MCP or REST.
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.
Model Context Protocol server for executing Python and C++ code with PyROOT
Minimal MCP (Model Context Protocol) server that allows LLMs and other MCP clients to execute Python and C++ code directly using PyROOT, without HTTP endpoints or external APIs.
Below is the architecture diagram for the root_mcp_server project. The image contains a visual representation of the components and their interactions.
Description:
root_python, root_cpp) and dispatches them to the in-process executor.This architecture keeps ROOT running in-process for low-latency execution while providing a web-backed path for interactive visualization.
pip install -e .
The easiest way to use this MCP server is through VS Code with GitHub Copilot Chat.
Make sure you have the GitHub Copilot Chat extension installed in VS Code.
Add the MCP server configuration to your VS Code settings. Open your settings.json (Ctrl/Cmd + Shift + P → "Preferences: Open User Settings (JSON)") and add:
{
"github.copilot.chat.codeGeneration.instructions": [ { "text": "Use ROOT MCP server for data analysis" } ], "mcp.servers": { "root/mcp-server": { "type": "stdio", "command": "root_mcp_server", "args": [] } } }
Important: Replace /path/to/ROOT/build/bin/thisroot.sh with the actual path to your ROOT installation's thisroot.sh script.
Once configured, you can use the MCP tools in GitHub Copilot Chat:
@workspace Use #root_python to execute Python code with PyROOT
@workspace Use #root_cpp to execute C++ code with ROOT
The server will automatically log executed code and results to the MCP console (visible in VS Code's Output panel).
Start the MCP server directly:
root_mcp_server
from mcp.client.stdio import stdio_client, StdioServerParameters
from mcp.client.session import ClientSession
server_params = StdioServerParameters( command="bash", args=["-lc", "source /path/to/thisroot.sh && python3 -m root_mcp_server.cli"], env=None )
async with stdio_client(server_params) as (read, write): async with ClientSession(read, write) as session: await session.initialize()
result = await session.call_tool("root_python", arguments={ "code": "import ROOT; print(ROOT.gROOT.GetVersion())" }) print(result)
The server exposes two MCP tools:
root_pythonExecute Python code with ROOT automatically available in scope.
Arguments:
code (string): Python code to executeReturns:
{
"ok": boolean, "stdout": string, "stderr": string, "error": string | null, "error_type": string | null }
Example:
code = """
import ROOT h = ROOT.TH1F("h", "Gaussian", 100, -5, 5) for i in range(10000): h.Fill(ROOT.gRandom.Gaus(0, 1)) print(f"Mean: {h.GetMean():.3f}") """
root_cppExecute C++ code via ROOT's cling interpreter.
Arguments:
code (string): C++ code to executeReturns:
{
"ok": boolean, "stdout": string, "stderr": string, "error": string | null, "error_type": string | null }
Example:
TH1F* h = new TH1F("h", "Gaussian;X;Y", 100, -5, 5);
for(int i=0; i<10000; i++) h->Fill(gRandom->Gaus(0,1)); TCanvas* c = new TCanvas("c", "Canvas", 900, 600); h->Draw(); c->Update(); std::cout << "Mean: " << h->GetMean() << std::endl;
The server automatically detects C++ compilation errors by:
ROOT.gInterpreter.ProcessLine()error:, Error:, fatal error:)Errors are reported with ok=false and detailed error messages.
All code execution is logged to stderr (MCP console) with:
Example output:
============================================================
EXECUTING PYTHON CODE: 1 | import ROOT 2 | print(ROOT.gROOT.GetVersion()) ============================================================ ✓ EXECUTION SUCCESS STDOUT: 6.39/01
The server initializes TApplication and supports ROOT graphics:
# Test basic functionality
python test_mcp_client.py
python test_persistent_window.py
python test_histogram.py
root_mcp_server/
├── root_mcp_server/ │ ├── init.py │ ├── cli.py # Entry point │ ├── executor.py # Code execution │ └── server.py # MCP server definition ├── test_mcp_client.py ├── test_persistent_window.py ├── test_histogram.py └── README.md
See LICENSE file.
Contributions are welcome! Please feel free to submit a Pull Request.