Open Components
Server Details
Guidelines for UI components with a perfect UX, DX and AX, whether humans or AI agents write them.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- uxfront-com/open-components
- GitHub Stars
- 7
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 6 tools
Each tool targets a distinct artifact type: contract YAML, docs prose, reference code, component index, rule records, and search. The only genuine overlap is that get-contract also carries every checklist rule while list-rules is the filtered rule browser, but descriptions explicitly route users ("for some of the rules only, use list-rules
All six names follow a strict kebab-case verb_noun pattern: get-contract, get-page, get-reference-implementation, list-components, list-rules, search-docs. The verb choice (get vs list vs search) also maps consistently to single-item fetch, enumeration, and query.
Six tools is well-scoped for a read-only standard/docs server: one index lister, one contract fetcher, one docs reader, one code fetcher, one rule query, one search. Each fills a distinct retrieval need with no filler tools.
The surface covers the full read lifecycle for the domain: discover components/foundations, read contracts, read prose sections, fetch implementations, query rules (with pagination), and full-text search. Minor gap: no explicit tool to enumerate all pages or a section table of contents outside of long-page outlines and search, and get-page outlines require a follow-up call, but agents can work around this.
Available Tools
6 toolsget-contractGet ContractARead-onlyIdempotentInspect
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, usage or both) and how to check it. It holds every requirement in a fraction of the page's length, and it's the same file as https://opencomponents.dev/raw/docs/.yaml.
WHEN TO USE: first, before you build, review or explain a component or its tokens. WHEN NOT TO USE: for some of the rules only (by scope, layer, level or check), use list-rules. For the reasoning or the examples behind a rule, use get-page with its sections.
Inputs: component (required).
get-pageGet PageARead-onlyIdempotentInspect
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 rule (like the sections ["Loading"] of the button's page), or for a page without a contract, like the introduction or the roadmap. WHEN NOT TO USE: for the requirements alone, use get-contract or list-rules, which are much shorter. To find which page or section covers a topic, use search-docs.
A page longer than about 8,000 tokens, like the button's, returns its outline instead: every heading with its anchor and length, so you can ask for the sections you need. So do sections that are too long to return together.
Inputs: path (required), sections, framework.
get-reference-implementationGet Reference ImplementationARead-onlyIdempotentInspect
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 the standard, in Vue or by porting it and its tests to another framework, or to see how a rule is met in code. WHEN NOT TO USE: for the requirements, use get-contract. For how the component is used in another framework, use get-page with that framework.
Inputs: component (required), files.
list-componentsList ComponentsARead-onlyIdempotentInspect
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 for it, or to see what's planned. WHEN NOT TO USE: if you already know the component, call get-contract directly. To find a topic in the docs, use search-docs.
Shipped entries come with their page, their contract and how many rules they have. Planned ones have no page, contract or rules yet: hold them to the three layers and Design Tokens, following the Button's structure, as the build-component prompt does.
Inputs: status. Returns: total, components
list-rulesList RulesARead-onlyIdempotentInspect
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 TO USE: to review code rule by rule, to get only the rules that apply to a task, to look rules up by ID, or to find the ones a tool can check. Pass scope ["component", "both"] to build or review a component, and ["usage", "both"] to review a screen that uses it. WHEN NOT TO USE: for a component's API, DOM contract and tokens, use get-contract, which has every rule too.
It returns up to 50 rules at a time, and total counts every rule that matches. When there are more, pass nextOffset as offset, with the same filters, to get the next page.
A component meets the standard when it meets every must rule. Each should rule is expected unless there's a good reason not to follow it.
Inputs: ids, check, layer, level, +5 more. Returns: rules, total, unknown, nextOffset
search-docsSearch DocsARead-onlyIdempotentInspect
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 delete", "spinner", "aria-pressed" or "dark mode". Then read a section with get-page, or rules with list-rules. WHEN NOT TO USE: to list a component's rules, use list-rules. To see which components there are, use list-components.
Search for a few specific words rather than a whole question.
Inputs: query (required), type, limit, component. Returns: query, total, results
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
A design harness for AI coding agents: design systems, design principles, icons and UI review.
UI references for coding agents: real screens, flows, components, fonts and animated icons.
Live React design-system APIs, patterns, and code validation so AI agents build real UI, not slop.
Human know-how for AI agents: rules, reasons and checks for design, code, product and writing.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceProvides design systems, UI prompts, and layout variation guidance to AI coding tools for generating better user interfaces.321 npm2,255MIT
- AlicenseBqualityBmaintenanceEnables AI coding agents to absorb UI references into perceptual design tokens, semantic responsive layout skeletons, motion physics parameters, and zero-dependency multi-framework components, while auditing WCAG contrast, touch targets, reduced-motion guardrails, and layout stability.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to generate bespoke design systems by synthesizing OKLCH color palettes, chamfer highlights and spring physics, teaching layout composition grammar, and returning micro-interaction primitives and component blueprints. Also audits JSX/TSX/HTML through a senior design director's lens to score and critique UI quality.1MIT
- AlicenseBqualityDmaintenanceProvides AI assistants with tools to grade, generate, and validate UI components against the components.build specification. Supports searching documentation, checking compliance, and generating framework-agnostic accessible components.1124 npmApache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.