change-component-version
Switches the Ant Design version that the other tools answer against.
LABSCO SUMMARY
Version-aware antd answers, instead of props that never existed.
The changelog and version switch are what set this apart from a model recalling Ant Design from training: asking whether a component supports something becomes a question with a version attached, which is the form the question actually takes in a real project. Fetch the examples and the typed API before generating a screen — the union types are exactly the detail that makes generated antd code compile or fail.
What it is
A local Ant Design reference. Component documentation, example code, API tables and changelogs are bundled and served as tools, and the active antd version can be switched so the answers match the version the project is on.
What you get
- The list of available components, for turning a described interface into the components that can build it
- Full documentation for one or several named components in a single call
- Example code per component, so generation starts from working usage rather than from an invented prop set
- The component API with TypeScript types and union values — the part that decides whether a prop takes a string or one of four literals
- Changelogs for named components, which answers whether the feature you want exists in the version installed or needs an upgrade
- A version switch, so all of the above answer for the antd version the project actually uses
- Best-practice notes per component, gathered by a crawler the author describes as still rough
Requirements
Node.js 16 or newer. It runs as npx antd-mcp, or from a local build with node dist/cli.js after npm install and npm run build. Nothing to authorize and no network calls for lookups — the component docs, examples and API data are extracted into the repository, with scripts to re-extract them from a local clone of the Ant Design repository and to regenerate the component changelog file when it is missing.
Setup effort
One command — npx antd-mcp
USE CASES
01
Building a screen out of the right components
List what is available, then pull documentation and example code for the ones that fit before writing any markup.
02
Getting a prop right the first time
Read the component's API with its TypeScript types and union values, rather than guessing which literals a prop accepts.
03
Working out whether you need to upgrade
Check the component's changelog against the version your project is on, so a missing feature is identified as a version gap rather than a coding problem.
04
Matching the docs to the version you actually run
Switch the active antd version first, so documentation, examples and API answers describe what is installed.
7 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get-best-practices
Returns the recommended usage practices for a named Ant Design component.
get-component-api
Returns a named component's API, including the TypeScript types and union values behind a specified api name.
get-component-changelog
Returns the changelog for one or more named Ant Design components, for checking whether a feature only arrives in a later version.
get-component-docs
Returns detailed documentation for one or more named Ant Design components.
get-component-examples
Returns code examples for one or more named Ant Design components.
list-components
Returns the list of available Ant Design components, for deciding which ones a described interface needs.
BEFORE YOU INSTALL
What to know first
Tools you get
7 tools when we connected.
Requires
- npx on PATH
- Node.js >= 16.0.0
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 7 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx antd-mcpMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"antd-components-local": {
"command": "npx",
"args": [
"antd-mcp"
]
}
}
}
