An MCP server and <strong>CLI tool</strong> that allow LLMs to interact with CERN ROOT files.
Most knowledge and memory work still happens through a UI a human drives. Root MCP MCP server moves it into the conversation instead. An MCP server and CLI tool that allow LLMs to interact with CERN ROOT files.
The server publishes 1 tool. What each one is for:
Documentation — See docs/skills/root-cli.md for complete command reference with examplesConfiguration is passed through the environment: ROOT_MCP_CONFIG, ROOT_MCP_DATA_PATH, ROOT_MCP_EXPORT_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Root MCP's toolset — Documentation — is a fair guide to whether it matches your workflow. It is maintained by mohamedelashri; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Root MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Documentation | See [docs/skills/root-cli.md](docs/skills/root-cli.md) for complete command reference with examples. |
Or with a persistent config file:
```json
{
"mcpServers": {
"root-mcp": {
"command": "root-mcp",
"env": {
"ROOT_MCP_CONFIG": "/path/to/config.yaml"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| ROOT_MCP_CONFIG | Configuration value read at startup. | Optional |
| ROOT_MCP_DATA_PATH | Filesystem location the server is allowed to use. | Optional |
| ROOT_MCP_EXPORT_PATH | Filesystem location the server is allowed to use. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.