Echo UI is an MCP server published by com.echo-ui, hosted at mcp.echo-ui.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 10 tools, including search_components, get_component, get_tokens, get_examples, get_accessibility.
A tactile React component library, and the design system that keeps your AI agent on-brand.
Nothing else in the archive shares these values.
Inferred from the host name and headers: what a server runs on, not who runs it.
Find 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 before writing Echo code.
| Parameter | Type | Description |
|---|---|---|
| query | string | A job in plain words, or a name. Omit to list everything. |
{
"name": "search_components",
"title": "Search Echo UI components",
"description": "Find 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 before writing Echo code.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"query": {
"type": "string",
"description": "A job in plain words, or a name. Omit to list everything."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
The 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 the part a model gets wrong from priors.
| Parameter | Type | Description |
|---|---|---|
| name * | string | Registry name ("echo-hardware-button"), bare name ("hardware-button") or title ("HardwareButton"). |
{
"name": "get_component",
"title": "Get an Echo UI component",
"description": "The 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 the part a model gets wrong from priors.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "Registry name (\"echo-hardware-button\"), bare name (\"hardware-button\") or title (\"HardwareButton\")."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}The 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. Echo components are styled and moved only through these: a hex, a duration or a shadow written by hand, or a token name that isn't here, is off Echo's system.
No parameters.
{
"name": "get_tokens",
"title": "Get Echo UI tokens",
"description": "The 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. Echo components are styled and moved only through these: a hex, a duration or a shadow written by hand, or a token name that isn't here, is off Echo's system.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}Just 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.
| Parameter | Type | Description |
|---|---|---|
| name * | string | Registry name, bare name or title. |
{
"name": "get_examples",
"title": "Get usage examples",
"description": "Just 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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "Registry name, bare name or title."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}The 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 cannot cover for you. It's for before building a form, a dialog or anything icon-only.
| Parameter | Type | Description |
|---|---|---|
| name | string | A component, for its own tested/untested record. Omit for the rules that apply everywhere. |
{
"name": "get_accessibility",
"title": "Get Echo UI accessibility rules",
"description": "The 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 cannot cover for you. It's for before building a form, a dialog or anything icon-only.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"name": {
"type": "string",
"description": "A component, for its own tested/untested record. Omit for the rules that apply everywhere."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}Echo'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, restyling Echo from outside, and the screen rules one file can show. The same rules as `npx echo-ui-cli check`, which runs on a whole project with its own theme; this one uses the default theme. Each finding says the Echo way to fix it.
| Parameter | Type | Description |
|---|---|---|
| code * | string | The file's contents: TSX, JSX or CSS, up to 200,000 characters. |
| file | string | Its file name, e.g. "app/settings/page.tsx" or "styles.css", which says what it is. TSX when left out. |
{
"name": "check_code",
"title": "Check code against Echo",
"description": "Echo'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, restyling Echo from outside, and the screen rules one file can show. The same rules as `npx echo-ui-cli check`, which runs on a whole project with its own theme; this one uses the default theme. Each finding says the Echo way to fix it.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"code"
],
"properties": {
"code": {
"type": "string",
"maxLength": 200000,
"description": "The file's contents: TSX, JSX or CSS, up to 200,000 characters."
},
"file": {
"type": "string",
"description": "Its file name, e.g. \"app/settings/page.tsx\" or \"styles.css\", which says what it is. TSX when left out."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}Echo'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: they're in their library or the conversation, and fit_styles weighs them with Echo's.
| Parameter | Type | Description |
|---|---|---|
| name | string | One of Echo's styles, e.g. "echo". Omit to list them all. |
{
"name": "list_styles",
"title": "List Echo UI styles",
"description": "Echo'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: they're in their library or the conversation, and fit_styles weighs them with Echo's.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"name": {
"type": "string",
"description": "One of Echo's styles, e.g. \"echo\". Omit to list them all."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}Style 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, then nearest. The same arithmetic as `npx echo-ui-cli style fit`. It orders; it doesn't pick.
| Parameter | Type | Description |
|---|---|---|
| yours | array | The builder's own styles, from their library or this conversation. |
| profile * | string | Where the product sits, 1 to 5 on each axis: "W4 V2 D1 F2 E3 C3 O3". |
| tolerance | string | How far a style may drift on each axis, 0 (locked) to 4: "W1 V1 D1 F0 E2 C1 O1". Left out, every axis may drift a point. |
{
"name": "fit_styles",
"title": "Rank styles for a product",
"description": "Style 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, then nearest. The same arithmetic as `npx echo-ui-cli style fit`. It orders; it doesn't pick.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"profile"
],
"properties": {
"yours": {
"type": "array",
"items": {
"type": "object",
"required": [
"name",
"fingerprint"
],
"properties": {
"name": {
"type": "string",
"description": "The style's name, as its folder is called."
},
"essence": {
"type": "string",
"description": "Its one line."
},
"fingerprint": {
"type": "string",
"description": "Its fingerprint, as its style.json or the library's INDEX.md gives it: \"W3 V2 D3 F3 E2 C4 O2\"."
}
}
},
"maxItems": 50,
"description": "The builder's own styles, from their library or this conversation."
},
"profile": {
"type": "string",
"description": "Where the product sits, 1 to 5 on each axis: \"W4 V2 D1 F2 E3 C3 O3\"."
},
"tolerance": {
"type": "string",
"description": "How far a style may drift on each axis, 0 (locked) to 4: \"W1 V1 D1 F0 E2 C1 O1\". Left out, every axis may drift a point."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}Whether 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 it leaves open.
| Parameter | Type | Description |
|---|---|---|
| style * | object | The style.json's contents, as a JSON object. |
{
"name": "check_style",
"title": "Check a style",
"description": "Whether 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 it leaves open.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"style"
],
"properties": {
"style": {
"type": "object",
"description": "The style.json's contents, as a JSON object.",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}What 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 the slop police stops isn't worn; the answer says what to ask the builder.
| Parameter | Type | Description |
|---|---|---|
| name | string | One of Echo's styles, e.g. "echo". |
| files | boolean | Include the theme CSS and DESIGN.md (the default). False when the builder will run the command in a project, which writes both itself. |
| style | object | The builder's own style.json, as a JSON object. |
{
"name": "wear_style",
"title": "Wear a style",
"description": "What 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 the slop police stops isn't worn; the answer says what to ask the builder.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"name": {
"type": "string",
"description": "One of Echo's styles, e.g. \"echo\"."
},
"files": {
"type": "boolean",
"description": "Include the theme CSS and DESIGN.md (the default). False when the builder will run the command in a project, which writes both itself."
},
"style": {
"type": "object",
"description": "The builder's own style.json, as a JSON object.",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}A neo-skeuomorphic React component library you install into your own source tree with `npx echo-ui-cli`. Molded caps in recessed wells, emissive readouts, real press travel. Motion (GSAP) and sound (zero-dep WebAudio synth) are first-class token families alongside color and type. Working rules: - The Base UI package is `@base-ui/react` (per-component imports, e.g. `@base-ui/react/dialog`), NOT `@base-ui-components/react` (the old name). Training data may be stale. - Set the project up once with `npx echo-ui-cli init`. It installs `echo-ui-core` (and `echo-ui-cli` as a dev dependency), writes `echo.json`, `echo-lock.json` and `echo-theme.css`, adds a marked Echo block to CLAUDE.md or AGENTS.md, a check hook to .claude/settings.json and three skills (building with Echo; Design Eye, which reads a moodboard into a style the project can wear; and Style Fit, which picks the style it wears), and prints the lines to paste. It never edits your source code, and `add` refuses to run before it. - Components render with no colour until the theme is on the page. `init` writes `echo-theme.css` into the Echo folder — import it once from your global CSS or your root layout (or call `createEchoTheme().css` from `echo-ui-core/theme` to build it at runtime). Give the page the device's ground (`body { background: var(--echo-well); color: var(--echo-text); font-family: var(--echo-font-sans); }`), dark or light as the chassis makes it, and wrap the app in `SoundProvider` from `echo-ui-core/sound` — without it every component is silent. It starts muted until the person turns sound on, and remembers their choice; `defaultMuted={false}` starts with sound. Put `<EchoCheck />` from `echo-ui-core/check` once in the root layout: in development it says in the console what's still missing, and in production it renders nothing. - Echo components are client components. In the Next.js App Router, a file that passes them a function (`onSave`, `onSubmit`, `onClick`) must start with `"use client"`. - Echo is a REGISTRY, not an npm component package. Components are installed with `npx echo-ui-cli add <component>` and then live in the consumer's own source tree, importing each other by relative path inside one Echo folder. Never suggest `npm install` for a component. The one npm package is `echo-ui-core`, the grammar they all import (theme, sound, motion, tactile, presence). - Installed files still receive Echo's later fixes. `npx echo-ui-cli diff` reports every installed item as up to date, behind, edited, or edited and behind; `npx echo-ui-cli update` brings them forward and merges Echo's change into files somebody edited; where an edit and Echo's change meet in the same lines, it leaves that item and prints the lines between git's conflict markers, to bring together before running it again. Never tell a user to re-run `add --overwrite` to upgrade — that discards their edits without showing them what it is discarding. - Style only through the Layer-3 semantic vars (`var(--echo-*)`) from `createEchoTheme`. Never hardcode a hex, and never invent a token name — call get_tokens for the real list. - Read a component's anti-patterns before using it. They exist because the obvious thing is wrong for this material system (a screen readout does not ease smoothly; severity is not red/amber/green). Accessibility is part of the grammar, not a review step. Echo guarantees WCAG 2.2 AA, and these are the parts a consumer can still get wrong: - Every control needs a name. `Switch`, `Checkbox`, `Slider`, `Segmented`, `Select`, `RadioGroup` and `Progress` take `aria-label` (or `aria-labelledby` pointing at visible text); `Field`, `Textarea` and `OtpField` take a visible `label`. Without one they do not compile. - An icon-only `HardwareButton` (`iconOnly`) needs `aria-label`: it has no text to read. - Forms: put the help text in `description` and the problem in `error`, both on the field. They are linked to the input and set `aria-invalid` for you. Never signal an error with colou
Names, descriptions and schemas were written by the server and are shown as data.