Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Descripción del creador (original en inglés)
High-entropy alloy and oxide descriptors, phase rules, corpus, properties, and design tools.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"hea-bench": {
"command": "uvx",
"args": [
"hea-bench"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add hea-bench -- uvx hea-benchPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"hea-bench": {
"command": "uvx",
"args": [
"hea-bench"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"hea-bench": {
"type": "stdio",
"command": "uvx",
"args": [
"hea-bench"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub dfieser, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (2.9.0) llegó al registro hace 29 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Python (uv) en tu computadora.
En la misma categoría: Figma Context MCP, Claude Real Video, Figma MCP Server
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
The Figma MCP server brings Figma design context directly into your AI workflow.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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
Solo se muestra el principio; lee el resto en el repo