Aspenhysys MCP Server
Aspen HYSYS simulations controlled via natural language with 51 specialized tools.
Data last scanned today · Reviewed today
Overview
The Aspenhysys MCP Server provides a bridge between AI assistants and Aspen HYSYS using Windows COM Automation. It enables users to perform complex process engineering tasks, such as querying stream values, monitoring simulation convergence, and building flowsheets, directly through natural language interactions. By supporting 51 distinct tools, the server covers extensive simulation management, from session control to detailed model modification. The server emphasizes safety through a configurable mode system managed by the HYSYS_MCP_MODE environment variable. It defaults to a read-only or session-limited state, preventing accidental model changes. Advanced users can elevate permissions to an 'enhanced' mode to unlock write capabilities, solver execution, and automated flowsheet construction.
Our verdict
With a high-risk security score of 24/100, users should exercise caution. The server is community-maintained rather than vendor-official and has not undergone an independent editorial security review. While the server provides an explicit read-only safety mode by default to mitigate unintended operations, it operates via Windows COM automation, which carries inherent risks when granting write access. This tool is best suited for experienced HYSYS users capable of monitoring the implications of automated model edits.
- Provides 51 tools for comprehensive HYSYS simulation management
- Configurable safety modes prevent accidental write operations by default
- Zero direct dependencies simplifies the supply-chain surface
- Verified functionality on HYSYS V14
- High-risk security score requires careful environment configuration
- Community-maintained project lacking official AspenTech support
- Strictly limited to Windows environments using COM
- Bus-factor risk due to being maintained by one contributor
Tools
| Tool | Description | Risk |
|---|---|---|
| hysys_list_streams | Lists all streams in the current HYSYS simulation. | low |
| hysys_get_stream | Retrieves the values and properties of a specific stream. | low |
| hysys_list_unit_ops | Lists all unit operations present in the simulation. | low |
| hysys_get_status | Gets the current convergence status of the simulation. | low |
| hysys_list_column_specs | Lists the current column specifications. | low |
| hysys_get_column_profile | Gets the profile data for a specific column. | low |
| hysys_balance_check | Performs a mass balance check for the simulation. | low |
| hysys_get_stream_phys | Retrieves the physical properties of a specific stream. | low |
| hysys_introspect | Performs introspection on objects within the simulation. | low |
| hysys_list_components | Lists the components defined in the fluid package. | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›What are the system requirements for running the HYSYS MCP Server?
The server requires Windows 10 or 11, Aspen HYSYS V12 or later (V14 is verified), and a native Windows Python 3.10+ installation with the pywin32 library.
›Can I run this MCP server from WSL or Linux?
No, the server must be executed using native Windows Python because it relies on COM Automation to interface with the HYSYS application.
›What is the purpose of the HYSYS_MCP_MODE environment variable?
It controls the safety level of the server by limiting which tools are exposed. The default 'default' mode restricts the server to read and session management, while 'enhanced' mode enables write and flow-sheet building tools.
›Are write operations enabled by default?
No, write operations are disabled by default to prevent accidental model changes. You must explicitly set HYSYS_MCP_MODE to 'enhanced' in your configuration to enable these functions.
›Are there any limitations to the stream disconnection tool?
Yes, the hysys_disconnect_stream tool is unsupported due to HYSYS V14 COM API limitations. You must use other methods like re-connecting via connect_stream, deleting objects, or manual GUI intervention.
›Do I need an existing case to use the flow-sheet building tools?
Yes, the flow-sheet building tools require a case with pre-defined components and Fluid Packages, as these operations will fail in an empty simulation case.
Badge
Maintain this server? Add the live badge to your README.