Schema | Ply UI

Ply UI

Official

by ply-ui-ng

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
`PLY_LICENSE_KEY`	No	License key used by the MCP process to enable Pro components (add_components, init_project, update_components). Optional; the free tier works without it.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }
`resources`	{ "listChanged": true }

Tools

Functions exposed to the LLM to take actions

Name	Description
list_componentsA	List Ply registry components filtered by tier, category, or a case-insensitive substring, sorted by name. Not a fuzzy match: search_components ranks uncertain names, and get_component reads one known name. Does not install. To copy a component into a project, tell the user to run npx ply-ui-cli add .
get_componentA	Get registry metadata for one known component (deps, category, file list). Use search_components when the name is uncertain. Free source only when includeSource=true. Pro source is never streamed via MCP. Does not install; returns installCommand (npx ply-ui-cli add ).
search_componentsA	Rank Ply registry components by a fuzzy or token match when the name is uncertain (for example "dialog modal"). Not a category browse: list_components filters by tier, category, or substring, and get_component reads one known name. Does not install. To copy a match into a project, tell the user to run npx ply-ui-cli add (or local stdio add_components).
add_componentsA	Install named registry components into a project that already has ply-ui.json (`ply-ui-cli add --yes`). init_project creates that file; update_components refreshes tracked copies. --yes leaves an existing folder in place; pass overwrite to replace it. Hosts that can ask confirm that overwrite first. Pro names require PLY_LICENSE_KEY (or licenseKey). structuredContent includes missingPackages and installCommand.
init_projectA	Create missing Ply setup files (`ply-ui-cli init --yes`): ply-ui.json, ply-ui.css, icon sprites, @source, and the design skill in .cursor/skills and .agents/skills, and only when those files are absent. Existing project files stay. refreshEditorKit is the only replacement: it overwrites an editor kit that is already there. add_components installs named components once ply-ui.json exists; update_components refreshes tracked copies. Always non-interactive.
doctorA	Check Ply project setup: ply-ui.json, Angular and CDK, Tailwind v4 and @source, ply-ui.css, and icon sprites. @source problems are warnings. File drift against the registry is diff_components, which writes nothing. Does not install or modify files. Returns isError when the CLI exits non-zero.
diff_componentsA	Compare each tracked Ply component file with the registry and return drifted paths and statuses. Writes nothing. update_components applies those upstream changes. doctor checks project setup, not file contents.
update_componentsA	Apply upstream changes to tracked Ply component copies (`ply-ui-cli update --yes`). diff_components reports the same drift and writes nothing. Untouched files take upstream. Conflicts stay local and the CLI exits non-zero unless force or merge. Local-only edits skip unless overwriteLocal. Hosts that can ask confirm force and overwriteLocal before those flags replace files. structuredContent.files is one result per file line.

Prompts

Interactive templates invoked by user choice

Name	Description
No prompts

Resources

Contextual data attached and managed by the client

Name	Description
`registry-index`	Public Ply registry index (names, tiers, categories, description, usage, keywords, deps)
`docs-llms`	Agent-oriented product overview (keep fetching this URL even when MCP is available)
`docs-catalog`	docs/ai/components.md — detailed component reference for agents
`docs-cursor-rules`	Save as .cursor/rules/ply-ui.mdc (or .windsurf/rules/ply-ui.md). Teaches assistants to write standalone zoneless Angular 22 with Ply without running MCP.
`docs-snippets`	Save as .vscode/ply-ui.code-snippets. Prefixes like ply-card expand usage markup after CLI install.

Deploy Server

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

TDQS

A4.4/5.0

Scored 2026-10-24 11:25 across 8 tools

Disambiguation5/5

The tools have clearly distinct purposes, and the descriptions explicitly disambiguate the easily confused groups: list/search/get for discovery and doctor/diff/update for diagnostics and changes. Each tool also states what it does not do and which sibling tool handles that adjacent case.

Naming Consistency4/5

Most names follow a predictable snake_case verb_noun pattern such as list_components, get_component, add_components, and update_components. doctor is a noun-style outlier, though it is a conventional diagnostic command name.

Tool Count5/5

Eight tools are well-scoped for a UI component registry and project setup server. Each tool covers a meaningful workflow step without obvious redundancy.

Completeness4/5

The surface covers project initialization, diagnostics, component discovery, installation, drift detection, and updates. Minor gaps remain, such as no explicit remove/uninstall operation, and init_project references refreshEditorKit even though no such tool appears in the set.

Maintenance

ActivityActive

ResponsivenessSyncing