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