Tools and capabilities#
You can use these tools from the default MCP surface:
Tool |
Purpose |
|---|---|
|
Inspect the active CFX session state. |
|
Connect to CFX resources. |
|
Release active sessions. |
|
Coordinate lifecycle actions such as CFX-Pre, CFX-solver, and CFD-Post workflows. |
|
Retrieve bounded model context, API help, named objects, and state snippets. |
|
Run validated Python code in the configured backend. |
|
Pre-check Python code before execution. |
Recommended tool order#
Use the tools in this order for most workflows:
Run
session_statusto see whether a backend is connected.Run
connectorcfx_workflowwithstart_prewhen you need a CFX-Pre session.Run
cfx_model_contextto inspect named objects, allowed values, or a selected state.Run
cfx_workflowfor lifecycle operations such as importing meshes, writing solver input, running the solver, and opening results.Use
validate_codeonly when your task requires custom PyCFX code.Run
run_codeonly after validation and user approval in your MCP client.
Language-model ownership#
PyCFX-MCP is a deterministic leaf server and does not call a server-side
language model. Custom code authoring belongs in the MCP host or a higher-level
agent layer. This server validates and executes reviewed Python through
validate_code and run_code.
Common workflow actions#
Action |
Example request |
|---|---|
|
Start CFX-Pre to prepare a setup. |
|
Import this mesh file into the active CFX-Pre session. |
|
Write a solver input file for the current setup. |
|
Start the solver for this solver input file. |
|
Wait until the current solver run finishes. |
|
Return the result file produced by the solver run. |
|
Open this result file in CFD-Post. |
Context inspection actions#
Ask for targeted context instead of broad dumps. For example:
Find named boundary objects that contain
inlet.Show allowed values for a selected boundary setting.
Return API help for a specific CFX path.
Fetch state only for these paths and named-object types.