mcpbeat Sign in

Mlola UI MCP Server

by mlolahq Your server? Claim it
answering

Mlola UI is answering right now. Last checked 2 min ago. 2 481 installs a week from npm. It exposes 9 tools. Last commit 9 Oct 2026.

Mlola UI components, tokens and design rules for coding agents, with a markup checker

Installs per day peak 1 967 · avg 331 · +74% w/w
a month agotoday
Uptime history 15 days of history · worst day 98%
15 days agonow
100.0%
Uptime 24h
92 of 92 checks
9
Tools
read from the server
421 ms
Response time
average over 24h
2 481
Installs / week
npm and PyPI

What changed 50

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 28 September 2026. No other catalogue keeps this.

11 Oct a tool changed version
9 Oct a tool changed version4 times that day
9 Oct 3 tools appeared check_render, get_render_catalog, render_ui
7 Oct a tool changed version4 times that day
5 Oct a tool changed version
4 Oct a tool changed version2 times that day
3 Oct a tool changed version3 times that day
2 Oct a tool changed version2 times that day
1 Oct a tool changed version4 times that day
30 Sep a tool changed version5 times that day
and 38 more, back to 28 September 2026

What the code does

We read the source, 1 h ago · tools taken from the live server · rules ccca72095570

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Builds a file path from a variable packages/cli/src/assets.js:67, packages/cli/src/knowledge.js:17, packages/cli/src/pro.js:131 и ещё 7 
    const filename = path.join(cwd, relative);
Runs an external command packages/cli/src/cli.js:156, [пакет] src/cli.js:156 
        spawnSync(name, installArgs, { cwd: directory, stdio: options.installStdio ?? "inherit", shell: process.platform === "win32" })),
Page executes code built at runtime packages/cli/registry/render-app.html:8475, [пакет] registry/render-app.html:8475 
…r));for(let o of n.flat())o!=null&&o!==!1&&i.append(o);return i}function ke(e,t){let n=document.createElement("span");n.innerHTML=lt[e];let i=n.firstElementChild;return t&&i.classList.add(t),i}function dt(e,t={}){let n=t.host??at(t.rules,{onAction:t.onAction,onError:t.onError}),i…

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add mlola-ui --transport http https://ui.mlola.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mlola-ui": {
      "url": "https://ui.mlola.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mlola-ui]
url = "https://ui.mlola.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mlola-ui": {
      "url": "https://ui.mlola.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mlola-ui": {
      "url": "https://ui.mlola.com/mcp"
    }
  }
}

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

render
check_render
Checks A2UI messages (createSurface, updateComponents, updateDataModel, deleteSurface) against the Mlola Render catalog before they render: components and props that do not exist, values a component does not offer, colors or styles set by hand, fields and controls without a name, a missing root, children that do not exist or form a loop, headings that skip a level, values outside a range. Each error names its JSON Pointer path and the fix. Pass every message of the surface: one object, an array, or JSON Lines.
get_render_catalog
The components an agent may compose at runtime with Mlola Render, as A2UI v0.9 messages: each component's props and allowed values, how surfaces, data binding and actions work, and complete examples. Read once before composing a surface. format "schema" returns the A2UI catalog (JSON Schema) instead.
render_ui
Shows an interface in the conversation: a form, a status card, a table of results. Pass A2UI messages composed from the Mlola Render catalog (read get_render_catalog first); they are checked, and drawn with Mlola components where the host shows MCP Apps. When the person presses a button, their next message carries the A2UI action with what they entered. Where the host shows no apps, this answers with the check's report.
component
get_component
Everything needed to use one item: import, every prop with fixed values (variant, tone, size, side…) and its default, the classes it styles and the data-* values each reacts to, dependencies and the install command. Set include_source to read a free component's source.
components
search_components
Find components, blocks, pages and templates by what they do (for example 'date range', 'chat input', 'pricing'). Returns name, tier (free or Mlola Pro) and a one-line description.
design
get_design_rules
The rules for building UI with Mlola: compose first, color by role, measure with the scales, shared state words, touch and focus. Read once before writing UI.
install
get_install_command
How to set Mlola up: the commands to run in a project to add components, blocks, pages or templates (with the license step for Mlola Pro items), and the stylesheet link and script for a page with no build step. Leave names out for the setup alone.
markup
check_markup
Checks HTML or JSX: classes that do not exist, variant classes, data-* values a class does not react to, utility classes, misuse of data-theme or data-mode, and in style attributes, <style> blocks and utility classes (bg-[#fafafa]) hand-written colors, spacing written by hand instead of the --ml-space-* scale, overridden theme tokens and text faded with opacity. Each issue names its line. Run it on markup you wrote before finishing: pass the whole page or file, <style> blocks included, not an excerpt, since it only checks what it is given.
tokens
get_tokens
The --ml-* tokens grouped by purpose (planes and ink, color roles, spacing, type, density, shape, depth, motion, layers…). Filter with a group name or part of a token name.

Endpoints

URLTransportStateLatencyChecked
https://ui.mlola.com/mcp streamable-http answering 110 ms 2 min ago

Alternatives to Mlola UI

same job, measured the same way
WunderUI
by kl-webmedia

The WunderUI design system for coding agents: components, props, tokens, rules and skills.

898 installs/wk local only
Buoy
by ahoybuoy

Design tokens and drift checks for coding agents: use the token, not the hardcoded value.

284 installs/wk local only
tesserai
by tesserai

Your project's design system for coding agents: tokens, components, contrast checks, guidelines.

724 installs/wk local only
Visily UI Design
by visily-app

UI design from prompts, screenshots, and URLs for AI coding agents and theme tokens.

answering
Design System
by zaklad

Build and manage your design system with AI: tokens, themes, components, icons, Figma and code.

answering
Mozaic
by merzoukemansouri

Mozaic Design System (ADEO): tokens, components, icons, docs and style guides for any agent.

150 installs/wk local only
onsystem
by dgesteves

Keeps coding agents on your design system: knows your real components, props, variants and tokens.

local only
useVyre Context
by gapra

useVyre component context for AI agents — valid props, variants, anti-patterns, and design tokens.

48 installs/wk local only

Mlola UI — questions

Answers built from our own checks of this server.

What can Mlola UI do?
It exposes 9 tools, read directly from the server on our last check. Among them: check_markup, check_render, get_component, get_design_rules, get_install_command, get_render_catalog and 3 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 Mlola UI working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 421 ms. The bar chart above shows every period we have measured.
How do I connect Mlola UI?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Mlola UI need an API key?
No. Mlola UI completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Mlola UI?
It answers our handshake in 421 ms on average, which is faster than 33% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Mlola UI?
The npm package mlola-ui was installed 2 481 times in the last week. Week over week that is +74%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Mlola UI open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.