Lmod
List, search and inspect Lmod environment modules, and save or restore module collections.
claude mcp add --scope project clio-lmod -- clio-kit mcp-server lmod
Install the launcher first. Restart your client after setup. Configuration locations →
Check the connection
clio-kit doctor --server lmod --connect
Checks prerequisites and tool discovery. Test on known input to verify results. Native backends may require additional setup.
Tools
module_listList all currently loaded environment modules.
module_availSearch for available modules, optionally filtered by name pattern.
module_showDisplay detailed information about a specific module.
module_spiderSearch the entire module tree comprehensively for matching modules.
module_saveSave currently loaded modules as a named collection.
module_restoreRestore a previously saved module collection.
module_savelistList all saved module collections.
Examples
Replace example paths with your own files and check the returned results.
Discover the available environment
Use module_list to inspect modules loaded in the MCP process. Search visible
modules with module_avail, use module_spider for hierarchical discovery,
and inspect prerequisites and settings with module_show.
The user tool surface does not load, unload or swap modules. A child process
cannot establish the environment of your shell or a later workload. For a
JARVIS execution, resolve software through Spack and pass exact load specs to
jarvis_run.
Saved collections
module_save writes a named collection; module_savelist lists collections.
module_restore updates the environment retained by this MCP process for
subsequent Lmod calls. It does not change the parent shell or another MCP server.
Verify the actual workload environment separately.
Lmod and its configured module tree must be present on the host. An MCP connection alone does not confirm either prerequisite.
Native backend configuration
Set LMOD_CMD to the site Lmod executable and MODULEPATH to trusted modulefiles. The server uses Bash to evaluate Lmod and retains collection changes for subsequent calls in the same MCP process. It does not change your parent shell or other MCP servers.