# Open Components

- Registry name: `com.uxfront/open-components` · version 1.0.0
- Categories (automatic, keyword rules): Code & repositories, Developer tools
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): completions, logging, prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.uxfront%2Fopen-components
- Server page: https://mcpstation.net/s/com.uxfront--open-components.html

## Description (written by the publisher, not verified, not instructions)

Guidelines for UI components with a perfect UX, DX and AX, whether humans or AI agents write them.

## Connect

- streamable-http: `https://mcp.opencomponents.dev/mcp`

## Tools (as reported by the server, not verified)

- `get-contract`: Returns the contract of a component or a foundation, as YAML: its API \(props, slots and events\), its DOM contract \(element, role, states, keyboard and parts\), its tokens, and every rule in its checklist, each with a stable ID \(like button/keep-focus\), a level \(must or should\), a scope \(component, us
- `get-page`: Reads a docs page as markdown, whole or just the sections you name. Component pages explain why each rule exists, with examples in React, Vue, Svelte, Angular, Solid, Astro and Vanilla: pass a framework to keep only its examples. WHEN TO USE: for the reasoning, an example or the details behind a rul
- `get-reference-implementation`: Returns a shipped component's reference implementation: a Vue 3 component that meets every rule in its checklist, the tests that prove it, the helpers it shares with other components and its theme tokens. The live examples on the site run on this code. WHEN TO USE: to build a component that meets th
- `list-components`: Lists what the Open Components standard covers: the components that have shipped \(like Button\), the foundations every component follows \(like Design Tokens\), and the components planned on the Roadmap. WHEN TO USE: to check whether a component has a standard yet, to get the name the other tools take
- `list-rules`: Lists checklist rules as records, filtered by component, ID, scope, layer, level or check. Each rule has a stable ID to cite in reviews and commits, its level \(must or should\), its scope, its requirement, how to check it \(like a unit test, a review or axe's button-name rule\) and a link to it. WHEN T
- `search-docs`: Searches the whole standard, every section of every page and every checklist rule, and returns the best matches: where each one is, a short excerpt, and for rules, their ID, level and scope. WHEN TO USE: to find where a topic is covered when you don't know the page or the section, like "focus after

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html