comsol-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COMSOL_ROOT | Yes | Path to COMSOL installation directory, e.g., C:\Program Files\COMSOL\COMSOL63\Multiphysics | |
| COMSOL_SERVER_MCP_HOME | Yes | Path to the server home directory for MCP, e.g., $PWD\comsol-server-home |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_infoA | Return COMSOL Server MCP status, configured paths, and current runtime state. |
| server_startB | Start a local COMSOL Multiphysics Server and connect the MCP client to it. This is an advanced entrypoint. The recommended visible workflow is to start COMSOL Multiphysics Server manually, connect Desktop to it, and then use server_connect() from MCP. |
| server_connectC | Connect the MCP client to an existing COMSOL Multiphysics Server. |
| server_disconnectA | Disconnect the MCP client. Optionally shut down the local server if MCP started it. |
| model_createB | Create a new in-memory model on the connected COMSOL server and select it as current. |
| model_loadB | Load an MPH file on the connected COMSOL server and select it as current. |
| model_treeA | Return tags and structure for the current server-side model. |
| get_parametersB | Return current global parameters from the selected server-side model. |
| set_parametersC | Set multiple global parameters on the selected server-side model. |
| ensure_componentC | Ensure a component exists in the selected server-side model. |
| ensure_geometryC | Ensure a geometry sequence exists in the selected server-side model. |
| ensure_meshC | Ensure a mesh sequence exists in the selected server-side model. |
| create_featureC | Create a geometry feature and optionally apply initial properties. |
| update_featureC | Update geometry feature properties on the selected server-side model. |
| delete_featureC | Delete a geometry feature from the selected server-side model. |
| run_featureC | Run a geometry or mesh sequence on the selected server-side model. |
| run_studyC | Run the current model study, optionally restricting execution to a study tag. |
| save_modelC | Save the current server-side model to disk. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Every tool targets a distinct action or entity: server management, model operations, geometry/mesh features, parameters, and study execution. There is no ambiguity between server tools, model tools, and feature tools.
Tool names mix two patterns: noun_verb (e.g., server_connect, model_create) and verb_noun (e.g., create_feature, set_parameters). While still readable, the inconsistency across the set reduces predictability.
With 18 tools, the set covers server lifecycle, model CRUD, geometry/mesh operations, parameters, and study runs without being bloated or insufficient for the domain.
The tools cover core workflows: server management, model creation/loading/saving, parameter manipulation, feature creation/deletion/update, and running sequences/studies. Missing result extraction and mesh-specific feature creation are minor gaps.