inspire-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INSPIRE_ROOT | No | Path to the Altair Inspire install root, Inspire folder, or ExecWinEnvInsp.exe. Can also be set with --inspire-root; if omitted, the server auto-detects Inspire. | |
| INSPIRE_MCP_RUNS | No | Directory for per-call run folders. Can also be set with --runs-dir; defaults to ./runs next to the script. Keep this path ASCII-only. |
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 |
|---|---|
| inspire_statusA | Report whether Altair Inspire is installed/found, its version, batch executor path, running Inspire-related processes, free memory and the runs directory. Does not start Inspire. |
| inspire_run_pythonA | Run Python code inside a fresh headless Altair Inspire process.
Pre-defined names: |
| inspire_model_infoA | Open a model file read-only in headless Inspire (.stmod, .fem and other formats Inspire can open) and summarize parts (dimensions, mass, volume, material, sheet thickness), load cases, loads and contacts (bounding_box = minimum bounding box x/y/z). The file is not saved or modified. units: e.g. MKS, MMKS. |
| inspire_h3d_summaryB | Read an OptiStruct .h3d result file in headless Inspire and return, for each analysis run, the list of available result types and min/max (with positions) for the requested fields (default: Displacement, von Mises Stress) at the first subcase/step. |
| inspire_export_optistructA | Open a model in headless Inspire and export an OptiStruct input deck (.fem) for its parts and the given load cases (default: all), using inspire.OptiStructAnalysis.export. element_size_m is in metres. Refuses to overwrite an existing output file. Does not run the solver. Export happens in an ASCII-only staging folder and the .fem is then copied to output_fem (Inspire 2026 export hangs on non-ASCII output paths). |
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 5 tools
Each tool targets a distinct stage of the headless Inspire workflow: status check, Python execution, model inspection, result reading, and OptiStruct export. The main overlap is that inspire_run_python is a generic escape hatch that could technically replicate model_info, h3d_summary, or export, but the dedicated tools' descriptions make their intended scope clear.
All five tools share the inspire_ prefix and snake_case, giving a predictable namespace. Minor deviation: three names are noun-style (status, model_info, h3d_summary) while two are verb_noun (run_python, export_optistruct), so the verb convention isn't fully uniform.
Five tools is well within the ideal 3-15 range and each covers a distinct workflow need without redundancy. The generic run_python handles arbitrary scripting, so no bloat of convenience wrappers is needed.
The surface covers discovery, execution, model inspection, results extraction, and export — a coherent lifecycle for headless Inspire automation. Gaps remain: there is no dedicated tool to run the solver (export explicitly does not solve) and no model save/conversion flow, though inspire_run_python can bridge most of these.