perfectui-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_installA | How to install Perfect UI 1.0.0: the npm command and the other package managers' commands, the CDN stylesheet and script URLs and the import statements, all pinned to this version, from the library's installation document (get_component with name installation explains when the script is needed). |
| list_componentsA | Every document of Perfect UI 1.0.0, in the documentation's order: components, forms, layout, customization and guides, each with its slug (the name get_component takes), title, section and one-line description. |
| get_componentA | The full Markdown of one Perfect UI 1.0.0 document, with its HTML examples and the pui-* classes they use. Copy markup from the examples instead of writing classes from memory. Names come from list_components. |
| search_docsA | Full-text search over the sections of every Perfect UI 1.0.0 document (prefix and typo tolerant). Returns the document slug (for get_component), the section heading (empty for the opening section), a snippet and a score, best first. |
| check_markupA | Lists every pui-* class in the HTML that Perfect UI 1.0.0 does not define (kind "unknown"), with its line and the closest real class, and every Perfect UI 0.23.0 class that the migration guide renames (kind "legacy"), with the guide's replacement. Reads class and className attributes only; other classes (your own, Tailwind) are ignored. Call it on any markup before returning it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
get_install and get_component both retrieve documentation content for installation, but get_install is a specialized shortcut for install commands while get_component returns full Markdown of any document; descriptions clarify the boundary. Other tools (list_components, search_docs, check_markup) have clearly distinct purposes. Minor overlap prevents a perfect score.
All tool names follow a consistent snake_case verb_noun pattern (get_install, list_components, search_docs, get_component, check_markup). This makes the set predictable and easy to parse.
Five tools cover the essential operations for a UI library documentation server: installation lookup, listing documents, searching, retrieving a document, and validating markup. Each tool has a clear role and the set is well-scoped.
The surface covers installation, discovery (list, search), retrieval, and validation, including legacy class migration. No obvious dead ends for the stated purpose of helping agents use Perfect UI correctly; the documentation lifecycle is fully covered.