liquefy-ui — Claude Code MCP server: real library API
Answers questions about liquefy-ui from the library's actual API surface, so your coding agent stops making up props.
claude mcp add liquefy-ui -- npx -y @liquefy-ui/mcpWhat liquefy-ui does
The server hands your agent the real API surface of liquefy-ui: components, exports, type declarations, sources and tokens. Six tools cover the ground. get_conventions spells out the rules that trip people up — the client boundary, the provider you must wrap around your app, props that do not exist. list_components filters by ui, hook or lib. get_component returns one component's exports and every exported type, verbatim. search_components does free-text search across names, descriptions and type declarations. get_component_source gives you copy-paste source with imports already rewritten to shadcn aliases. get_tokens lists the --lq-* tokens with their values per theme scope.
The catalog is built from the library's own source during the build step, so it stays in sync with what the package actually ships. No runtime dependencies, and the server never reaches the network — fine for an air-gapped setup.
Install is one npx command and no API key. Cursor, GitHub Copilot and the rest take a JSON config you write yourself.
What it helps with
- check which props a component actually accepts
- find a component by description or type snippet
- grab component source with imports already fixed
- look up
--lq-*token values per theme - explain the client boundary and provider rules to an agent
Example prompts for the agent
- List the liquefy-ui components filtered by
hook - What types does this component export?
- Give me the component source with shadcn imports
How to install liquefy-ui
Platform CLI
claude mcp add liquefy-ui -- npx -y @liquefy-ui/mcpPlatform CLI
codex mcp add mcp -- npx -y @liquefy-ui/mcpConfig file
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@liquefy-ui/mcp"
]
}
}
}Config file
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@liquefy-ui/mcp"
]
}
}
}Platform CLI
gemini mcp add mcp npx -y @liquefy-ui/mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about liquefy-ui
How do I install liquefy-ui in Claude Code?
Run claude mcp add liquefy-ui -- npx -y @liquefy-ui/mcp. The server starts through npx with no extra setup.
What does liquefy-ui do?
It is an MCP server that answers questions about the liquefy-ui library from its real API: components, types, sources and tokens. It keeps your agent from inventing props.
Does it need an API key or network access?
No. There are no runtime dependencies and the server does not touch the network.
