@ant-design/cli 6.3.3 → 6.3.5-beta.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ant-design/cli",
-  "version": "6.3.3",
+  "version": "6.3.5-beta.0",
   "description": "CLI tool for querying antd knowledge and analyzing antd usage in projects",
   "type": "module",
   "bin": {
@@ -43,7 +43,9 @@
     "access": "public"
   },
   "dependencies": {
-    "commander": "~13.1.0"
+    "@modelcontextprotocol/sdk": "^1.27.1",
+    "commander": "~13.1.0",
+    "oxc-parser": "^0.121.0"
   },
   "devDependencies": {
     "@types/node": "^25.5.0",

package/skills/antd/SKILL.md

@@ -25,6 +25,8 @@ Before first use, check if the CLI is installed. If not, install it automaticall
 which antd || npm install -g @ant-design/cli
 ```
 
+After running any command, if the output contains an "Update available" notice, run `npm install -g @ant-design/cli` to update before continuing.
+
 
 **Always use `--format json` for structured output you can parse programmatically.**
 
@@ -203,6 +205,23 @@ antd bug-cli --title "antd info Button returns wrong props for v5.12.0" \
 
 **Key principle:** You are a quality feedback loop for the CLI. Don't silently work around CLI issues — report them so they get fixed. Always confirm with the user before submitting.
 
+### 10. Using as MCP server
+
+If working in an IDE that supports MCP (Claude Desktop, Cursor, etc.), the CLI can also run as an MCP server, exposing all knowledge-query tools directly:
+
+```json
+{
+  "mcpServers": {
+    "antd": {
+      "command": "antd",
+      "args": ["mcp", "--version", "5.20.0"]
+    }
+  }
+}
+```
+
+This provides 7 tools (`antd_list`, `antd_info`, `antd_doc`, `antd_demo`, `antd_token`, `antd_semantic`, `antd_changelog`) and 2 prompts (`antd-expert`, `antd-page-generator`) via MCP protocol.
+
 ## Global Flags
 
 | Flag | Purpose |