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
Skills that teach the AI this kind of work; they work alongside this one
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
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 16/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 28/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install OptiVibe. Follow https://mcp.popnx.com/i/chuang44-tiff-optivibe-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server OptiVibe for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "optivibe": { "command": "uvx", "args": [ "optivibe-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the OptiVibe tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
SettingsDeveloperEdit Config
{
"mcpServers": {
"optivibe": {
"command": "uvx",
"args": [
"optivibe-mcp"
]
}
}
}Use OptiVibe and tell me what you can do for me, then show me one thing✓ If Claude says it is using OptiVibe or shows a OptiVibe tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect OptiVibe yet
OptiVibe runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect OptiVibe
B · Others in Design, images & audio that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server OptiVibe for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user optivibe -- uvx optivibe-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the OptiVibe tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user optivibe -- uvx optivibe-mcpYou should see OptiVibe listed as connected
Use OptiVibe and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using OptiVibe or shows a OptiVibe tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server OptiVibe for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "optivibe": { "command": "uvx", "args": [ "optivibe-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the OptiVibe tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Use OptiVibe and tell me what you can do for me, then show me one thing✓ If Cursor says it is using OptiVibe or shows a OptiVibe tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server OptiVibe for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "optivibe": { "type": "stdio", "command": "uvx", "args": [ "optivibe-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the OptiVibe tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Use OptiVibe and tell me what you can do for me, then show me one thing✓ If VS Code says it is using OptiVibe or shows a OptiVibe tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
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"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account chuang44-tiff, which owns the repo
Code last changed 6 days ago
Uses Apache-2.0
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for optivibe-mcp@0.2.3
Checks only this package version, not every dependency · checked Nov 15, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/chuang44-tiff-optivibe-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 6 days ago, and the latest version (0.2.3) reached the registry 6 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: HyperFrames by HeyGen, Pascal 3D Editor, draw.io, Figma MCP Server, Remocn: Remotion MCP server
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.
Hosted MCP for Remotion videos: search Remocn components, read docs, plan a video, preview it.
| This one OptiVibe | HyperFrames by HeyGen | Pascal 3D Editor | draw.io | Figma MCP Server | Remocn: Remotion MCP server | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | Yes | No | No | Yes | No |
| Basic checks | 3/3 | 4/4 | 5/5 | 4/4 | 4/4 | 4/4 |
| License | Apache-2.0 | Apache-2.0 | MIT | Apache-2.0 | – | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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