liquefy-ui

io.github.liquefy-uiPublished by GitHub account liquefy-uiv0.1.5Updated Oct 30, 2026

Answers questions about liquefy-ui from its real API surface, so an agent stops inventing props.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Local MCP server that gives coding assistants the real API of the liquefy-ui Liquid Glass React component library, so they stop inventing props.

What you can do
  • List and search components, hooks and internal modules, with one-line descriptions
  • Read a component's exported names, verbatim type declarations, import line and docs URLs
  • Fetch copy-paste component source with imports rewritten to shadcn aliases
  • Read design tokens and their values per theme scope
  • List icons from the icons package with their props
  • Read the core engine API and the library conventions that are easy to get wrong
When to use it
Useful when an assistant writes or reviews code with liquefy-ui and needs accurate prop names, types, tokens or conventions instead of guesses. Also handy when deciding whether the library has a component for a given need.
Requirements
Runs as a local stdio process, typically launched with npx from the npm package. Needs Node.js and npx on the machine. No authentication, environment variables or headers are declared, and the server does not use the network at runtime.
Before you install
Read-only lookup server: it exposes library API details and source snippets, not actions on your project. The catalog is generated from the library source at build time, so it reflects the published package version rather than your local edits.

Installation

In SourceWeft

  1. Open liquefy-ui in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@liquefy-ui/mcp

A Model Context Protocol server that answers questions about liquefy-ui from its real API surface, so a coding agent stops inventing props.

bash
# Claude Codeclaude mcp add liquefy-ui -- npx -y @liquefy-ui/mcp
json
{  "mcpServers": {    "liquefy-ui": { "command": "npx", "args": ["-y", "@liquefy-ui/mcp"] }  }}
ToolAnswers
get_conventionsThe rules that are easy to get wrong: the client boundary, the required provider, which props do not exist
list_componentsEverything in the library, filterable by ui / hook / lib
get_componentOne component's exports and every exported type declaration, verbatim
search_componentsFree text over names, descriptions and type declarations
get_component_sourceThe copy-paste source, imports already rewritten to shadcn aliases
get_tokensThe --lq-* tokens and their real values, per theme scope

Docs: https://liquefy-ui.com/#/guides/ai-tooling

The catalog is generated from the library source at build time, so it cannot drift from what the package ships. The server has no runtime dependencies and never touches the network.

Source: packages/mcp/README.md at commit 96af8d8

Tools

8

list_components

List every component, hook and internal module in liquefy-ui with a one-line description. Start here when you do not know what the library contains.

Parameterskind

get_component

Get the real API of one component: its exported names, every exported type declaration verbatim, the import line, and the docs and registry URLs. Use this instead of guessing prop names.

Parametersnamerequired

search_components

Free-text search across component names, descriptions and type declarations. Use it to answer "is there a component for X" or "which component has prop Y".

Parametersqueryrequired

get_component_source

Get the copy-paste source of a component, with imports already rewritten to shadcn aliases (@/components/ui, @/lib, @/hooks). Use this when the user wants to own and edit the code.

Parametersnamerequired

get_tokens

List the --lq-* design tokens and their real values, per theme scope.

Parameterstheme

list_icons

List the icons in @liquefy-ui/icons by name, with their props. Use it before reaching for another icon library, and to check a name exists rather than guessing it.

Parametersquery

get_core_api

The public API of @liquefy-ui/core, the dependency-free engine under the components: the WebGL renderer, the bezel lens, the spring integrator and the tokens. Use it to drive the physics on an element the React components do not cover.

Takes no parameters.

get_conventions

The conventions of this library that are easy to get wrong: the client boundary, the required provider, the styles prop, which props do not exist. Read this before writing liquefy-ui code.

Takes no parameters.

Version history

2
  1. v0.1.5LatestOct 30, 2026
  2. v0.1.4Sep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts