Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Guidelines for UI components with a perfect UX, DX and AX, whether humans or AI agents write them.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.opencomponents.dev/mcp在终端中运行这条命令
claude mcp add --transport http open-components https://mcp.opencomponents.dev/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"open-components": {
"url": "https://mcp.opencomponents.dev/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"open-components": {
"type": "http",
"url": "https://mcp.opencomponents.dev/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.opencomponents.dev/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 uxfront.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于27天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Safe Fetch
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
MCP server for fetching URLs, safe against SSRF, DNS rebinding, and redirect-to-internal attacks.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Open Components
Open Components is the standard for perfect UI components: guidelines for building UI components with a perfect user experience, developer experience and agentic experience, whether humans or AI agents write them.
Open Components is part of UXFront , written and maintained by @alexgrozav .
Homepage · Documentation · Changelog · llms.txt · Issue Tracker
The standard has three layers, one for each audience a component serves. A component meets the standard when it meets all three.
Learn the guidelines once, then hold every component to the same high standards, whether you or your agents write it.
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.
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/ .md holds one page, as in /raw/docs/getting-started/introduction.md for the introduction.https://opencomponents.dev/raw/ .yaml holds 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.json is 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.txt lists every page and every contract./llms-full.txt holds them all in one file. Point your agent at it to give it the whole standard in one request.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.
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!
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 © 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.