
ROOT MCP Server
io.github.omazapaPublished by GitHub account omazapav1.0.0Updated Oct 24, 2026
ROOT-based MCP server exposing root_python and root_cpp tools (stdio transport).
Overview
Local MCP server that runs Python and C++ code in-process with CERN ROOT/PyROOT, returning stdout, stderr and error details.
- What you can do
- Execute Python code with ROOT already in scope and get back stdout, stderr and error metadata
- Execute C++ snippets through ROOT's cling interpreter, with compilation errors detected from return codes and stderr
- Create histograms, canvases and other ROOT graphics objects, with an event loop and optional embedded HTTP server for interactive canvases
- Log each execution, with numbered code and results, to the MCP console
- When to use it
- Useful when an assistant should run ROOT-based data analysis, histogramming or plotting code locally, for example inside VS Code with Copilot Chat, instead of only writing snippets for you to run.
- Requirements
- Runs as a local stdio process on the user's machine (Docker image or pip install). Needs a ROOT 6.x or later installation with PyROOT enabled, Python 3.10+, and the ROOT environment sourced (for example thisroot.sh) before starting the server.
Installation
In SourceWeft
- Open ROOT MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
root_mcp_server: MCP Server for ROOT
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.
Features
- Direct Python execution: Run Python code with PyROOT available automatically
- Direct C++ execution: Run C++ code via ROOT's cling interpreter
- In-process: All code runs in the same process (no subprocess isolation)
- Error detection: Automatic detection of C++ compilation errors via return codes and stderr
- Console logging: Pretty-printed code execution with results in MCP console
- Graphics support: TCanvas and ROOT graphics objects with event loop support
Architecture
Below is the architecture diagram for the root_mcp_server project. The image contains a visual representation of the components and their interactions.
Description:
- MCP Client (VS Code / CLI / Programmatic): connects to the MCP server and sends execution requests. Clients can be interactive (e.g. VS Code + Copilot Chat) or scripted CLI clients.
- FastMCP Server: receives MCP tool calls (
root_python,root_cpp) and dispatches them to the in-process executor. - RootExecutor (in-process PyROOT): runs Python or C++ code with the ROOT runtime, manages graphics mode, and can expose an embedded HTTP server (THttpServer) for interactive canvases.
- ROOT Web Canvas (THttpServer / JSROOT): when graphics are enabled, canvases created in the ROOT session are available via the embedded HTTP server; clients can open the provided URL to inspect plots interactively.
- Artifacts & Outputs: execution results (stdout/stderr and error metadata) are returned to the MCP client; interactive canvases are accessible via the HTTP endpoint.
This architecture keeps ROOT running in-process for low-latency execution while providing a web-backed path for interactive visualization.
Installation
Prerequisites
- ROOT (6.x or later) with PyROOT enabled
- Python 3.10+
Install the package
Usage
Option 1: VS Code with GitHub Copilot Chat
The easiest way to use this MCP server is through VS Code with GitHub Copilot Chat.
1. Install GitHub Copilot Chat extension
Make sure you have the GitHub Copilot Chat extension installed in VS Code.
2. Configure MCP server 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:
Important: Replace /path/to/ROOT/build/bin/thisroot.sh with the actual path to your ROOT installation's thisroot.sh script.
3. Use in Copilot Chat
Once configured, you can use the MCP tools in GitHub Copilot Chat:
The server will automatically log executed code and results to the MCP console (visible in VS Code's Output panel).
Option 2: Command line
Start the MCP server directly:
Option 3: Programmatic usage
Available Tools
The server exposes two MCP tools:
1. root_python
Execute Python code with ROOT automatically available in scope.
Arguments:
code(string): Python code to execute
Returns:
Example:
2. root_cpp
Execute C++ code via ROOT's cling interpreter.
Arguments:
code(string): C++ code to execute
Returns:
Example:
Features in Detail
Error Detection
The server automatically detects C++ compilation errors by:
- Checking the return code from
ROOT.gInterpreter.ProcessLine() - Scanning stderr for error keywords (
error:,Error:,fatal error:)
Errors are reported with ok=false and detailed error messages.
Console Logging
All code execution is logged to stderr (MCP console) with:
- Pretty-printed code with line numbers
- Execution status (✓ success / ❌ failure)
- Complete stdout, stderr, and error details
Example output:
Graphics Support
The server initializes TApplication and supports ROOT graphics:
- TCanvas windows (batch mode can be disabled)
- Histogram plotting
- ROOT event loop for interactive graphics
- Object persistence to prevent garbage collection
Development
Running tests
Project Structure
License
See LICENSE file.
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Acknowledgments
- Built with the Model Context Protocol
- Powered by ROOT from CERN
Source: README.md at commit 0dd2d95
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts