Auto-LAMMPS MCP
Related Servers
Alternatives to Auto-LAMMPS MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables automating materials science research workflows through a multi-agent AI platform, including literature discovery, knowledge extraction, simulation, and document generation.MIT
- AlicenseBqualityCmaintenanceEnables LLM agents to run verified DFT materials workflows (structure fetch, relaxation, band/DOS) with automated convergence gates and physics validation, ensuring every result is machine-verified with a complete evidence trail.53MIT
- AlicenseBqualityBmaintenanceEnables AI agents to plan, confirm, submit, observe, and audit compute jobs across local machines, SSH workstations (including WSL), and Slurm clusters through a unified stdio interface, with node probing, environment evidence, project sync, storage governance, and progress/ETA tracking.311MIT
- FlicenseNot gradedqualityBmaintenanceEnables agents to inspect molecular-dynamics trajectories — frames, atom counts, elements, depth profiles, and rendered images or videos — and to run LAMMPS/ReaxFF simulations as detached background jobs that survive the server exiting, with status, logs, results, and cancellation tools. Also supports submitting decks to a hosted GPU tier or your own SSH hosts, with credit balance checks and deck preflight validation.-
- AlicenseBqualityCmaintenanceEnables users to work on a SLURM HPC cluster over SSH through plain-language requests, covering file browsing and editing, batch job generation and submission, queue monitoring, and log reading to debug failed jobs. It runs with built-in safety guardrails such as fixed commands and configurable path policies for reads and writes.27MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to discover and execute simulated engineering workflows through ontology-generated typed tools, with prerequisite-aware planning, unit and range validation, and structured recovery hints.1MIT
TDQS
Scored across 75 tools
The tool set contains many overlapping read/get/check families: task_get, run_get, batch_get, check_get, operation_get, results_get, task_records, operation_read, response_read, file_read, and resource_file_read all retrieve state with subtle distinctions. Descriptions are long and do clarify boundaries, but an agent can easily select the wrong retrieval or status tool without careful cross-referencing.
Most names follow a predictable snake_case noun_verb pattern with clear domain prefixes such as task_, run_, batch_, validation_, check_, resource_, and memory_. A few outliers like doctor, events, help, and response_read slightly break the pattern but remain readable.
Seventy-five tools is far beyond a well-scoped set and imposes a very high selection burden. The domain is complex, but the surface is heavily fragmented into many narrowly split workflow, validation, retrieval, and background-control tools.
Coverage is broad: project lifecycle, resource registration, environment capture, validation planning, run/batch preparation and submission, analysis, artifact linking, memory, events, backup, and export/import are all present. Only minor gaps such as explicit deletion or simpler file/listing operations are apparent.