salome-mcp
Related Servers
Alternatives to salome-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server that connects AI agents to KOMPAS-3D CAD, enabling automated 3D document operations through deterministic COM/API7 calls.1-
- AlicenseAqualityBmaintenanceA parametric CAD workspace as an MCP server, enabling agents to create, edit, and manipulate 3D models through tools, with a live studio UI and STL/OBJ import/export.1232 npm3MIT
- AlicenseBqualityDmaintenanceMCP Server for COMSOL Multiphysics simulation automation via AI agents.781MIT
- AlicenseNot gradedqualityBmaintenanceA local MCP server that enables AI agents to create and edit parametric CAD models through natural language, using a validated operation graph that compiles to real geometry.1MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to interact with Nastran FEA models by reading, writing, and analyzing BDF and OP2 files. It provides tools for mesh quality assessment, geometric analysis, and automated report generation for structural engineering workflows.3MIT
- AlicenseBqualityCmaintenanceEnables AI agents to automate COMSOL Multiphysics simulations, including model management, geometry building, physics configuration, meshing, solving, and results visualization through the MCP protocol.78MIT
TDQS
Scored across 36 tools
Several tools have overlapping purposes: boolean_operation duplicates fuse_objects/cut_objects/common_objects, create_group/create_groups/create_surface_group/create_volume_group are redundant, and copy_object vs duplicate_object are similar. This overlapping surface will confuse an agent.
Most names follow a consistent verb_noun pattern (get_, create_, list_, export_, import_, etc.). Minor deviations include 'boolean_operation' (not a verb) and the somewhat inconsistent group creation variants (create_group, create_groups, create_surface_group, create_volume_group), but overall the naming is predictable.
With 36 tools, the server is over-scoped for the domain. While SALOME is complex, the tool set includes many near-duplicates and convenience wrappers that inflate the count beyond what is necessary, making it heavy and harder to navigate.
The tool surface covers the main geometry and meshing workflows: creation, import/export, boolean operations, grouping, transformations, and mesh generation/computation. Minor gaps exist (e.g., no scaling, no mesh deletion explicitly but delete_object likely covers it), but core operations are well represented.