impeccable
The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.
Lens design automation for Zemax OpticStudio through the typed ZOS-API
教 AI 做这类工作的 Skill,可与本项一起使用
The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.
Editorial diagram design for Claude Code, Codex, GitHub Copilot, Cursor, Factory Droid, Qoder, and Pi. 45 diagram types. Self-contained HTML + SVG. No shadows. No Mermaid slop.
Create beautiful slides on the web using a coding agent's frontend skills
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 16/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 28/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 OptiVibe。按照 https://mcp.popnx.com/i/chuang44-tiff-optivibe-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server OptiVibe,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "optivibe": { "command": "uvx", "args": [ "optivibe-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 OptiVibe 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"optivibe": {
"command": "uvx",
"args": [
"optivibe-mcp"
]
}
}
}用 OptiVibe 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 OptiVibe,或回答中出现 OptiVibe 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 OptiVibe
OptiVibe 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 OptiVibe 的应用
B · 设计、图片与音频 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server OptiVibe,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user optivibe -- uvx optivibe-mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 OptiVibe 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user optivibe -- uvx optivibe-mcp应能看到 OptiVibe 在列表中并显示已连接
用 OptiVibe 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 OptiVibe,或回答中出现 OptiVibe 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server OptiVibe,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "optivibe": { "command": "uvx", "args": [ "optivibe-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 OptiVibe 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 OptiVibe 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 OptiVibe,或回答中出现 OptiVibe 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server OptiVibe,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "optivibe": { "type": "stdio", "command": "uvx", "args": [ "optivibe-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 OptiVibe 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 OptiVibe 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 OptiVibe,或回答中出现 OptiVibe 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user optivibe -- uvx optivibe-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"optivibe": {
"command": "uvx",
"args": [
"optivibe-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"optivibe": {
"command": "uvx",
"args": [
"optivibe-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"optivibe": {
"type": "stdio",
"command": "uvx",
"args": [
"optivibe-mcp"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 chuang44-tiff 验证,该账户拥有此仓库
代码最后更新于6天前
使用 Apache-2.0
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 optivibe-mcp@0.2.3 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/chuang44-tiff-optivibe-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于6天前,最新版本(0.2.3)于6天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:HyperFrames by HeyGen, Pascal 3D Editor, draw.io, Figma MCP Server, Remocn: Remotion MCP server
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Official HyperFrames by HeyGen: the best AI video editor in chat. Captions, motion graphics, MP4.
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
Create draw.io diagrams in chat from Mermaid or XML, shown live and interactive. 10,000+ shapes.
The Figma MCP server brings Figma design context directly into your AI workflow.
Hosted MCP for Remotion videos: search Remocn components, read docs, plan a video, preview it.
| 本项 OptiVibe | HyperFrames by HeyGen | Pascal 3D Editor | draw.io | Figma MCP Server | Remocn: Remotion MCP server | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 否 | 否 | 是 | 否 |
| 基础检查 | 3/3 | 4/4 | 5/5 | 4/4 | 4/4 | 4/4 |
| 许可证 | Apache-2.0 | Apache-2.0 | MIT | Apache-2.0 | – | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Lens design with an AI agent. optivibe-mcp gives a coding agent such as Claude Code typed tools for Zemax OpticStudio, and skills that take a lens from its first form through glass choice to an as-built tolerance check. It is experimental.
*One unattended run: a 60× objective reworked into a 10× / NA 0.45 apochromat, polychromatic Strehl ≥ 0.935 at every field point. How it was done and measured.*
pip install optivibe-mcp "optivibe-reference[manual]"
optivibe-build-data --probe claude mcp add optivibe -- C:/path/to/venv/Scripts/optivibe-mcp.exe
On PyPI and in the official MCP Registry as io.github.chuang44-tiff/optivibe-mcp. Details: Install.
optivibe-mcp, in packages/optivibe-harness/) drive OpticStudio over the ZOS-API: load and edit lenses, analyse, optimize, trial glass swaps and tolerance. Beyond spherical surfaces they author aspheres, coordinate breaks, fold mirrors, diffraction gratings and gradient-index media. Each returns a result envelope with read-backs instead of raising, so the agent checks a value rather than assuming a call worked.optivibe-reference) grounds the agent's choices: operand and glass lookups and manual search. Engine-free and licence-free; its data is built locally (see Build the reference data).The project ships code only. No vendor data (glass catalog, manual text, operand descriptions) is included; you generate it from your own licensed OpticStudio install.
| Demo | Result |
|---|---|
| A 60× objective reworked into a 10× apochromat, unattended | Strehl ≥ 0.935 at all four field points in one run |
| The same job on a local model | Strehl ≥ 0.834 with a tuned brief; the page says where it trails Opus |
| Refining a 20× zoom | Blur at the worst zoom position more than halved; the distortion target missed |
| Does the agent design better when it sees the drawing? | Every vision run made a shorter lens: 70–100 mm against 140–221 mm |
| The glass step against OpticStudio's Hammer | On the 10×, all three runs beat Hammer's merit by 12–19 % |
| Desensitizing a finished 10× so more built lenses pass | Builds diffraction-limited at every field: 57.50 % to 69.25–74.65 % in four runs |
Each demo ships its brief and lens files; demos/ lists them and has a script that re-measures a lens file.
IsValidLicenseForAPI.PYTHONNET_RUNTIME=netfx and locates your install directory (via env override, registry, or a Program Files scan). No manual setup.In a Python 3.11+ virtual environment:
pip install optivibe-mcp "optivibe-reference[manual]"
optivibe-build-data --probe optivibe-doctor
Both packages are on PyPI: optivibe-mcp and optivibe-reference, released together with matching versions. optivibe-mcp is the server; it brings the reference layer (optivibe-reference) with it. The [manual] extra (PyMuPDF) is optional and reads your OpticStudio manual PDF (see Manual install). optivibe-build-data builds the reference data from your own OpticStudio install, and --probe also runs the two operand probes, which open OpticStudio and need the ZOS-API licence. optivibe-doctor checks the install. Then register the server with Claude Code.
optivibe-build-data writes into the installed package's data/ and data/captures/ directories, so install optivibe-mcp into a virtual environment (or with pip install --user) rather than into a system Python whose site-packages is not writable.
Clone the repository, then run one command from its root:
powershell -ExecutionPolicy Bypass -File install.ps1
It creates a virtual environment in .venv, installs both packages, builds the reference data from your OpticStudio install, runs the doctor, and prints the command that registers the server with Claude Code. It opens no OpticStudio session. Options:
-Python : the Python 3.11+ to build the environment from, when the python on PATH is older;-Probe: also run the two operand probes, which open OpticStudio and need the ZOS-API licence (see Build the reference data);-Register: run the claude mcp add command for you.The script only runs the steps below, which you can also do by hand.
From packages/optivibe-harness/:
pip install -e ../optivibe-reference # reference layer first
pip install -e . # then the harness
Install the reference package first — the harness loads it in-process, and without it the reference and lookup tools won't be available.
The [manual] extra (PyMuPDF) reads your OpticStudio manual PDF. It is needed for both manual search and the operand/tolerance description enrichment (the build extracts verbatim descriptions from the PDF). Without it, the operand and tolerance catalogs build synonyms-only (grounding still works — every entry is searchable by its synonyms — but carries no manual descriptions). To get the full enriched build, install it:
pip install -e "../optivibe-reference[manual]"
A per-package environment.yml (Python 3.11) is provided if you prefer conda.
Then check the install:
python -m optivibe_doctor
It checks the interpreter, the two packages, their dependencies, the reference data and your OpticStudio install directory, and prints one line per check with a remedy for anything that is wrong. It opens no OpticStudio session unless you ask: --engine also opens one and proves the ZOS-API licence, and --boot starts the real server once. On a fresh install the reference-data checks read WARN until you build the reference data, and the exit code is 1 while any check warns.
claude mcp add optivibe -- /path/to/python -m optivibe_harness
/path/to/python is the interpreter of the environment you installed into — pointing it at a different Python is a common cause of silent failures. You can find it with:
python -c "import sys; print(sys.executable)"
The equivalent JSON configuration:
{ "command": "/path/to/python", "args": ["-m", "optivibe_harness"] }
After a PyPI install you can register the optivibe-mcp command instead. Give its full path (where optivibe-mcp prints it while the environment is active):
claude mcp add optivibe -- C:/path/to/venv/Scripts/optivibe-mcp.exe
Once the optimizer has settled a lens, three tools help with the glass step. explain_glass_swaps is read-only: it lists which glass elements carry the colour and Petzval terms. trial_glass_swaps tries up to four swap sets, each re-optimized beside an unchanged control, and judges them on measured image quality; it edits the open lens while it runs and restores it at the end. substitute_glass makes one swap and leaves it in place. The design-glass-matching skill runs this step.
To have Claude Code ask you before either tool that edits the lens runs, add an ask rule to your settings (for example .claude/settings.json):
{
"permissions": { "ask": ["mcpoptivibetrial_glass_swaps", "mcpoptivibesubstitute_glass"] } }
An ask rule takes precedence over an allow rule and still asks under bypassPermissions. In a headless run (claude -p) or in dontAsk mode there is no one to ask, so a matching call is denied.
The reference layer's data is built locally from your own licensed install; nothing vendor-derived is committed. After a PyPI install, run optivibe-build-data (add --probe to run the two probes below first); it needs no clone. From a clone, run it from the repository root:
python packages/optivibe-reference/scripts/build_vendor_data.py
This reads the glass catalog from your .agf files (ZEMAX_GLASSCAT) and, if you point it at the manual PDF (OPTIVIBE_MANUAL_PDF), indexes it for search.
The operand and tolerance catalogs are built from a live probe of your install's ZOS-API enum surface. Run the two probes once first (each boots a headless OpticStudio session, reads the operand/tolerance surface, and reaps it):
python packages/optivibe-reference/scripts/probe_operands.py
python packages/optivibe-reference/scripts/probe_tolerances.py
If an input is missing the corresponding step is skipped: that tool (glass or manual search, or operand/tolerance lookup) returns a typed "unavailable" result and the rest of the server keeps working. Details and the data-source ledger are in PROVENANCE.md.
OpticStudio is not opened at startup — the engine is launched on the first tool call that touches a design, and it works with one design at a time. The reference and lookup tools work with no engine running — so install, registration, the reference build, and every lookup succeed regardless of license tier; the ZOS-API license is checked only when the engine opens.
A note on trust: tools return a result envelope and don't raise on failure, so a call completing is not proof it did what you intended. Check the returned value or the optimizer's verdict rather than the absence of an error.
The repository includes a few Claude Code skills for common tasks:
| Skill | For |
|---|---|
design-review | Assess a design against a spec |
design-compare | Compare designs side by side |
design-vision-review | Observe a rendered layout and report what lens data does not show (advisory) |
design-aberration-review | Read the ray fan and field curvature / distortion plots and report how the aberrations are balanced (advisory) |
optimize-loop | Run optimization with monitoring |
design-glass-matching | Choose glass for a settled lens: find the elements that carry the colour or field-curvature terms, trial swaps against a control, and keep a swap only when overall image quality improves |
design-tolerance-desensitize | The last finishing stage: pick the push compensator, find the tolerance hotspots, and keep a change only when the as-built yield improves |
bench-catalog | Benchmark and rank a folder of lens designs against a target spec or each other |
zos-api-debug | Troubleshoot OpticStudio connection / license errors |
Experimental, early-stage and provided as-is; expect rough edges. It has been developed and exercised against a single OpticStudio version (2025 R1) on Windows; behavior on other versions is unverified. Interfaces and tool coverage may change.
Running another OpticStudio version or licence tier? Please open an issue with the output of