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)
Cross-media conversion engine: 2D art, 3D models and engine formats, deterministic over MCP.
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.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
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.
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.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
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.
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 6, 2026
The registry name was verified against the domain qompass.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
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
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 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 –, and the latest version (1.0.0) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
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.
Lux in motu — light in motion. A cross-platform, cross-media conversion engine, written in Rust (edition 2024, rmcp 3.8.0): one operation core that bridges media formats — 2D art and sprite formats, 3D models, and game-engine packages — converting between them deterministically from code-first records, so the same input record yields the same output on any platform. Aseprite sprites and Bevy were its first endpoints, not its purpose; the center is the factory (one identity record, emitted as 2D or 3D) and the named, verified converter chain between formats — one operation core behind three surfaces —
lumen-policy.toml before it executes, decisions are replayable, and denials name the rule they violated. See POLICY_DESIGN.md.Companion strategy — pair, don't duplicate — is in COMPANIONS.md. How lumen was built, in what order, and under what governance (including the evidence rule its first failed build produced) is in HISTORY.md.
Character generation and derivation run against a single canon record per character (canon-record/1), enforced by four tools (15 registered total at 1.0.0; the 11 pre-B2 tools are unchanged):
canon_resolve — handle (canon:// / @ canon/ / .json); lumen never persists an adult record.canon_gate — measurements → verdict over proportion and register bands (ink colour, stroke weight, shadow-edge hardness, saturation/contrast percentiles, key-light direction, iris spec, blush). Drift returns a typed drift_detected refusal with per-metric deltas. PASS releases an artifact to the eye sheet, never to adoption.canon_generate — anchored generation broker. There is no unanchored mode: a job requires a canon handle, an anchor role, the keeper anchor + style-authority hashes among its inputs, and turnaround + plate reference inputs (reference conditioning). Jobs anchored outside the Owner-adopted keeper set are refused pre-generation. Every job persists a workflow-JSON provenance receipt (canon-receipts/ .json, digest-verified; tampering is detectable), and any supplied outputs are gated before the job returns as admitted.canon_convert — handled conversion (1.0.0, R-607): a project PNG is remapped under the record's fingerprint palette (nearest palette colour within its tolerance; out-of-tolerance pixels keep their colour and are counted) and the result is gated against the record's bands before anything is written — drift writes nothing. There is no unhandled mode on this tool; the pre-canon conversion tools keep their existing behaviour without a handle (SPEC §6).The format/handle/gate crate is crates/lumen-canon (package lumen-canon, lib canon_record), absorbed from the B1 reference implementation without re-derivation.
Also at 1.0.0: the Phase F motion evaluator leg is verified landed in crates/lumen-rig-core (MOTION-EVALUATOR.md), and the sprite→3D fidelity metric (silhouette IoU + landmark Δ) ships in crates/lumen-factory with its first measurement on record (crates/lumen-factory/FIDELITY.md). The server package is lumen-mcp-server 1.0.0 (D-298 rename; the library crate remains lumen). EFLO for the 15-tool surface: EFLO.md. Utilization evidence: UTILIZATION.md.
-D warnings clean (resolved clippy 0.1.100, nightly-2026-09-25 pin) on sandbox and primo; Diver gate at the primo mirror. (Suite split between validation and adversarial cases.)scripts/interop_check.sh): 5 passed / 3 failed — the failures are documented premise mismatches between lumen's assumptions and the real tools' behavior; see HISTORY.md.src/ — operation core: sprite_ops, inspect, palette, text, style, dream, qa, export, pipeline, policy, bevy, doc, vrm, and the a2a/ surface (mod, task, http, registry).tests/ — validation and adversarial suites, incl. interop.rs (live-tool gates, ignored by default).lumen-policy.toml — the shipped policy; lumen policy check and lumen policy replay are its gates.This project is licensed under the Apache License, Version 2.0.