carmaker-mcp
Related Servers
Alternatives to carmaker-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables AI agents to read and write .mph model files, control the COMSOL desktop GUI in real time, and run complete modeling, meshing, solving, and post-processing workflows.231MIT
- AlicenseAqualityBmaintenanceEnables AI agents to control SimInTech dynamic modeling environment via COM API, including creating projects, configuring and connecting blocks, running simulations, and reading/writing signals.24MIT
- AlicenseAqualityDmaintenanceMCP server that connects any AI agent to MATLAB — execute code, async jobs, interactive Plotly plots, custom tools, and monitoring dashboard203MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to automate COMSOL Multiphysics simulations, including model management, geometry building, physics configuration, meshing, solving, and results visualization via the MCP protocol.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to control MATLAB Simulink models through natural language, providing tools for model creation, block management, wiring, simulation, and more via a local MCP backend.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 46 tools
Most tools target distinct resources and actions, and the descriptions are unusually detailed, which helps separate e.g. cm_live from cm_results_read or cm_model_get from cm_get_workspace_var. However, the parallel main-session and standalone-session families, plus several read/get-style tools across different data sources, can still require careful description reading to avoid misselection.
Almost all names use a consistent cm_ prefix and snake_case, with clear resource-oriented prefixes such as cm_model_, cm_results_, cm_standalone_, and cm_study_. There is minor inconsistency in verb ordering (e.g. cm_model_get vs cm_get_workspace_var), but the pattern remains highly readable.
46 tools is far above the typical well-scoped range and exceeds the 25+ threshold for a heavy surface. Although CarMaker is a broad domain, many tools could likely be consolidated or grouped, especially the parallel main and standalone lifecycle families.
The surface covers simulation lifecycle, project file CRUD via list/read/edit/clone, workspace variables, model parameters, results, studies, standalone instances, logs, GUI popups, and movie snapshots. Minor gaps remain, such as no explicit project-file delete/cleanup operation and limited direct GUI-setting management beyond popup timeout.