OptiGuide for Claude Desktop - BETA
Setup Guide for setting up 3doptix MCP with Claude Desktop
Welcome to OptiGuide in Claude Desktop
OptiGuide connects Claude to your 3DOptix workspace via MCP, so you can ask Claude to create, open, and modify optical simulation setups, manage components (sources, optics, detectors), run simulations, and review results, using the same capabilities available through the 3DOptix API.
What is MCP, and what does OptiGuide enable?
MCP (Model Context Protocol) is an open protocol that enables an AI app to securely connect to external tools and data sources via an MCP server.
OptiGuide is 3Doptix’s MCP integration. With OptiGuide enabled, Claude can use the same capabilities exposed by the 3Doptix API / SDK, such as:
Working with simulation setups (create, list, open).
Adding and editing components such as optics, detectors, and light sources.
Changing positions/poses, running simulations (e.g., ray tracing), and reviewing results.
Why Claude Desktop (not the web app)?
Claude Desktop is the installed application that supports configuring MCP servers locally; this differs from using Claude in a browser, as the Desktop app is where OptiGuide/MCP is configured and managed.
1) Install prerequisites
1.1 Install Claude Desktop
Use the official Claude Desktop installer for macOS or Windows.
1.2 Install Node.js (highly recommended)
OptiGuide is launched through npx (Node’s package runner). Installing Node.js also installs npm/npx in standard setups. While Claude Desktop ships with an embedded version of Node, we noticed that it is often not enough for running OptiGuide.
3) Configure OptiGuide in Claude Desktop
- Open Claude Desktop → Settings
- Go to Developer
- Click Edit Config and open
claude_desktop_config.json - Paste the configuration below.
- Replace
YOUR_API_KEY_HEREwith your real 3doptix API key - Quit and reopen Claude Desktop (Claude Desktop loads MCP
servers at startup, so you need to quit Claude Desktop from tray icon, not
just close the window)
claude_desktop_config.json must contain a single top-level JSON object. If your file already has content (e.g., "preferences"), merge the "mcpServers" block into the existing { ... } instead of pasting this as a second separate { ... } block (two root objects will cause a config error).
{
"mcpServers": {
"OptiGuide": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.3doptix.com/?api-key=YOUR_API_KEY_HERE"
]
}
}
}
4) Post-configuration: Tool permissions (recommended)
After restart, go to Settings → Connectors, open OptiGuide, and set tool permissions.
You can choose:
- Always allow (smoothest experience; fewer prompts), or
- Ask / allow one-by-one during use (more control; more prompts)
Both are valid—pick what fits your internal policy and comfort level.
5) Notes
Keep one source of truth + use preview widgets
To avoid unexpected behavior, don’t edit the same OptiGuide setup in multiple places at the same time
(for example, don’t open it on 3doptix website while changing it with the AI agent).
Pick one place to manage the configuration and keep it consistent.
For previews, OptiGuide can generate a widget/preview link. Open that link in your browser to reviewthe
results.
Use OptiGuide with other AI agents
OptiGuide is powered by our MCP server and can also be connected to other AI agents that support MCP.
If you’d like to integrate OptiGuide with another tool or workflow, contact us, and we’ll do our best to help.
Need help?
If you run into any issues during setup or use, contact us, and we’ll be happy to help.