optivibe-mcp
ZOS-API automation, typed tools, and the MCP server for optivibe-mcp. Drives
Zemax OpticStudio through the typed ZOS-API (.NET via pythonnet / clr), and
composes the optivibe-reference grounding layer in-process so everything is
served through one MCP.
It exposes more than 80 typed tools — loading and editing designs, analyses, merit-function construction, optimization, and tolerancing — each returning a uniform result envelope rather than raising, so a caller checks a read-back value instead of assuming a call succeeded. OpticStudio is opened lazily on the first design-touching call and reaped automatically; one design at a time.
Install with pip install optivibe-mcp (Windows, Python 3.11+, and a Zemax OpticStudio
licensed for the ZOS-API). The repository README covers
building the reference data and registering the server with Claude Code, and AGENTS.md in
the repository describes the usage model.
Metadata
Release files for optivibe-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)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| optivibe_mcp-0.2.0.tar.gz | 1.8 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| optivibe_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.7 MB
Release files / optivibe_mcp-0.2.0.tar.gz
| Download URL | optivibe_mcp-0.2.0.tar.gz |
|---|---|
| Size | 1.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d1251d622e346c312e1b2e2c540361cf26a49706e2b7be68fbda9a997130a334
|
|
BLAKE2b-256 checksum How to use checksums |
b619fafe8880c1d51fa30de7ead4ea5caf41da99171aeb2fb833d74890b05c4b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 23, 2026.
Transparency logRelease files / optivibe_mcp-0.2.0-py3-none-any.whl
| Download URL | optivibe_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 1.9 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8b6418eb04b8eb3239c131f3f4a497f738e5f784b11d885da2ee44d7d9f41426
|
|
BLAKE2b-256 checksum How to use checksums |
b82477a9c5f2d8e524ace480af98ed63bc86f0348d64327d8b3d476f2e0b4450
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 23, 2026.
Transparency logSecurity for optivibe-mcp 0.2.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for optivibe_mcp-0.2.0.tar.gz
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 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.