get-component-changelog
列出 Ant Design 特定组件的更新日志 适用场景：
- 用户询问特定组件的更新日志
- 在知道用户 antd 版本的情况下，当用户需要实现相关组件功能时判断是否在后续版本中才实现，来决定是否需要升级依赖
LABSCO SUMMARY
An agent writes Ant Design against the docs instead of from memory.
What it takes off you is the tab-switching: the component list, the prop table, a working example and the release a prop landed in all arrive as calls, so the code that comes back uses the API as documented rather than as remembered.
What it is
A documentation server for Ant Design. It answers with the library's own component list, API documentation, example code and per-component changelog, so an agent writing a UI reads the components rather than recalling them.
What you get
- The available components, each arriving with its description and the docs' own guidance on when to use it
- One component's full documentation, including its API properties
- The example code the documentation ships for that component
- That component's changelog, which is where the release a prop arrived in is written down
Requirements
npx on your PATH. It serves Ant Design's own documentation, so the component names it takes are the library's and the guidance text comes back in the language the docs are written in.
Setup effort
One command — npx @jzone-mcp/antd-components-mcp
USE CASES
01
Building a screen out of the right components
Start from what the library actually has: the list arrives with each component's description and the docs' own guidance on when to use it, and from there the API and a working example are one call each.
02
Getting a prop right the first time
Read the component's documentation, including its API table, so the attribute names and types in the generated code are the ones the library takes.
03
Finding out whether your version has it
A prop that exists in the docs may have landed after the version you are pinned to. The changelog says which release introduced it, so the answer is upgrade or work around rather than a build error.
04
Starting from code that already works
Pull the examples the documentation ships for a component and adapt one, instead of writing a first version from the prop list and finding out what it missed.
4 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get-component-docs
获取 Ant Design 特定组件的详细文档 适用场景：
- 用户询问如何使用特定组件
- 用户需要查看该组件的 api 属性
list-component-examples
获取 Ant Design 特定组件的代码示例 适用场景：
- 用户询问特定组件的示例时
- 用户想要实现某个功能时直接告知可使用的例子
- 生成页面前需要获取组件的示例代码
list-components
当用户请求一个新的用户界面（UI）使用 Ant Design 组件时使用此工具。 此工具仅返回可用的组件列表。 调用此工具后，你必须编辑或添加文件，以便将代码片段集成到代码库中
BEFORE YOU INSTALL
What to know first
Tools you get
4 tools when we connected.
Requires
npx on PATH
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @jzone-mcp/antd-components-mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"Ant Design Components": {
"command": "npx",
"args": [
"@jzone-mcp/antd-components-mcp"
]
}
}
}
