PyAnsys Common MCP
PyAnsys Common MCP provides the infrastructure for building Model Context Protocol (MCP) servers for PyAnsys libraries.
Overview
This package provides the foundation for creating MCP servers that enable AI assistants (like Claude, ChatGPT) to interact with Ansys products through PyAnsys libraries.
Key features:
- Persistent Python sessions: Maintains stateful code execution across multiple AI requests.
- Lifecycle management: Handles startup, cleanup, and errors automatically.
- Extensible architecture: Uses base classes and patterns for product-specific implementations.
- Logging infrastructure: Uses pre-configured logging that does not interfere with the MCP protocol.
Installation
For users
The ansys.common.mcp package currently supports Python 3.12 through
Python 3.14 on Windows, Mac OS, and Linux.
Install the latest package for use with this command:
pip install ansys-common-mcp
Alternatively, install the latest PyAnsys Common MCP GitHub package with this command:
pip install git+https://github.com/ansys/pyansys-common-mcp.git
For developers
If you are contributing to PyAnsys Common MCP or creating custom servers, install the package in developer mode:
# Clone the repository
git clone https://github.com/ansys/pyansys-common-mcp.git
cd pyansys-common-mcp
# Install in editable mode with development dependencies
pip install -e .[dev]
# Or install documentation dependencies for building documentation
pip install -e .[doc]
Quick start
To create an MCP server for your PyAnsys library, follow these three main steps:
- Define your custom context: Extend the
PyAnsysBaseAppContextdataclass to store the product-specific state. - Implement your MCP server: Extend the
PyAnsysBaseMCPbase class with startup and cleanup logic. - Create MCP tools: Define tools that interact with your product.
Real-world example
For a complete, production-ready implementation, see the PyMAPDL-MCP repository.
Resources
For general PyAnsys questions, email pyansys.core@ansys.com.
Metadata
Release files for ansys-common-mcp 0.3.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ansys_common_mcp-0.3.6.tar.gz | 24.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ansys_common_mcp-0.3.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 52.9 kB
Release files / ansys_common_mcp-0.3.6.tar.gz
| Download URL | ansys_common_mcp-0.3.6.tar.gz |
|---|---|
| Size | 24.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
97bcf0a7fa701958b004409bf8bc039d7fa14c3f9ebca484fd12336a345f662b
|
|
BLAKE2b-256 checksum How to use checksums |
9ac0df1063a9a6d9009b063fb1a2b38973eec5f972f4a83d0129b26f9ba200c5
|
| 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 Oct 5, 2026.
Transparency logRelease files / ansys_common_mcp-0.3.6-py3-none-any.whl
| Download URL | ansys_common_mcp-0.3.6-py3-none-any.whl |
|---|---|
| Size | 28.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5c4f97576335ac14007184515659fa95200a84c80cdc5c1b58b383ae7a5ed1c7
|
|
BLAKE2b-256 checksum How to use checksums |
40057f69467312ecffb834653f1e42691ed105205c446b7bdad481c4a6e1793a
|
| 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 Oct 5, 2026.
Transparency log