Echo UI is answering right now. Last checked 4 min ago. It exposes 10 tools. Last commit 7 Nov 2026.
A tactile React component library, and the design system that keeps your AI agent on-brand.
Uptime history
10 hours of history
10 hours agonow
100.0%
Uptime 24h
34 of 34 checks
10
Tools
read from the server
218 ms
Response time
average over 24h
0
Stars
last commit 7 Nov 2026
Nothing serious here today
Today is the operative word: we check Echo UI every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.
run in your terminal
claude mcp add mcp --transport http https://mcp.echo-ui.com/mcpSettings → Connectors → Add custom connector, then paste this address
https://mcp.echo-ui.com/mcp~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.echo-ui.com/mcp".cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.echo-ui.com/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "http",
"url": "https://mcp.echo-ui.com/mcp"
}
}
}Available tools 10
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
accessibility
get_accessibility
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.
code
check_code
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.
component
get_component
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.
components
search_components
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.
examples
get_examples
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.
fit
fit_styles
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.
style
check_style
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.
styles
list_styles
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.
tokens
get_tokens
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.
wear
wear_style
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.echo-ui.com/mcp | streamable-http | answering | 225 ms | 4 min ago |
Alternatives to Echo UI
same job, measured the same wayRoast My Design System
by pencilrebel
Audit your Design System and serve your Agent the rules that keep AI-written UI on-system.
Roast My Design System
by gregkozakiewicz
Audit your Design System and serve your Agent the rules that keep AI-written UI on-system.
Orvain UI
by orvain
Orvain UI design system for React and Vue: real component props, variants and tokens for AI tools
NuvUI
by nuvraxis
The docs, rules, blocks, charts and design tokens of nuvui, a React UI library, for coding agents.
Design System
by zaklad
Build and manage your design system with AI: tokens, themes, components, icons, Figma and code.
Mimic AI
by miapre
Builds Figma from your design system: real components and tokens, enforced, learning every build.
Nasaq UI
by fadymondy
Nasaq design system docs for agents: 390 components for React, Vue, Blade and HTML, with Arabic RTL.
noslopUI
by noslopui
Hand-crafted UI components and design systems for agents, so builds don't look like AI slop.
Echo UI — questions
Answers built from our own checks of this server.
What can Echo UI do?
It exposes 10 tools, read directly from the server on our last check. Among them: check_code, check_style, fit_styles, get_accessibility, get_component, get_examples and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Echo UI working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 34 of 34 checks got a reply (100.0%), average response time 218 ms. The bar chart above shows every period we have measured.
How do I connect Echo UI?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Echo UI need an API key?
No. Echo UI completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Echo UI?
It answers our handshake in 218 ms on average, which is faster than 63% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Echo UI open source?
The code is open source: it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at mcp.echo-ui.com, which runs on its operator's own terms.