abaqus

This MCP server is designed to work with an already-running Abaqus/CAE GUI session. It exposes two main MCP tools: execute_script_in_abaqus_gui and get_abaqus_gui_message_log. The first tool submits a Python script to be executed within the active Abaqus GUI session by automating the File -> Run Script... workflow. The second tool attempts to read the text content from the Abaqus GUI message/log area, which typically appears at the bottom of the main window. Use these tools in sequence to run code inside Abaqus and then retrieve any resulting messages or logs to verify outcomes. Note that this server does not start or stop Abaqus; it relies on an open Abaqus/CAE session and uses GUI automation via pywinauto, so reliability can vary with UI changes, screen resolution, and modal dialogs.

Prerequisites:

• Python 3.7 or newer
• Abaqus/CAE installed and an Abaqus GUI session running
• Git (optional, for cloning the repository)

Install the Python dependencies specified by the project:

pip install -r requirements.txt

Start the MCP server from the server's directory:

python mcp_server.py

Usage steps:

1. Ensure Abaqus/CAE GUI is open and responsive. The server will interact with this existing session.
2. Run the MCP server (as shown above).
3. Use MCP clients or tooling to call the available tools, e.g., execute_script_in_abaqus_gui with a Python code string, then call get_abaqus_gui_message_log to fetch any messages produced by the script.

If you need to adjust UI interaction behavior, you may need to modify the server code to account for your Abaqus version and UI element identifiers.

Tips and caveats:

• The server only interacts with an already-running Abaqus GUI session; it will not launch Abaqus itself.
• GUI automation depends on UI element stability; changes in Abaqus version, window size, or themes can affect element detection.
• If get_abaqus_gui_message_log struggles to capture content, consider refining UI element selectors or using UI inspection tools to identify reliable properties (AutomationId, Name, ClassName).
• Ensure Abaqus is the foreground window when performing automation for more reliable results.
• Distinguish between errors raised by the MCP tooling (e.g., window not found) and errors produced within Abaqus during script execution, which will appear in the Abaqus message log.
• Timeouts and sleep delays in the script may need tuning for slower Abaqus responses in your environment.