Summary
A bridge, not a model: the component knowledge lives in the Dify app behind the key.
That is the whole shape of it — the server handles the MCP side, the upload and the streaming, and the Dify application decides what good Ant Design code looks like. Being able to attach an image is what makes it useful in practice: hand it the design and ask for the component.
What it is
A TypeScript server that forwards your request to a Dify AI application built for Ant Design component generation, and streams the answer back.
What you get
- antd-component-codegen-mcp-tool generates Ant Design business-component code
- Text input, and optionally an image alongside it
- Image files uploaded to Dify as part of the request
- Streaming responses from the Dify API rather than one blocking wait
Requirements
A Dify API key, supplied as DIFY_API_KEY in the client's environment block. Build the TypeScript with npm run build, then have the client launch build/index.js with node. Config examples are given for both Continue and Cline.
Setup effort
Build from source — clone the repository and build it, then point your client at the binary