Repository navigation
feat: manage PyAnsys MCP installations and coding-agent profiles - #658
tusharbana-ansys wants to merge 14 commits into
Conversation
|
@tusharbana-ansys - let me know when I can start reviewing (I know you've been changing the status of the PR several times from draft to ready and back). =) |
Hi @RobPasMue - Yeah, I was trying to optimize the UI & functionality of the new PyAnsys MCPs tab. |
RobPasMue
left a comment
There was a problem hiding this comment.
I will do a more "functional review" approach by downloading the app and trying it out. I'll keep you posted but for now you can see here a few comments
| # Preserve the Windows check names required by existing branch protection. | ||
| name: ${{ matrix.os == 'windows-latest' && format('Tests ({0})', matrix.python-version) || format('Tests ({0}, {1})', matrix.os, matrix.python-version) }} | ||
| runs-on: ${{ matrix.os }} |
There was a problem hiding this comment.
It's probably best if we delete this workaround for branch protection. I'll change the settings myself before merging so that this doesn't have an impact
| .. list-table:: Product launch contracts | ||
| :header-rows: 1 | ||
| :widths: 22 28 22 28 | ||
|
|
||
| * - Product | ||
| - Package | ||
| - Python baseline | ||
| - Transports | ||
| * - `PyAEDT MCP <https://github.com/ansys/pyaedt-mcp>`_ | ||
| - ``ansys-aedt-mcp`` | ||
| - 3.13–3.14 | ||
| - Stdio, HTTP | ||
| * - `PyMechanical MCP <https://github.com/ansys/pymechanical-mcp>`_ | ||
| - ``ansys-mechanical-mcp`` | ||
| - 3.12–3.14 | ||
| - Stdio, HTTP | ||
| * - `PyFluent MCP <https://github.com/ansys/pyfluent-mcp>`_ | ||
| - ``ansys-fluent-mcp`` | ||
| - 3.12+ | ||
| - Stdio, HTTP | ||
| * - `PyMAPDL MCP <https://github.com/ansys/pymapdl-mcp>`_ | ||
| - ``ansys-mapdl-mcp`` | ||
| - 3.12–3.14 | ||
| - Stdio, HTTP | ||
| * - `PyLumerical MCP <https://github.com/ansys/pylumerical-mcp>`_ | ||
| - ``ansys-lumerical-mcp`` | ||
| - 3.11+ | ||
| - Stdio | ||
| * - `PyCFX MCP <https://github.com/ansys/pycfx-mcp>`_ | ||
| - ``ansys-cfx-mcp`` | ||
| - 3.12–3.14 | ||
| - Stdio, HTTP |
There was a problem hiding this comment.
Are you sure you want to manually maintain this table? I don't think it's a good idea. Product versions will easily change, as well as supported transport methods. I would simply redirect to their doc pages if the users want any extra information
| COPY scripts/validate_mcp.py ./scripts/validate_mcp.py | ||
| ENV QT_QPA_PLATFORM=offscreen UV_LINK_MODE=copy | ||
| RUN uv venv --python 3.13 /opt/apm && uv pip install --python /opt/apm/bin/python -e '.[tests]' | ||
| CMD ["/opt/apm/bin/python", "-m", "pytest", "tests/test_mcp_backend.py", "tests/test_mcp_releases.py", "tests/test_mcp_compatibility.py", "tests/test_mcp_profiles.py", "tests/test_mcp_process.py", "tests/test_mcp_launch.py", "tests/test_mcp_tab.py", "-q", "--tb=short"] |
There was a problem hiding this comment.
Aren't you running the "validate_mcp" test?
| "pymechanical", | ||
| "PyMechanical MCP", | ||
| "ansys-mechanical-mcp", | ||
| ">=3.12,<3.15", |
There was a problem hiding this comment.
You should be able to extract this info from PyPI
There was a problem hiding this comment.
But keep it if desired - I just think it will imply a lot of manual maintenance

Interface
Installation and connections
Validation
a2c140b.