
wot-ui/open-wot
Developer toolsThis page was translated automatically. Technical details may differ from the original. View the original
Wot UI's AI capability toolkit: Skills, MCP protocol, and CLI tools, among others
Overview
Official Website · Quick Start · Agent Access · CLI · MCP · Participate in contributions Component documentation should not be just for people to read. Open Wot packages wot-ui v2 component knowledge into offline data and provides it to developers and AI agents via CLI, MCP, and Skills. - :Query real props, events, slots, CSS variables, and demo source code. - :Automatically identify project dependencies and precisely query specified WOT-UI versions. - :Component data is published with npm packages, no documentation API or keys required. - :Supports dry-run, power-etc writes, atomic updates, and failure protection. --client all Under project scope, it handles Claude Code, Cursor, VS Code, Codex, OpenCode, and Antigravity; In user scope, only clients that support user-level configuration are handled. After configuration, restart the client; If prompts like "Trust Project" or "Approve MCP Server" appear, please follow the client instructions to confirm. AI without context easily mixes Vue component library APIs, uses properties that don't exist, or generates code that doesn't match the project version. Open Wot adds accurate wot-ui context before AI writes code: agent init is the recommended entry point; it simultaneously configures the MCP, installs the skill, and writes project instructions managed by open-wot. - --dry-run only shows the change plan, not the file. - Interactive write operations request acknowledgments; Agent or CI explicitly passes --yes. - Repeated init execution does not repeatedly insert configurations. - Remove only removes open-wot management content and does not overwrite other server or user configurations. - By default, the component user-oriented wot-ui-v2 skill is installed; Warehouse maintenance skill wot-ui-cli is not installed by default.
Overview (machine translated)
@wot-ui/cli
Let AI truly understand wot-ui.
Integrate component APIs, documentation, examples, and version knowledge into your terminal and AI programming tools.
Official website · Let’s get started · Agent access · CLI · MCP · Participate in contributions
Component documentation should not be just for people to read. Open Wot packages wot-ui v2 component knowledge into offline data and provides it to developers and AI agents via CLI, MCP, and Skills.
- No Guessing API: Query real props, events, slots, CSS variables, and demo source code.
- Version matching: Automatically identifies project dependencies and can precisely query the specified WOT-UI version.
- Knowledge available offline: Component data is published with npm packages, no documentation API or keys required.
- Configurable Secure and Controllable: Supports dry-run, idempotent writes, atomic updates, and failure protection.
🚀 30-second access
Requires Node.js >= 20.
Upon completion, the current project will receive:
When using other clients, simply replace the client ID:
| Claude Code | Cursor | VS Code | Codex | OpenCode | Antigravity | DeepSeek Harness |
|---|---|---|---|---|---|---|
claude |
cursor |
vscode |
codex |
opencode |
antigravity |
deepseek |
| Qoder IDE | Qoder CLI | CodeBuddy IDE | CodeBuddy Code CLI |
|---|---|---|---|
qoder |
qoder-cli |
codebuddy |
codebuddy-cli |
DeepSeek Harness also defaults to project-by-project; Please run it in the root directory of Git, or add --cwd . After the first installation, restart the desktop version and reopen the project session.
When using multiple AI clients simultaneously, you can complete all project-level configurations at once:
--client all Under the project scope, it handles Claude Code, Cursor, VS Code, Codex, OpenCode, Antigravity, and DeepSeek Harness; Within the user scope, only clients that support user-level configuration, including DeepSeek Harness, are handled.
This page was translated automatically. Technical details may differ from the original.
Install
npx -y @wot-ui/cli mcpConfiguration
{
"mcpServers": {
"wot-ui": {
"command": "npx",
"args": ["-y", "@wot-ui/cli", "mcp"]
}
}
}