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)
A tactile React component library, and the design system that keeps your AI agent on-brand.
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 …”.
Funciona en Claude para web, escritorio y móvil:
https://mcp.echo-ui.com/mcpEjecuta esto en tu terminal
claude mcp add --transport http echo-ui https://mcp.echo-ui.com/mcpPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"echo-ui": {
"url": "https://mcp.echo-ui.com/mcp"
}
}
}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": {
"echo-ui": {
"type": "http",
"url": "https://mcp.echo-ui.com/mcp"
}
}
}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ú.
ChatGPT solo se conecta a servidores en internet:
https://mcp.echo-ui.com/mcpLos nombres de los menús pueden variar un poco según el plan y con el tiempo.
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.
Nombres y descripciones de las herramientas tal como los informó el servidor el 7 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.
search_componentsFind the Echo UI item for a job ("a settings toggle", "confirm a delete") or by name. Leads with the best fit, or says plainly that Echo has nothing for the job yet, then lists every match with its install command. The cheapest way to find out what exists, and the first call befo
get_componentThe full record for one component: description, install command, usage (imports + smallest working snippet), composition (part tree), examples, accessibility, motion & sound, prop table and anti-patterns. It's for before writing code that uses the component: the anti-patterns are
get_tokensThe token families: Layer-3 semantic colour roles (--echo-*), sound names, motion's whole vocabulary — the motion tokens, the spring presets, the morph feels and the CSS duration and ease steps — and the shadow recipes. Any name a component's record lists under Motion is here. Ec
get_examplesJust the usage examples for one component, without the rest of its record. For when the component is already chosen and only its calling convention is needed.
get_accessibilityThe accessibility rules a consumer of Echo can still get wrong — names on controls, form errors, announcements, focus and target size — and, with a name, what that component's accessibility was actually tested against. Echo guarantees WCAG 2.2 AA; this is the part the guarantee c
check_codeEcho's check on a piece of code you've written or are about to write: colours, spacing, radii, shadows and timing off Echo's scales, raw elements where Echo has the component, props a component doesn't take, controls without a name, markup a keyboard or screen reader can't use, r
list_stylesEcho's own styles, the looks Echo publishes, each with its one line and its fingerprint on the seven axes styles are placed on; or, with a name, one of them in full: its settings, rules, refusals, fonts, decisions and the slop police's word. The builder's own styles aren't here:
fit_stylesStyle Fit's shortlist: Echo's styles, and the builder's own passed in, measured against where a product sits on the seven axes (warmth, volume, density, formality, era, craft, ornament) and put in order: a style that misses a locked axis last, then least past tolerance first, the
check_styleWhether a style.json is one Echo can apply, as `npx echo-ui-cli style check` says it: what stops it, the device it makes (light or dark), what the theme corrects for AA contrast, what the slop police stops (with the question for the builder) or the builder kept, and the decisions
wear_styleWhat a style gives a project: a link that makes the whole Echo site wear its colours, the commands that put it in a project, and, for a project without a terminal, its theme CSS and a DESIGN.md with its rules. One of Echo's styles by name, or the builder's own style.json. A style
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 el dominio echo-ui.com (el registro comprueba quién es dueño del dominio)
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Respondió en 157 ms (HTTP 200)
No hace falta iniciar sesión
Leímos 10 descripciones de herramientas y no encontramos instrucciones ocultas para la IA
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ó 3 de 3 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 la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.
El repo de GitHub cambió por última vez –, y la última versión (0.3.5) llegó al registro hoy.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.
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.
An MCP server for Echo UI. It gives a coding agent ten tools over the Echo UI registry, so the agent can look up a component's props, usage, accessibility notes and anti-patterns before it writes code with it, check what it wrote, and find and wear a style.
Every client runs the same command:
{
"mcpServers": { "echo-ui": { "command": "npx", "args": ["-y", "echo-ui-mcp"] } } }
claude mcp add echo-ui -- npx -y echo-ui-mcp~/.codex/config.toml as [mcp_servers.echo-ui], with command = "npx" and args = ["-y", "echo-ui-mcp"]..cursor/mcp.json..vscode/mcp.json, under servers instead of mcpServers.Requires Node.js 20 or later.
For tools that only connect to a server on the web (ChatGPT, claude.ai, Lovable, v0, Bolt, Claude Design), the same tools run at https://mcp.echo-ui.com/mcp: nothing to install, no account. Add it as a custom connector (a remote MCP server) with that address, or:
claude mcp add --transport http echo-ui https://mcp.echo-ui.com/mcp{ "mcpServers": { "echo-ui": { "url": "https://mcp.echo-ui.com/mcp" } } }It reads the same published documents as the package, and keeps nothing it's sent: check_code reads your code and forgets it, and its request logs hold the path, the status and the timing, never a body. Cloudflare, which hosts it, keeps those logs, with the address a request came from, for up to 7 days (privacy policy). check_code takes up to 200,000 characters, a request past what that needs is refused with 413 before it's read, and one address can send 300 requests in ten seconds and about 2 MB of large code a minute, each whole 16 KB of a request counting (429 past either, with Retry-After).
Echo's plugin carries the hosted server and Echo's three skills (Echo UI, Design Eye and Style Fit) in one install: echo-ui.com/docs/plugin. In ChatGPT it's in the plugin directory. Until Claude's directory lists it too, it installs from the docs: the Claude ZIP for claude.ai and Claude Code, and the Codex ZIP for Codex and ChatGPT desktop.
| Tool | Takes | Answers with |
|---|---|---|
search_components | query? | The item for a job ("a settings toggle", "confirm a delete"), or a plain "Echo has nothing for this yet", then one line per matching component with its install command. The same answer as the CLI's which. With no query, every component. |
get_component | name | The full record: description, install command, usage, composition, examples, accessibility, motion & sound, props and anti-patterns. Accepts echo-hardware-button, hardware-button or HardwareButton. |
get_tokens | — | The colour roles (--echo-*), sound names and motion names. |
get_examples | name | Just the examples for one component. |
get_accessibility | name? | The rules a consumer of Echo can still get wrong. With a name, that component's own record of what was tested and what is not. |
check_code | code, file? | Echo's check on a piece of code: the same rules as npx echo-ui-cli check, against the default theme, each finding with the Echo way to fix it. For a tool with no terminal to run the CLI in. |
list_styles | name? | Echo's own styles, each with its one line and fingerprint; with a name, that style in full. |
fit_styles | profile, tolerance?, yours? | Echo's styles and the builder's own (by fingerprint), ranked against where the product sits on the seven axes. The same arithmetic as npx echo-ui-cli style fit. |
check_style | style | Whether a style.json is one Echo can apply, as npx echo-ui-cli style check says it. |
wear_style | name or style, files? | A link that makes the Echo site wear the style (one of Echo's whole, your own in its colours), the command that puts it in a project, and, for a project with no terminal, its theme CSS and DESIGN.md. |
When it connects, the server also sends instructions: how to set the project up, how to wire the theme and sound, and the corrections agents most often need (Base UI's package is @base-ui/react; Echo components are installed with npx echo-ui-cli add, not npm install).
get_component returns the same text as the component's page in the Echo UI docs and its entry in llms-full.txt, plus what the component ships as: its version, the echo-ui-core range it needs, and its accessibility record. That half is read from the same registry echo-ui-cli installs from, with the same client, so the two cannot disagree.
The server reads two published documents and re-reads them after five minutes: the catalog at https://echo-ui.com/r/catalog.json and the registry at https://echo-ui.com/e. To point it at a fork or a local build, set either:
{
"mcpServers": { "echo-ui": { "command": "npx", "args": ["-y", "echo-ui-mcp"], "env": { "ECHO_CATALOG": "/absolute/path/to/catalog.json", "ECHO_REGISTRY": "https://example.com/e" } } } }
If the registry cannot be reached the server still answers from the catalog, with the versions the catalog was built at. A copy it has already read keeps answering while its source can't be read, and is tried again every minute. If a file does not match the hash the registry published for it, the server says so rather than answering.
MIT