3DOptix

com.3doptixPublished by 3doptix.comOfficial publisherv1.0.0Updated Oct 24, 2026

Optical design, simulation and analysis with GPU-powered ray tracing. Import from Zemax and CAD.

VerifiedStreamable HTTPWeb executableDeveloper Tools Data & Analytics Media & Design

Server details

Identifier: com.3doptix/optical-design
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to 3doptix.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.3doptix%2Foptical-design.svg)](https://sourceweft.com/mcp/com.3doptix%2Foptical-design?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Connects an assistant to the 3DOptix cloud platform to build optical setups, run GPU ray-trace simulations and analyze results.

What you can do: Create and manage optical setups, including component placement and alignment, light sources and detectors, and catalog or custom optics. Import designs from Zemax and upload CAD files. Run GPU-powered ray-trace simulations and optical analysis such as spot diagrams and aberration checks. Optimize optical systems and render results.
When to use it: Use it when you want an assistant to design, simulate or analyze optical systems, such as building a beam expander or checking aberrations in an imported Zemax design, without leaving the coding agent. It suits optical engineering work that benefits from cloud GPU ray tracing. A bundled skill adds workflow guidance for Claude Code, Codex and Cursor. The server provides tools for setups, parts, optics and optomechanics catalogs, simulation, analysis and rendering.
Requirements: A remote endpoint reached over streamable HTTP at the 3DOptix MCP server. A 3DOptix account is required, with OAuth 2.0 sign-in through the browser (dynamic client registration; no API key). New accounts get a trial; continued use needs a subscription. Network access to the 3DOptix cloud is needed for simulation.

Before you install

Requires a paid subscription after the trial, so continued use costs money. Sign-in is OAuth through a browser; no API key is pasted. Simulations, imports and uploads send your optical designs and files (including Zemax and CAD data) to the 3DOptix cloud platform. Setups you create or modify are written to your account.

Installation

In SourceWeft

Open 3DOptix in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.3doptix%2Foptical-design/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "3doptix": {
      "type": "http",
      "url": "https://mcp.3doptix.com/"
    }
  }
}

README

3DOptix for AI coding agents

Design, simulate and analyse optical systems from your coding agent, using the 3DOptix cloud platform.

This repository is a plugin — it bundles the 3DOptix MCP server together with a skill that teaches the agent how to use it well. Install it once and your agent can build optical setups, place lenses and detectors, run GPU ray-trace simulations and advanced optical analysis.

Skills here follow the Agent Skills open standard, so they work in Claude Code, Codex, Cursor and other compliant clients.

Install

Claude Code

Codex

Just the MCP server

If you only want the tools and not the workflow guidance, the server is listed in the MCP Registry as com.3doptix/optical-design, or add it directly:

Connect your account

You need a 3DOptix account. New sign-ups at 3doptix.com get a fully functional trial; continued use needs a subscription.

Authentication is OAuth 2.0 with dynamic client registration. There is no API key to paste.

Claude Code — run /mcp, select 3doptix, sign in via the browser.
Codex — run codex mcp login 3doptix.

Then confirm it worked by asking your agent to list your setups. Your agent can also walk you through this itself — the bundled 3doptix-setup skill activates on connection errors. Full troubleshooting: skills/3doptix-setup/SKILL.md.

What's included

Skill	What it covers
`3doptix-workflow`	Setup creation, component placement and alignment, light sources, detectors, catalog and custom optics, simulation, analysis, optimisation, Zemax import, CAD upload
`3doptix-setup`	Connecting and verifying the MCP server; activates on auth errors

The 3doptix MCP server provides tools for setups, parts, the optics and optomechanics catalogs, simulation, analysis and rendering. Tool reference: 3doptix.com.

Try it

Build a 2-lens beam expander for a 5 mm 632 nm beam, 3× magnification,then run a spot diagram on the output.

Build a 2-lens beam expander for a 5 mm 632 nm beam, 3× magnification,then run a spot diagram on the output.

Repository layout

.claude-plugin/     Claude Code plugin + marketplace manifests.codex-plugin/      Codex plugin manifest.agents/plugins/    Codex marketplace manifest.mcp.json           The 3DOptix remote MCP serverserver.json         MCP Registry entryskills/             Agent Skills — shared by every storeassets/             Store icons (the spectral sphere from the 3DOptix mark)scripts/            validate.js, set-version.js — plain Node, no dependencies

.claude-plugin/     Claude Code plugin + marketplace manifests.codex-plugin/      Codex plugin manifest.agents/plugins/    Codex marketplace manifest.mcp.json           The 3DOptix remote MCP serverserver.json         MCP Registry entryskills/             Agent Skills — shared by every storeassets/             Store icons (the spectral sphere from the 3DOptix mark)scripts/            validate.js, set-version.js — plain Node, no dependencies

Skill content lives in exactly one place. Each store gets a small manifest pointing at the same skills/ tree — nothing is duplicated per client.

There is no build step. Skills are Markdown and manifests are JSON, so what you see here is exactly what gets installed.

Contributing

Adding a skill

Create skills/<name>/SKILL.md with the required frontmatter:

name must match the directory name — every store enforces this. Put anything lazily loaded in skills/<name>/references/ and point at it from SKILL.md. Skills are discovered by directory, so there is no manifest to register a new one in.

Only skills under skills/ ship. A skill still in development belongs in an inactive-skills/ directory instead — no store scans it there, so it can live in the repository without reaching users.

Checks

No install step; it has no dependencies. It checks skill frontmatter against the Agent Skills spec, confirms all four manifests agree on a version, and refuses to pass if .mcp.json ever grows a credential. CI runs the same script on every push and pull request.

Before publishing a change, also confirm what a user will actually receive:

Releasing

.claude-plugin/plugin.json holds the authoritative version. To cut a release:

bash

node scripts/set-version.js 1.1.0   # writes all four manifestsnode scripts/validate.jsgit commit -am "release: 1.1.0" && git tag v1.1.0git push && git push --tags

node scripts/set-version.js 1.1.0   # writes all four manifestsnode scripts/validate.jsgit commit -am "release: 1.1.0" && git tag v1.1.0git push && git push --tags

Never edit a manifest's version by hand — validate.js will fail, which is the point.

Directories that list this plugin track commits on main and pick up changes automatically, so a push is a release whether or not you tag it. Tag anyway; it is how users pin a known-good version.

Support

Product and accounts — [email protected]
Bugs in these skills — open an issue on this repository
Privacy — privacy policy

Licence

MIT — see LICENSE.

Source: README.md at commit 2e0191f

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts