Metadata-Version: 2.4
Name: optivibe-mcp
Version: 0.2.0
Summary: OptiVibe harness: ZOS-API automation, typed tools, and the single OptiVibe MCP
License: Apache-2.0
Project-URL: Homepage, https://github.com/chuang44-tiff/optivibe-mcp
Project-URL: Issues, https://github.com/chuang44-tiff/optivibe-mcp/issues
Project-URL: Changelog, https://github.com/chuang44-tiff/optivibe-mcp/blob/main/CHANGELOG.md
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Programming Language :: Python :: 3.11
Classifier: Operating System :: Microsoft :: Windows
Requires-Python: >=3.11
Description-Content-Type: text/markdown
Requires-Dist: pythonnet
Requires-Dist: mcp<2,>=1.28
Requires-Dist: psutil
Requires-Dist: anyio
Requires-Dist: matplotlib>=3.6
Requires-Dist: numpy
Requires-Dist: pillow
Requires-Dist: optivibe-reference==0.2.0
Provides-Extra: dev
Requires-Dist: pytest; extra == "dev"

# optivibe-mcp

<!-- mcp-name: io.github.chuang44-tiff/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](https://github.com/chuang44-tiff/optivibe-mcp#readme) covers
building the reference data and registering the server with Claude Code, and `AGENTS.md` in
the repository describes the usage model.
