Ply UI
List, search, and inspect Ply Angular + Tailwind copy-in components.
Sollte ich dies verwenden
Qualität und Sicherheit
Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.
Kontextkosten
Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.
Installieren
Installation mit einem Klick
Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:
{
"mcpServers": {
"ply-ui": {
"url": "https://mcp.ply-ui.com/mcp"
}
}
}Remote-Endpunkte
https://mcp.ply-ui.com/mcpstreamable-httpWas es kann
Tool-Inventar
Tools (3)
🟢list_components(tier, category, q)
List components from the Ply registry. Filter by tier (free|pro|all), category, or name substring. Does not install anything. To copy a component into a project, tell the user to run npx ply-ui-cli add <name>.
Eingabe-Schema
{
"type": "object",
"properties": {
"tier": {
"default": "all",
"description": "Filter by license tier",
"type": "string",
"enum": [
"free",
"pro",
"all"
]
},
"category": {
"description": "Filter by registry category",
"type": "string",
"enum": [
"application",
"page-layout",
"block",
"widget",
"shell",
"component"
]
},
"q": {
"description": "Substring filter on name, description, usage, or keywords (case-insensitive)",
"type": "string"
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_component(name, includeSource)
Get registry metadata for one component (deps, category, file list). Free source only when includeSource=true. Pro source is never streamed via MCP. Does not install; returns installCommand (npx ply-ui-cli add <name>).
Eingabe-Schema
{
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "Registry component name (e.g. button, card)"
},
"includeSource": {
"default": false,
"description": "If true, include free-tier source file contents. Pro source is never returned via MCP in V1.",
"type": "boolean"
}
},
"required": [
"name"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢search_components(query, tier, category, limit)
Fuzzy / token search over registry component names (e.g. "dialog", "sheet", "carousel"). Does not install anything. Prefer this before guessing names, then give the user npx ply-ui-cli add <name> (or local stdio add_components).
Eingabe-Schema
{
"type": "object",
"properties": {
"query": {
"type": "string",
"minLength": 1,
"description": "Natural-language or substring query (e.g. \"dialog modal\", \"button\"). Matches name, description, usage, and keywords."
},
"tier": {
"default": "all",
"description": "Filter by license tier",
"type": "string",
"enum": [
"free",
"pro",
"all"
]
},
"category": {
"description": "Filter by registry category",
"type": "string",
"enum": [
"application",
"page-layout",
"block",
"widget",
"shell",
"component"
]
},
"limit": {
"default": 12,
"type": "integer",
"minimum": 1,
"maximum": 40
}
},
"required": [
"query"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}Community
Nachweis