Skip to main content

Ansys CFX-MCP

PyAnsys Python Apache

Ansys CFX-MCP (ansys-cfx-mcp) is a Model Context Protocol (MCP) server that enables AI assistants to interact with Ansys CFX through PyCFX. It enables natural-language-assisted CFX-Pre, CFX Solver, and CFD-Post workflows for setup, execution, and postprocessing.

It is built on PyAnsys Common MCP (ansys-common-mcp), the shared PyAnsys MCP foundation.

This package is self-contained and works as a standalone server for any MCP host. It exposes a compact CFX-oriented tool surface so you can connect to CFX sessions, inspect bounded model context, validate and run reviewed PyCFX snippets, and coordinate common solver and CFD-Post actions.

For quick-start, configuration, architecture, examples, and per-tool reference material, see the PyCFX-MCP documentation.

Overview

Ansys CFX-MCP is a stateless MCP leaf. MCP clients such as Visual Studio Code Copilot, Claude Desktop, Cursor, or a custom automation host call a focused set of tools to drive live CFX-Pre, CFD-Post, and CFX Solver sessions. Custom Python runs through a validated, Python-level restricted execution path. This is not an operating-system or container sandbox.

Key features:

  • CFX session management: Start or attach to CFX-Pre, CFX Solver, and CFD-Post workflows.
  • Workflow routing: Use one compact cfx_workflow tool for common CFX lifecycle actions.
  • Bounded model context: Inspect summaries, named objects, API help, allowed values, and selected state snippets without dumping entire models into an MCP client.
  • Validated execution: Run custom snippets in a persistent PyCFX execution context with strict AST validation, guarded imports, and limited built-in functions.
  • Flexible MCP transport: Run over STDIO for local clients or Streamable HTTP for trusted local integrations.

Tool surface

The default MCP surface includes seven tools:

Group Tools
Connection and session connect, disconnect, and session_status
CFX workflow routing cfx_workflow
Bounded model context cfx_model_context
Code execution run_code and validate_code

The server also exposes a toolsets://definition MCP resource for clients or conductors that group related tools. The default CFX toolsets cover connection management, CFX workflow routing, CFX model context, and code execution.

Requirements

Requirement When needed Notes
Python 3.12 or later Always 3.12, 3.13 and 3.14 are supported
Core runtime dependencies Always (installed automatically) ansys-common-mcp, fastmcp, pydantic, and requests
A licensed local Ansys CFX installation To launch or attach CFX tools Required for workflows that use CFX-Pre, CFX Solver, or CFD-Post

PyCFX and Ansys CFX are required for live-session tools. Any tool that touches a CFX app (connect, run_code, cfx_workflow, cfx_model_context, and session_status) requires ansys-cfx-core and a licensed CFX installation on your machine.

Installation

Install the latest release for users:

pip install ansys-cfx-mcp

Install the latest release for developers:

git clone https://github.com/ansys/pycfx-mcp.git
cd pycfx-mcp
pip install -e ".[dev,doc]"

Usage

Run PyCFX-MCP over STDIO, the default transport for desktop MCP clients:

ansys-cfx-mcp --transport stdio

Or, run PyCFX-MCP over Streamable HTTP:

ansys-cfx-mcp --transport http --host 127.0.0.1 --port 8000

Use STDIO for desktop MCP clients that launch the server process. Use Streamable HTTP only on trusted networks or behind infrastructure that provides authentication and TLS.

Starting PyCFX-MCP only makes the tools available. You still need an MCP-compatible client, such as Visual Studio Code Copilot, Claude Desktop, Cursor, or another assistant host, to connect to PyCFX-MCP. For more information, see IDE and client configuration in the PyCFX-MCP documentation.

Configuration

The standalone server does not call a language model. Configure only the server transport, logging, and backend options needed for your MCP client. Custom code authoring belongs in the MCP host or a higher-level agent layer; PyCFX-MCP validates and runs reviewed Python through validate_code and run_code.

For transport settings, see Configuration in the PyCFX-MCP documentation.

License

This project is licensed under the Apache License, Version 2.0. See the LICENSE file for details.

Resources

For general PyAnsys questions, email pyansys.core@ansys.com.

Release files for ansys-cfx-mcp 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ansys-cfx-mcp 0.2.0
File Size Uploaded
ansys_cfx_mcp-0.2.0.tar.gz 307.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for ansys-cfx-mcp 0.2.0
File Interpreter ABI Platform
ansys_cfx_mcp-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 652.2 kB

Release files / ansys_cfx_mcp-0.2.0.tar.gz

Download URL ansys_cfx_mcp-0.2.0.tar.gz
Size 307.4 kB
Tags Source
SHA-256 checksum
How to use checksums
f7397a2e3c9cea1cb58324e61277744f58e60a532a04cf99c9abacd286df1438
BLAKE2b-256 checksum
How to use checksums
012f99b01469b6e47105c2b6cc36e132756937d0582fa7e04b638e93a18c77a1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 17, 2026.

Transparency log

Release files / ansys_cfx_mcp-0.2.0-py3-none-any.whl

Download URL ansys_cfx_mcp-0.2.0-py3-none-any.whl
Size 344.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e6bc2c2c9b8336f593f3f62597ed55ec20db9233bf6e2d0b48f53aa04477281e
BLAKE2b-256 checksum
How to use checksums
81eed2e3e15541706a49a742010bce3452447adf77183ca4cb0b034fb76c5892
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 17, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.2.0 This release

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page