How jianzhichun/abaqus-mcp-server works
This is an MCP bridge for automating an already-running Abaqus/CAE GUI. The principal workflow is a client submitting Python code, which the server stages and runs through Abaqus’s File → Run Script dialog; the client can then request a best-effort read of Abaqus’s message area to inspect outcomes. The server also exposes a scripting-strategy prompt. The excerpts show window discovery and GUI interaction, but omit portions of script staging and prompt registration, so those details rely on the README where noted.
Main entry points: mcp_server.py MCP server
Components 10
MCP interface
- MCP server
mcp_server.py - Script execution tool
mcp_server.py - Message log tool
mcp_server.py - Scripting prompt
mcp_server.py
GUI automation
- Window discovery
mcp_server.py - Temporary script file
mcp_server.py - GUI control
mcp_server.py
Abaqus application
- Abaqus/CAE GUI
- Message/log area
Other components
- MCP client
Connections 12
- MCP client → MCP server: sends requests
README.md - MCP server → Script execution tool: exposes tool
README.md - MCP server → Message log tool: exposes tool
README.md - MCP server → Scripting prompt: provides prompt
README.md - Script execution tool → Window discovery: finds window
mcp_server.py - Message log tool → Window discovery: finds window
mcp_server.py - Script execution tool → Temporary script file: stages code
README.md - Script execution tool → GUI control: automates dialog
mcp_server.py - GUI control → Abaqus/CAE GUI: submits script
mcp_server.py - Message log tool → Message/log area: scrapes text
mcp_server.py - Window discovery → Abaqus/CAE GUI: connects to
mcp_server.py - MCP client → Scripting prompt: consults prompt
README.md