What is the Liquefy UI MCP server?
Liquefy UI MCP is the server side of Liquefy UI, a React component library built on WebGL optics and physical springs. It runs through npx, and gives an agent 8 tools to list and search 36 components, pull a component's real source and tokens, and list the icon set, all answered locally with no network dependency.
Liquefy UI is a React component library built around a liquid glass look: WebGL edge refraction, physical spring motion, and accessible primitives underneath. The MCP server is the piece that lets an agent query that library directly instead of guessing at component names or props.
All 8 tools answer from the real package data with no network call, so an agent gets accurate results even without internet access, as long as the package itself is installed.
What you can ask it to do
- List or search the 36 components across inputs, data display, feedback, surfaces and navigation, and get back the exact ones that match a query.
- Pull a component's real source code before writing a usage example, instead of inventing props that do not exist.
- Read design tokens and conventions, such as naming and composition rules, before generating new code in the same style.
- List the 53 tree-shakeable icons that ship alongside the component set.
What makes the look distinct
Transform and backdrop-filter styling is written inline by the jelly spring physics every frame, so it cannot be overridden through ordinary CSS. Systems without WebGL fall back to plain CSS materials automatically.
Who it is for
Best for
- Next.js or React projects, including the App Router and Server Components, that want a distinct glass look instead of a flat default theme.
- Agents that keep inventing props or component names for a UI library instead of checking the real source first.
- Teams already using Tailwind CSS v4 who want a component set that integrates with it directly.
Not for
- If the React components you want come from a larger 160-plus animated source-code library rather than the glass-specific set, Lightswind UI MCP Server can search and read those React components instead.
- When the components need to map to an exact shadcn install command rather than a glass-specific package, ns-ui MCP Server can search those React components and return that exact command instead.
- If the framework is Astro rather than plain React, Starwind UI MCP Server gives Astro and React components guidance for that setup instead.
- When what you need is tokens and themes from a CSS-only component library rather than a React package, Veritheme MCP Server queries those components and tokens directly.
Use it with UiChemy
Liquefy UI builds React components for your own app. UiChemy Composer works on the WordPress side, so a similar glass-style look can go into an editable Elementor or Gutenberg page instead. Click Get Started on uichemy.com.
Connect Liquefy UI MCP: Query a Liquid Glass Component Library to your AI client
claude mcp add liquefy-ui -- npx -y @liquefy-ui/mcpAdd the MCP server in Claude Code
Run
claude mcp add liquefy-ui -- npx -y @liquefy-ui/mcp. This is the README's own command for Claude Code.Or add the config by hand
Put the config block above in any other MCP client's settings so it starts the same npx command over stdio.
Install the component package
Run
pnpm add @liquefy-ui/react @liquefy-ui/core @liquefy-ui/iconsin your React project to get the components the server describes.Ask for a component by task
Request a component by what it should do, such as a date picker or a toast, and let the agent search and pull the real source before writing usage code.
Client configuration
{
"mcpServers": {
"liquefy-ui": {
"command": "npx",
"args": ["-y", "@liquefy-ui/mcp"]
}
}
}Endpoints and ports
npx -y @liquefy-ui/mcpStarts the component query server over stdio.pnpm add @liquefy-ui/react @liquefy-ui/core @liquefy-ui/iconsInstalls the actual components, core logic and icon set.What you can do with it
- 8 local query toolsEvery tool answers from the installed package's own data, with no network dependency, so results stay accurate offline.
- 36 components, five categoriesInputs, data display, feedback, surfaces and navigation cover most common UI needs from one consistent set.
- Real source, not a guessget_component_source returns the actual component code, so generated usage examples match real props instead of invented ones.
- Token and convention accessget_tokens and get_conventions expose the design values and naming rules a new component should follow to match the rest.
- WebGL with a CSS fallbackThe liquid glass look runs on WebGL edge refraction and physical springs, with an automatic CSS fallback where WebGL is unavailable.
- Modern React supportWorks with Next.js 16 and the App Router, including React Server Components, and integrates with Tailwind CSS v4.
Tools it exposes
get_conventions
Returns the library's naming and composition conventions before an agent writes new code in the same style.
list_components
Lists the 36 components across inputs, data display, feedback, surfaces and navigation.
get_component
Returns the details for one named component.
search_components
Searches components by a task or keyword instead of requiring the exact component name.
get_component_source
Returns a component's real source code so an agent writes against its actual props.
get_tokens
Returns the design tokens the components are built from.
list_icons
Lists the 53 tree-shakeable icons that ship with the library.
get_core_api
Returns the shared core API that components and the icon set are both built on.
Frequently asked questions
What is the Liquefy UI MCP server?
It is the query layer for Liquefy UI, a liquid glass React component library, letting an AI coding agent list, search and read the real source and tokens of its 36 components instead of guessing at props or names.
How do I install the Liquefy UI MCP server?
Run claude mcp add liquefy-ui -- npx -y @liquefy-ui/mcp in Claude Code, or add a server entry with command npx and args -y and @liquefy-ui/mcp to any other MCP client's config.
Do I still need to install the React components separately?
Yes. The MCP server only answers queries about the library; run pnpm add @liquefy-ui/react @liquefy-ui/core @liquefy-ui/icons in your project to get the actual components, core logic and icon set it describes.
Does the MCP server need an internet connection?
No. All 8 tools read from the installed package's own data, so results stay accurate without any outbound network call, as long as the package itself is present on your machine.
Can I override the glass motion styling with CSS?
No. The transform and backdrop-filter properties are written inline by the jelly spring physics on every single frame, so ordinary CSS overrides on those two properties do not take effect at all.
What happens on a system without WebGL?
The components fall back to plain CSS materials automatically, so the library still renders fine on that machine, just without the WebGL-driven edge refraction effect on those particular systems or browsers.
Does Liquefy UI MCP work with agents other than Claude?
The README documents the install command specifically for Claude Code, but the server itself starts over standard stdio through npx, so any MCP-capable client can point at the same @liquefy-ui/mcp command.


