Plugin
Echo's plugin brings Echo to Claude and ChatGPT: the hosted MCP server and Echo's three skills, in one install. It's for the part of the work that happens in a chat. Make your style there, from a mood board, then build with it in your code tool.
The plugin, or the server alone
The server answers questions: which component does a job, what it takes, whether some code is right, which style fits. The skills know the workflow: when to read a board, what to ask you before writing a style, and when to hand the build to your code tool with the command that sets the project up.
| What you get | The MCP server | The plugin |
|---|---|---|
| Find and read components, check code, list, fit, check and wear styles | Yes | Yes, the same ten tools |
| Echo UI: knows whether it's in a project with Echo, one without, or a chat, and does what each needs | Yes | |
| Design Eye: reads a mood board into a style, and asks what the board can't settle first | Yes | |
| Style Fit: picks the style a product wears, from Echo's and yours, and says why | Yes |
In a project with a terminal you don't need either: init writes the same skills into the
project, and the CLI runs the check and the tests (For AI agents). In a project that
already has Echo, the plugin's Echo UI skill steps back and the project's own skill leads.
What it does in a chat
- Make a style. Share a mood board and ask for a style. Design Eye reads it as a designer
would, asks you what it can't settle, and hands back the style: a foundation document and a
style.jsonyou keep and reuse. - Pick one. Ask which style fits your product. Style Fit places the product on the seven axes, ranks Echo's styles and yours against it, and argues for one.
- Feel it. Wearing a style gives a link that makes this site wear its colours, every component pressing and moving in them.
- Hand it over. Code written in the chat is checked with
check_code, and ends with the commands for your code tool, in order:npx echo-ui-cli init --style <name>, thenaddfor each component it uses.
Install it
The plugin isn't in Claude's or ChatGPT's directories yet. Until it is, install it from here:
| Where | Download | Then |
|---|---|---|
| claude.ai | echo-ui-claude.zip | Customize, then Plugins, Add, and Upload plugin: choose the ZIP as it is. |
| Claude Code | echo-ui-claude.zip | Unzip it into a folder, then claude --plugin-dir <that folder>. |
| Codex and ChatGPT desktop | echo-ui-codex.zip | Unzip it, then codex plugin marketplace add ./echo-ui-codex and codex plugin add echo-ui@echo-ui-local. |
ChatGPT on the web takes the server without the skills: add https://mcp.echo-ui.com/mcp as a custom MCP
connector, and you get the tools.
What it sends
The plugin's tools are the hosted server. It receives what a tool is called with: a search, a component's name, a style's settings, or code to check. It needs no account and keeps nothing it's sent: code is checked and forgotten. A style of your own comes in with the call and is never stored. Everything else it reads is what this site publishes.