materials-studio-mcp-moc
Related Servers
Alternatives to materials-studio-mcp-moc
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceEnables MCP clients to execute Materials Studio modeling and computation tasks via MaterialsScript runtime, with a local Dashboard for monitoring.3316MIT
- AlicenseNot gradedqualityCmaintenanceEnables evidence-first CAE automation on Windows through local MCP servers for FreeCAD, Elmer FEM, and ParaView, supporting validated workflows from CAD to simulation and post-processing with a shared safety and evidence runtime.3MIT
- AlicenseNot gradedqualityDmaintenanceA specialized MCP server for Metal-Organic Framework research that provides tools for database searching, structural optimization, and energy calculations via ASE. It enables scientific workflows by allowing users to interact with MOF data and perform chemical simulations through a standard SSE interface.MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that provides tools for reproducible COMSOL Multiphysics batch workflows, enabling AI agents to compile, run, and diagnose Java API model scripts with COMSOL.4MIT
- AlicenseAqualityBmaintenanceAn MCP server for computational materials science that enables AI assistants to generate LAMMPS simulations, parse outputs, analyze nematic order, detect plastic rearrangements, and estimate viscosity through 12 specialized tools.121MIT
- AlicenseNot gradedqualityCmaintenanceMCP-native scientific skills for reproducible computational biology and AI-driven drug-discovery workflows. It combines deterministic scientific tools with an MCP server to give AI agents real computational capabilities.Apache 2.0
TDQS
Scored across 53 tools
Many tools have overlapping purposes, such as multiple preflight/check/validate tools (md_structure_preflight, ms_castep_fixed_profile_preflight, ms_castep_preflight_checked, md_msi2lmp_preflight) and several prepare/build tools. The distinction between 'preflight', 'checked', and 'readiness' tools is not clear from names, causing potential misselection.
Tool names mix conventions: some use verb_noun (md_task_submit), others use noun_noun (ms_castep_gateway_readiness), and prefixes vary between ms_, md_, and combinations. Verbs like get, check, assess, plan, prepare, and run are used inconsistently, making the naming pattern unpredictable.
With 53 tools, the server is over 25, which is excessive for most MCP servers. While the domain is complex, many tools are highly specialized and could be consolidated (e.g., multiple preflight and checked variants), making the surface feel bloated.
The tool set covers the core lifecycle of Materials Studio workflows, including project initialization, structure preparation, conversion, validation, task management, and quality gates. Minor gaps exist, such as no generic list projects or delete artifact tools, but agents can work around these via existing project_get and register_artifact.