Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Description from the maker (original English)
Optical design, simulation and analysis with GPU-powered ray tracing. Import from Zemax and CAD.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.3doptix.comRun this in your terminal
claude mcp add --transport http optical-design https://mcp.3doptix.comPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"optical-design": {
"url": "https://mcp.3doptix.com"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"optical-design": {
"type": "http",
"url": "https://mcp.3doptix.com"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.3doptix.comMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
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 6, 2026
The registry name was verified against the domain 3doptix.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 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 in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Figma Context MCP, Claude Real Video, Figma MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Let any LLM watch a video locally — and search everything it has ever watched.
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.
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.
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.
claude plugin marketplace add 3doptix/skills
claude plugin install 3doptix@3doptix
codex plugin marketplace add 3doptix/skills
codex plugin add 3doptix@3doptix
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:
claude mcp add --transport http 3doptix https://mcp.3doptix.com
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.
/mcp, select 3doptix, sign in via the browser.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.
| 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.
Build a 2-lens beam expander for a 5 mm 632 nm beam, 3× magnification,
then run a spot diagram on the output.
Import my Zemax file into 3DOptix and tell me where the aberrations are worst.
.claude-plugin/ Claude Code plugin + marketplace manifests
.codex-plugin/ Codex plugin manifest .agents/plugins/ Codex marketplace manifest .mcp.json The 3DOptix remote MCP server server.json MCP Registry entry skills/ Agent Skills — shared by every store assets/ 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.
Create skills/ /SKILL.md with the required frontmatter:
---
name: your-skill-name description: "When this skill should and should not trigger."
name must match the directory name — every store enforces this. Put anything lazily loaded in skills/ /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.
node scripts/validate.js
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:
claude plugin details 3doptix
.claude-plugin/plugin.json holds the authoritative version. To cut a release:
node scripts/set-version.js 1.1.0 # writes all four manifests
node scripts/validate.js git commit -am "release: 1.1.0" && git tag v1.1.0 git 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.
MIT — see LICENSE.