inspire-mcp
Drives Altair Inspire on Windows through its headless batch mode: runs Python inside Inspire (e.g. creating geometry, querying models), inspects models and their parts/materials/load cases, summarizes OptiStruct .h3d results (min/max displacement, stress), and exports OptiStruct .fem input decks.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@inspire-mcp summarize von Mises stress results in C:\models\bracket.h3d"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
inspire-mcp
A small Model Context Protocol (stdio) server that lets an AI agent
(Cursor, Codex, Claude Desktop, ...) drive Altair Inspire on Windows through Inspire's
official headless batch mode and its Python API (hwx.inspire).
Unofficial. Not affiliated with or endorsed by Altair. You need your own licensed Inspire install.
Tested with: Altair Inspire 2026.0 (release file 2026, embedded Python 3.10.18) on Windows 11,
mcp 1.30 (Python 3.13 venv), Cursor CLI and its MCP client.
How it works
Each tool call writes a small Python script into a fresh run folder and launches
<Inspire>\hwx\bin\win64\ExecWinEnvInsp.exe -cfg -b -p Inspire -ex hwx.exe -f <run>\task.pyThe script runs inside Inspire's own interpreter with from hwx import inspire available, writes
result.json, and Inspire exits. Consequences:
No GUI is opened and an Inspire window you already have open is never touched.
No state is kept between calls (each call is a new process, ~2-15 s startup, longer for big models). Save to a
.stmodif you need to continue in a later call.On timeout, only the batch process tree started by that call is terminated.
Calls are serialized (one Inspire batch process at a time per server).
Each run folder keeps
user_code.py,args.json,result.json,stdout.log,stderr.log.
Related MCP server: Windows-MCP
Tools
Tool | What it does |
| Is Inspire found, install root, release/version, batch executor path, running Inspire processes, free RAM. Does not start Inspire. |
| Run arbitrary Python inside a fresh headless Inspire. Names provided: |
| Open a model read-only ( |
| Open an OptiStruct |
| Export an OptiStruct input deck ( |
Example for inspire_run_python:
m = inspire.newModel()
m.createSolidBlock(x=0.02, y=0.01, z=0.005)
b = inspire.geometry.minBoundingBox(m.parts)
result = {"parts": len(m.parts), "bbox_m": [b.x, b.y, b.z]}API reference: https://help.altair.com/inspire/inspireapi/index.html
Install
Requires Windows, Altair Inspire with a working license, and Python 3.10+ for the server itself (the server does not need Inspire's Python; it just launches Inspire).
git clone https://github.com/zchenjun88-hash/inspire-mcp.git
cd inspire-mcp
python -m venv venv
.\venv\Scripts\python.exe -m pip install -r requirements.txt
# quick check: prints status and runs a tiny script inside Inspire
.\venv\Scripts\python.exe inspire_mcp_server.py --self-testFinding Inspire
In this order:
--inspire-root <path>command-line argumentINSPIRE_ROOTenvironment variableAuto-detect on all drives:
X:\Altair Inspire*\Inspire*\,X:\Program Files\Altair\*\Inspire*\,X:\Program Files\Altair\*\,X:\Altair\*\Inspire*\
The path may be the install root (e.g. C:\Program Files\Altair\2026), the Inspire2026 folder,
or ExecWinEnvInsp.exe itself.
Run folders go to --runs-dir, else INSPIRE_MCP_RUNS, else ./runs next to the script.
Keep this path ASCII-only (see Known issues).
Cursor
%USERPROFILE%\.cursor\mcp.json:
{
"mcpServers": {
"inspire": {
"command": "C:\\path\\to\\inspire-mcp\\venv\\Scripts\\python.exe",
"args": ["-u", "C:\\path\\to\\inspire-mcp\\inspire_mcp_server.py",
"--inspire-root", "C:\\Program Files\\Altair\\2026"]
}
}
}For the Cursor CLI (agent), you can pre-approve the tools by adding "Mcp(inspire:*)" to
permissions.allow in %USERPROFILE%\.cursor\cli-config.json, then check with agent mcp list.
Codex
%USERPROFILE%\.codex\config.toml:
[mcp_servers.inspire]
command = 'C:\path\to\inspire-mcp\venv\Scripts\python.exe'
args = ['-u', 'C:\path\to\inspire-mcp\inspire_mcp_server.py']
env = { INSPIRE_ROOT = 'C:\Program Files\Altair\2026' }
startup_timeout_sec = 30
tool_timeout_sec = 900 # exports of large models can take minutesOther clients
Any MCP client that can launch a stdio server works: command = the venv python.exe,
args = inspire_mcp_server.py plus optional --inspire-root.
Known issues / limits
Non-ASCII output paths hang OptiStruct export (observed on Inspire 2026: the batch process idles forever when the
.femtarget folder contains e.g. Chinese characters). The export tool therefore exports into an ASCII-only staging folder (inside the runs dir, or%SystemDrive%\inspire_mcp_stage) and copies the deck to your requested path. Opening models from non-ASCII paths worked fine. If you write your own export code withinspire_run_python, use ASCII paths.Not a live-GUI bridge: it cannot see or change the model currently open in your Inspire window.
inspire_h3d_summaryreads the first subcase/step; field names must match the names listed inavailable(shell models, for instance, may not exposevon Mises Stress).inspire_run_pythonexecutes arbitrary code with your user's permissions. Only connect it to agents you trust and review what they run.Some MCP clients have short default tool timeouts (Codex: 60 s). Raise them for exports.
中文说明
这是一个让 AI 助手(Cursor、Codex 等)通过 MCP 操作 Altair Inspire 的小服务。原理是调用 Inspire 官方的
无界面批处理(ExecWinEnvInsp.exe -cfg -b -p Inspire -ex hwx.exe -f 脚本.py),在 Inspire 自带的 Python 里执行
hwx.inspire 接口。每次调用都是一个全新的后台 Inspire 进程,不会打开界面,也不会碰你已经开着的 Inspire 窗口;
调用之间不保留状态,需要接着做的请先保存成 .stmod。
已测试版本:Altair Inspire 2026.0(Windows 11)。工具:inspire_status(安装/版本状态)、
inspire_run_python(在 Inspire 里跑任意 Python,给 result 赋值即可返回)、inspire_model_info(读取模型的零件、
材料、载荷工况)、inspire_h3d_summary(读取 .h3d 结果的最大/最小值)、inspire_export_optistruct(导出 OptiStruct .fem)。
安装:python -m venv venv,venv\Scripts\python.exe -m pip install -r requirements.txt,然后按上面的
Cursor / Codex 配置登记。Inspire 安装路径可用 --inspire-root 参数或 INSPIRE_ROOT 环境变量指定,不指定会自动搜索。
注意:导出路径含中文时 Inspire 2026 的 OptiStruct 导出会卡死,本工具已自动先导出到纯英文临时目录再复制过去; 自己写导出脚本时请用纯英文路径。需要有效的 Inspire 许可证。
License
MIT, see LICENSE.
Available Tools
5 toolsinspire_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).
Inputs: model_path (required), output_fem (required), run_name, timeout_s, +2 more.
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.
Inputs: path (required), units, fields, timeout_s.
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.
Inputs: path (required), units, timeout_s.
inspire_run_pythonA
Run Python code inside a fresh headless Altair Inspire process.
Pre-defined names: inspire (hwx.inspire module), RUN_DIR (a scratch folder for this run).
Assign result = ... to return data; print() output is captured in stdout.
Example: m = inspire.newModel(); m.createSolidBlock(x=0.01, y=0.01, z=0.01); result = len(m.parts)
Inputs: code (required), timeout_s.
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.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
Connect ChatGPT, Claude, Cursor or VS Code to your Windows PC: files, terminal, browser, apps.
Connect AI assistants to your approved computer for files, commands, browser and desktop tasks.
Parametric 3D CAD for AI agents: build print-ready parts, check them, export STL, 3MF or STEP.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with Windows operating systems through native UI automation, file navigation, application control, and system commands. Provides seamless integration between LLMs and Windows environments for tasks like clicking, typing, launching apps, and capturing desktop state.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with the Windows operating system, performing tasks such as file navigation, application control, UI interaction, and QA testing.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to seamlessly integrate with the Windows operating system, performing tasks such as file navigation, application control, UI interaction, and QA testing via the MCP protocol.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to operate Windows computers with parallel, human-like input streams, including held keys, concurrent mouse/keyboard actions, UIA/OCR targeting, and a knowledge base for engineering software.1MIT