Skip to content

feat: manage PyAnsys MCP installations and coding-agent profiles - #658

Open
tusharbana-ansys wants to merge 14 commits into
mainfrom
codex/pyansys-mcp-manager
Open

tusharbana-ansys wants to merge 14 commits into
mainfrom
codex/pyansys-mcp-manager

Conversation

@tusharbana-ansys

@tusharbana-ansys tusharbana-ansys commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Interface

  • Add a dedicated PyAnsys MCPs tab with clear installation, server, and coding-agent sections.
  • Keep dedicated Python selectable after installation and preserve separate environments when switching interpreters.
  • Filter unsupported Python versions; allow explicit advanced selections subject to package requirements.
  • Load strict, noneditable version dropdowns from PyPI or offline wheelhouses, with Latest selected by default.
  • Keep navigation responsive with shared discovery snapshots and hidden background probes.
  • Offer installed-release launch options and guide configuration through review and save.

Installation and connections

  • Manage PyAEDT, PyMechanical, PyFluent, PyMAPDL, PyLumerical, and PyCFX in dedicated or existing environments.
  • Support Latest releases, pinned versions, official Git sources, offline wheelhouses, updates, and cancellation.
  • Provide product-specific HTTP controls and stop manager-owned processes on shutdown.
  • Update existing agent entries and recognized aliases without duplicate servers or lost user preferences.
  • Preserve unrelated settings and environment variables, with backups and concurrent-edit protection.
  • Support current/legacy VS Code formats and OpenCode V2 profiles while preserving existing V1 layouts.

Validation

  • Pass 150 local tests; skip one unsupported Claude Desktop HTTP scenario.
  • Pass all 31 CI checks, including all 10 required contexts; three deployment/release-only jobs skip.
  • Cover Windows/Ubuntu Python 3.10–3.14 and Fedora 40/CentOS Stream 9 Qt integration.
  • Verify real dedicated installations with Python 3.12 and 3.13, plus six stdio and five HTTP connections.
  • Validate OpenCode profiles against its official schema and parse generated profiles with the installed Codex CLI.
  • Check the packaged Windows selectors and review flow, plus actual user configuration destinations on a normal launch.
  • Verify the signed installer matches this commit and passes signature and archive integrity checks.
  • Download the signed Windows preview built from a2c140b.

@github-actions github-actions Bot added documentation Improvements or additions to documentation maintenance Package and maintenance related labels Nov 17, 2026
@tusharbana-ansys
tusharbana-ansys marked this pull request as ready for review November 17, 2026 08:49
@tusharbana-ansys
tusharbana-ansys marked this pull request as draft November 17, 2026 10:17
@tusharbana-ansys
tusharbana-ansys marked this pull request as ready for review November 17, 2026 10:57
@tusharbana-ansys
tusharbana-ansys marked this pull request as draft November 18, 2026 10:24
@tusharbana-ansys
tusharbana-ansys marked this pull request as ready for review November 18, 2026 11:06
@RobPasMue

Copy link
Copy Markdown
Member

@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). =)

@tusharbana-ansys
tusharbana-ansys marked this pull request as draft November 19, 2026 08:33
@tusharbana-ansys
tusharbana-ansys marked this pull request as ready for review November 19, 2026 08:58
@tusharbana-ansys
tusharbana-ansys marked this pull request as draft November 20, 2026 06:53
@tusharbana-ansys
tusharbana-ansys marked this pull request as ready for review November 20, 2026 07:05
@tusharbana-ansys

Copy link
Copy Markdown
Contributor Author

@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.
You can start reviewing now.
Please let me know your thoughts & recommendations on the UI?

@RobPasMue RobPasMue left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Comment on lines +32 to +34
# 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 }}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Comment thread doc/source/mcp.rst
Comment on lines +13 to +44
.. 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

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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"]

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aren't you running the "validate_mcp" test?

"pymechanical",
"PyMechanical MCP",
"ansys-mechanical-mcp",
">=3.12,<3.15",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should be able to extract this info from PyPI

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But keep it if desired - I just think it will imply a lot of manual maintenance

@RobPasMue

Copy link
Copy Markdown
Member

Overall it seems to be working fine - a very reactive UI, I like it =)

Just one recommendation:

image

I would clarify (somehow, on the tab name) that "Server settings" is only needed for shared instances of the MCP server (multiple clients) and "Coding agents" is for single-client sessions inside IDEs...

I wanted to use it with my IDE directly and ended up launching it in HTTP mode (which was not the right path). Maybe reordering the tabs? Anyway.. let's try to figure out the UX path here.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation maintenance Package and maintenance related

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants