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)
High-entropy alloy and oxide descriptors, phase rules, corpus, properties, and design tools.
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 …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"hea-bench": {
"command": "uvx",
"args": [
"hea-bench"
]
}
}
}Run this in your terminal
claude mcp add hea-bench -- uvx hea-benchPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"hea-bench": {
"command": "uvx",
"args": [
"hea-bench"
]
}
}
}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": {
"hea-bench": {
"type": "stdio",
"command": "uvx",
"args": [
"hea-bench"
]
}
}
}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 7, 2026
The registry name was verified with the GitHub account dfieser, which owns the repo
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 (2.9.0) reached the registry 29 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: 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.
Open, interpretable tools for computing the standard high-entropy-alloy (HEA) and high-entropy-oxide (HEO) thermodynamic and geometric descriptors and the classic empirical phase-prediction rules, from any composition. Every descriptor is a transparent closed-form expression over a curated element-property table, validated against the primary literature. The fitted predictions (hardness, phase prediction sets) carry calibrated uncertainty and flag alloys unlike their training data.
Try it now: https://dfieser.github.io/hea-bench/. No install, it runs entirely in your browser, and every library feature works there: the calculator for alloys, oxides and ceramics with property and phase predictions, the experimental dataset, alloy search and experiment planning, and the benchmark.
The equimolar Cantor alloy CoCrFeMnNi, as the browser app reports it. The Python library, the desktop app and this page print the same digits, and a parity suite keeps it that way.
Using an AI coding agent to integrate this? See
AGENTS.md for a machine-oriented guide to the API,
exact return types and units, the fastest path to each task, and the
mistakes to avoid.
For any composition it reports:
hea_bench.oxides + the apps' Oxides mode): rock-salt, perovskite, fluorite, and pyrochlore formability descriptors over Shannon ionic radii with automatic charge-balance oxidation-state assignment: per-sublattice configurational entropy, cation size disorder, Goldschmidt t / octahedral μ / Bartel τ, the fluorite radius-dispersion rule, and the pyrochlore radius-ratio window.Element coverage: 55 elements for alloys (Ag Al Au Be Bi Ca Ce Co Cr Cu Dy Er Fe Ga Gd Ge Hf Ho In Ir La Li Lu Mg Mn Mo Nb Nd Ni Os Pb Pd Pr Pt Re Rh Ru Sb Sc Si Sm Sn Sr Ta Tb Th Ti Tm U V W Y Yb Zn Zr, covering the full experimentally active rare-earth HEA palette plus the nuclear, solder, and HE-BMG corners); the Miedema pair table covers 75 (1484 of our 1485 pairs; the lone Th-U gap is reported, never zeroed); the oxide module's Shannon table covers 94.
No fitted model sits anywhere in this chain. Each descriptor is a closed-form expression over curated tables, and the report carries the literature source of every input alongside the value.
flowchart LR
A["Composition CoCrFeMnNi"] --> B["Curated element tables 55 elements, 1484 Miedema pairs"] B --> C["Closed-form descriptors ΔS, δ, VEC, ΔH, Ω, Φ, φ, Λ, γ, κ"] C --> D["Empirical phase rules Yeh, Zhang, Guo-Liu, Yang-Zhang, King, Ye"] C --> E["Report per-value provenance, content-hashed result ID"] D --> E
| Part | Where | Best for |
|---|---|---|
| Web app | https://dfieser.github.io/hea-bench/ | anyone, no install |
| Desktop app | one portable .exe, download (no install), the same app in its own window, engine inside, works offline | Windows users who want it local |
| Python library + CLI | pip install "hea-bench[all]" | scripts and notebooks |
| MCP server for AI agents | pip install "hea-bench[mcp]", then hea-bench-mcp | Claude, Cursor and other MCP clients, as 24 tools |
Every feature is in all four parts, so pick whichever suits you and you lose nothing. That is a standing project rule, and CI enforces it: tests/test_feature_parity.py fails whenever a public feature lacks its library function, its MCP tool or a working app surface, a headless browser uses every tab of the built site, the built desktop exe goes through the same steps before it is attached to a release, and a freshly installed wheel answers every MCP tool. pip install hea-bench alone has no dependencies and covers everything except the fitted models and the MCP server; the [all] extra adds scikit-learn and the MCP SDK for those.
All four share one calculation core. The browser/desktop core (web/hea-calculator-core.js) is a pure-JS port of the Python library, and tests/test_web_parity.py guarantees the two match on all 1484 binary pairs and the canonical multi-element fixtures, while tests/test_web_oxides_parity.py does the same for the oxide module, down to identical warning messages. The app's Dataset, Design and Benchmark tabs and its predictions panel run the Python package itself, unchanged, inside the page (Pyodide, web/hea-engine-worker.js), and tests/test_web_engine.py checks that it returns exactly what CPython returns.
pip install hea-bench
import hea_bench as hb
cantor = {"Co": 0.2, "Cr": 0.2, "Fe": 0.2, "Mn": 0.2, "Ni": 0.2}
hb.smix(cantor) # 13.381 J/(mol·K) = R · ln 5 hb.delta(cantor) # 3.164 % atomic-size mismatch hb.vec(cantor) # 8.0 valence electrons hb.mixing_enthalpy(cantor) # -4.16 kJ/mol (Miedema) hb.omega(cantor) # 5.79 (Yang–Zhang) hb.delta_chi(cantor) # 0.138 Pauling electronegativity mismatch hb.s_excess(cantor) # 0.318 J/(mol·K) (Mansoori excess entropy) hb.delta_g_max(cantor) # -8.00 kJ/mol (most-negative Miedema pair) hb.phi_king(cantor) # 3.533 (King 2016 proxy) hb.phi_ye(cantor) # 34.82 (Ye 2015 proxy)
from hea_bench.rules import guo_vec, king_phi, yang_omega, ye_phi, zhang_delta zhang_delta.predict(cantor) # 'single-phase' yang_omega.predict(cantor) # 'single-phase' guo_vec.predict(cantor) # 'FCC' king_phi.predict(cantor) # 'solid_solution' ye_phi.predict(cantor) # 'solid_solution'
These Cantor-alloy values are pinned in the test suite as the canonical sanity check. The rules are simple empirical surrogates, fast screens rather than predictions, so treat their output accordingly.
Descriptors can also be computed through a pluggable backend. The default (native) is this package's own stdlib implementation; with pip install "hea-bench[interop]" the same interface drives an installed HEACalculator (GPLv3, installed at the user's choice), so a workflow standardized on its numbers can keep them while using everything downstream here:
from hea_bench.descriptors.backend import get_backend
get_backend("heacalculator").compute(cantor) # same names, their reference data
hea-bench describe Al0.3CoCrFeNi --backend native
The two backends vendor different reference data (radius conventions differ most), so same-named values legitimately differ; the measured, per-descriptor comparison lives in docs/backend-agreement.md. Quantities whose implementations differ structurally are deliberately not mapped onto each other, and the benchmark's published baselines use the native backend unchanged.
from hea_bench import oxides
j14 = oxides.describe_rock_salt({"Mg": 1, "Co": 1, "Ni": 1, "Cu": 1, "Zn": 1}) j14"descriptors" # 13.382 J/(mol·K) = R·ln 5 j14["oxidation_states"] # all 2+ by charge balance
pvk = oxides.describe_perovskite({"Sr": 1}, {"Zr": 1, "Sn": 1, "Ti": 1, "Hf": 1, "Mn": 1}) pvk"descriptors" # 0.979, inside the 0.92–1.04 window pvk"verdicts" # 'perovskite' (τ = 3.72 < 4.18)
Each describe_* report carries the solved oxidation states, the Shannon radii actually used, every descriptor, the formability verdicts with their windows, and any warnings. See examples/02_oxides_walkthrough.py for the full tour, including the fluorite and pyrochlore screens and oxidation-state overrides.
hea_bench.ceramics extends the calculator to rock-salt carbides and nitrides and AlB2-type diborides, composition-only and honest about what that buys:
from hea_bench import ceramics
hec = ceramics.describe_rock_salt_carbide({"Ti": 1, "Zr": 1, "Hf": 1, "Nb": 1, "Ta": 1}) hec["vec_per_formula_unit"] # 8.4, with annotated literature reference points hec["entropy"] # all normalization conventions, labelled
Reports carry the metal-sublattice entropy in every published normalization convention (papers switch between them without warning), VEC with annotated reference points rather than a verdict (the literature marks points, not one window), and explicit notes on what is deferred: the size-mismatch descriptor (the field computes it from DFT binary-cell bond lengths, and adopting a cited table is real curation work), and entropy-forming-ability or DEED, which are DFT-ensemble quantities this package cannot and does not claim to reproduce. Background, citations, and a license audit of candidate ceramics datasets: docs/ceramics.md.
LLM agents hallucinate descriptor values; this server grounds them. hea_bench.mcp_server exposes every feature of the package over the Model Context Protocol as 24 deterministic tools. The calculator: parse_composition, batch alloy_descriptors (with the Miedema enthalpies) and alloy_rules, both taking custom elements and pair values, omega_sensitivity, oxide_report, ceramic_report, element_data and `element_cove
Only the beginning is shown; read the rest in the repo