ctui vs UI Design to Code
ctui is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
ctui is a plugin bundle for AI coding tools published by Aliaksandr Katkou. No marketplace we read lists it any more. UI Design to Code is an MCP server published by Kinglions. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  UI Design to Code | |
|---|---|---|
| Community marketplace a1exk-dev/claude-tui | Removed on 2026-10-15 Version: 0.4.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.12 Downloads/month (npm): 370 Downloads/week (npm): 28 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | ctuino longer listed · | UI Design to Code |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (ui-design-to-code-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | MIT | MIT |
| Repository (differs) | github.com/a1exk-dev/claude-tui | github.com/kinglions/ui-design-to-code-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of ctui
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Real-time statusline HUD for Claude Code - context health, tool activity, agent tracking, and todo progress
-
Skins for Claude Code: tool rows with icons, diff, table and Mermaid chart cards, a usage band and fifteen themes. /skin swaps them live.
-
Customizable multi-line status line for Claude Code — real-time session telemetry in your terminal. Shows remaining context window, rate limit countdown, git status, session…
-
Status line plugin for Claude Code: live view of model, context, cost, and rate limits with customizable widgets and themes.
-
Tint a Terminal.app window by project and brighten it when a Claude Code response finishes unseen; tabs sharing a window get a tab-title marker instead. Includes a…
-
Display OpenAI Codex usage and rate limits inside Claude Code. Real-time statusline integration with claude-hud, slash commands for usage/costs/summary.
What each says it does
ctui
A skin for the Claude Code TUI: a docked sidebar with git, context, limits, todo, skills, MCP and agent sections, plus agent and shell toasts and a /ctui menu for plugins and themes.
UI Design to Code
Design-to-code artifact pipeline for UI screenshots, Figma node data, and visual review.
How to run each
ctui
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
UI Design to Code As a local MCP server: npm package
claude mcp add --transport stdio ui-design-to-code-mcp -- npx -y ui-design-to-code-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: ctui · What it can do: UI Design to Code · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.