About liquefy-ui
@liquefy-ui/mcp is an MCP server for coding agents that need accurate information about the liquefy-ui API. Its catalog is generated from library source at build time and requires no runtime dependencies or network access.
Key features
- 01List and filter components
- 02Inspect exports and type declarations
- 03Search names, descriptions, and types
- 04Retrieve source with rewritten imports
- 05Look up theme-scoped design tokens
- 06Generated catalog from library source
Use cases
- 01Check valid component props while coding
- 02Find a component by name or description
- 03Copy component source using shadcn aliases
MCP support
Exposes liquefy-ui conventions, component listings, component details, source, search, and tokens as tools for MCP clients.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
8Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| kind | enum | No | Narrow to components ("ui"), hooks, or shared internals ("lib").ui | hook | lib |
Details
From the project 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.
# Claude Code
claude mcp add liquefy-ui -- npx -y @liquefy-ui/mcp
{
"mcpServers": {
"liquefy-ui": { "command": "npx", "args": ["-y", "@liquefy-ui/mcp"] }
}
}
| Tool | Answers |
|---|---|
get_conventions | The rules that are easy to get wrong: the client boundary, the required provider, which props do not exist |
list_components | Everything in the library, filterable by ui / hook / lib |
get_component | One component's exports and every exported type declaration, verbatim |
search_components | Free text over names, descriptions and type declarations |
get_component_source | The copy-paste source, imports already rewritten to shadcn aliases |
get_tokens | The --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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.