Open Components MCP server
Commit Nov 14, 2026Gives AI agents UI component guidelines, contracts and rules for building accessible, well-designed components.
Also known as uxfront-com/open-components, open-components
- Stars
- 16
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.0.0
- Last commit
- Nov 14, 2026
- License
- MIT
What is Open Components MCP?
Open Components gives AI agents UI component guidelines, contracts and rules for building accessible, well-designed components.
Summary generated from the project's README
About Open Components MCP server
Providing AI agents with structured UI component guidelines and contracts is what Open Components does for developers and designers. It offers a standardized framework to ensure that components meet high requirements for user experience, developer experience, and agentic experience. By using this server, agents can access semantic, deterministic, and verifiable rules to build accessible and predictable interfaces.
Users can connect the MCP server via a remote endpoint without needing a sign-in or payment. It integrates with various clients including Claude, Cursor, VS Code, Gemini CLI, Grok, and Hermes Agent. Developers can also use the dedicated agent plugin for environments like GitHub Copilot and Claude Code to build and review components against the established standard. The system provides specific tools such as YAML contracts and JSON schemas to help validate that every component remains consistent and type-safe.
What you can do with it
- 1Validate component complianceAsk an AI agent to check a newly written UI component against the official component contracts and rules.
- 2Generate standardized component codeInstruct an AI client to build a new UI element that follows specific UX and DX guidelines.
Written from the project's README. Every use case is checked against a quote from it.
How to install Open Components MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Open Components MCP in Claude Code
$ claude mcp add --transport http open-components https://mcp.opencomponents.dev/mcpInstall Open Components MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"open-components": {
"url": "https://mcp.opencomponents.dev/mcp"
}
}
}Install Open Components MCP in VS Code
.vscode/mcp.json
{
"servers": {
"open-components": {
"type": "http",
"url": "https://mcp.opencomponents.dev/mcp"
}
}
}Install Open Components MCP in VS Code CLI
$ code --add-mcp '{"name":"open-components","type":"http","url":"https://mcp.opencomponents.dev/mcp"}'Install Open Components MCP in Codex
$ codex mcp add open-components --url https://mcp.opencomponents.dev/mcpInstall Open Components MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.open-components] url = "https://mcp.opencomponents.dev/mcp"
Install Open Components MCP in Gemini CLI
$ gemini mcp add -s user --transport http open-components https://mcp.opencomponents.dev/mcpInstall Open Components MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"open-components": {
"url": "https://mcp.opencomponents.dev/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableuxfront-com/open-components is public and reachablegithub.com/uxfront-com/open-components ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-12github.com/uxfront-com/open-components ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 323 msPass
README
View on GitHubTable of contents
- The standard
- Reading the standard
- For agents
- Bugs and feature requests
- Contributing
- Creator
- Copyright and license
The standard
The standard has three layers, one for each audience a component serves. A component meets the standard when it meets all three.
- User experience (UX): components behave the way people expect them to, with any input, on any device and for every ability. Accessible, predictable, every state, adaptive.
- Developer experience (DX): one clear API, learned once and used everywhere. Knowing one component means knowing them all. Consistent, type-safe, composable, controllable.
- Agentic experience (AX): components that AI agents can read, reason about and build with, so their output meets the same bar as yours. Semantic, described, deterministic, verifiable.
Learn the guidelines once, then hold every component to the same high standards, whether you or your agents write it.
Reading the standard
Start with the Introduction, which walks through the three
layers and what each one asks of a component. The guidelines live as markdown in
content/docs/, so you can also read them right here on GitHub.
For agents
If your agent supports MCP, connect it to our MCP server at https://mcp.opencomponents.dev/mcp,
free and with no sign-in. It gives agents the contracts, every rule and the docs a section at a
time, as tools. The MCP Server page
shows how to connect Claude, Codex, Cursor, VS Code, Gemini CLI, Grok, Hermes Agent and other
clients.
Or install our agent plugin, in plugins/open-components, which
connects the same server along with skills that build and review components the way the standard
asks. It's an Agent Plugin, so it works in VS Code, GitHub Copilot,
Cursor, Codex, Claude Code and other clients that support the format. The
Agent Plugin page shows how to
install it.
Every page of the documentation is also published as markdown, so agents can read the standard and check their work against it:
https://opencomponents.dev/raw/<path>.mdholds one page, as in/raw/docs/getting-started/introduction.mdfor the introduction.https://opencomponents.dev/raw/<path>.yamlholds a page's contract, with every rule from its checklist, as in/raw/docs/components/button.yaml. It's every requirement in a fraction of the page's length./schemas/contract.jsonis the JSON Schema every contract follows, so you can validate them, and contracts of your own. Each contract names it on its first line, so editors that use the YAML language server check it as you type./llms.txtlists every page and every contract./llms-full.txtholds them all in one file. Point your agent at it to give it the whole standard in one request.
Bugs and feature requests
Found a bug on the site, a gap in the guidelines or an idea for a new one? Please first search for existing and closed issues. If your problem or idea is not addressed yet, please open a new issue.
Contributing
Please read through our contributing guide. There you can find how to run the site locally, edit the guidelines and deploy. Everyone taking part in the project agrees to follow our Code of Conduct.
Thanks goes to these wonderful people!
Creator
Alex Grozav
If you use Open Components in your daily work and feel that it has made your life easier, please consider sponsoring me on GitHub Sponsors. 💖
Copyright and license
Copyright © 2026 UXFront. The site code is released under the
MIT License. The guidelines in content/ and the agent plugin in
plugins/open-components/ are released under the
Creative Commons Attribution 4.0 License: you can share and adapt them,
commercially too, as long as you credit Open Components.
Open Components MCP questions
How do I add Open Components MCP to Claude Code?
Run claude mcp add --transport http open-components https://mcp.opencomponents.dev/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Open Components MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Does the Open Components MCP server cost anything or need an account?
No. The server is free and requires no sign-in.
What can agents retrieve from the Open Components MCP server?
It provides the contracts, every rule and the docs a section at a time, exposed as tools.
Is there an agent plugin for Open Components?
Yes, there is an agent plugin in plugins/open-components that connects the same server plus skills for building and reviewing components. It follows the Agent Plugin format and works in VS Code, Copilot, Cursor, Codex, Claude Code and similar clients.
Can I get the whole standard in one file for my agent?
Yes, /llms-full.txt contains every page and contract in a single file. /llms.txt lists every page and contract instead.