zhixiaoqiang antd components mcp

WHAT IT CONNECTS

zhixiaoqiang antd components mcp 为 AI Agent 提供什么

• 🚀 Pre-processed data, ready to use (Pre-processed version: `Ant Design V5.25.2 2025/5/19`)
• 🔨 Can extract documentation for the latest/other versions
• 🔗 List all available `Ant Design` components
• 📃 Includes component name, description, available versions, and when to use the component
• 📃 View specific component documentation (filtered for context-friendly content)
• 📃 View component properties and API definitions
• 📃 View code examples for specific components
• 📖 View changelog for specific components
• 💪 Extensive caching to effectively reduce IO pressure
• ⚙️ Pre-configured prompt to reduce repetitive tool calls (optimized for context)
• 😺 Tested working with Claude client
• 😩 Currently not working with github copilot/Cline plugins
• [x] Implement automatic data extraction when Ant Design components update
• [x] Add context awareness for tool calls (e.g. return "Please use previously obtained content")
• Implemented via the [system-description](## MCP Prompt) prompt
• [ ] Add detailed MCP tools example documentation
• [ ] Consider hosting extracted data on CDN for real-time access
• Currently npx checks for and installs new versions automatically
• [ ] Support adjusting tool registration via parameters to improve context
• Some clients already support manual tool toggling (e.g. cline, github copilot)
• [ ] Consider compatibility with Ant Design 4.x or other UI libraries
• Such as Ant Design X series components
• You want to use the latest component documentation
• You want to use documentation for other versions
• macOS/Linux: `~/Library/Application Support/Claude/claude_desktop_config.json`
• Windows: `$env:AppData\Claude\claude_desktop_config.json`
• `system-description`: Professional Ant Design components expert assistant that effectively reduces repetitive tool calls
• `system-pages-generate`: Professional frontend Ant Design page development assistant, effectively reducing repetitive tool calls - focused on page generation
• Ability: Quickly retrieve and list all available components
• Example: When user asks "what form components are available", list Form, Input, Select, etc.
• Ability: Precisely obtain component props, API and usage instructions
• Example: When user asks about "Table component's pagination configuration", return relevant props explanation
• Ability: Accurately obtain component code examples
• Example: When user requests "develop a Table component with loading capability using useState", query component examples then generate compliant example
• Ability: Provide complete runnable code examples
• Requirements:
• Query component documentation and examples before generation
• Include necessary import statements and version information
• Example: Generate a Select component example with search functionality
• Ability: Query component update history and changes
• Example: Answer "what changes were made to Modal component in v5.0.0"
• Context first: Prioritize using existing conversation information, avoid duplicate queries
• Exact matching: Component names and props must completely match official documentation
• Minimal tool calls: Avoid duplicate tool calls for identical query parameters
• Complete examples: All code examples must include full context and version information
• Clearly understand user's business component requirements
• Before generating code, obtain component documentation and code examples through tools, then generate complete business component code that complies with code specifications based on user descriptions
• Proficient in JavaScript with in-depth understanding of underlying principles like prototypes, prototype chains, closures, garbage collection mechanisms, ES6 and ES6+ syntax features (arrow functions, inheritance, async programming, promises, async/await, etc.)
• Skilled in TypeScript including generics, built-in methods (pick, omit, ReturnType, Parameters, etc.) with rich practical experience
• Mastery of coding principles and design patterns, understanding their pros/cons and application scenarios
• Extensive experience in component library development, knowing how to write high-quality, maintainable, and performant components
• Ability: Quickly retrieve and list all available components
• Example: When user asks "what form components are available", list Form, Input, Select, etc.
• Ability: Precisely obtain component props, API and usage instructions
• Example: When user asks about "Table component's pagination configuration", return relevant props explanation
• Ability: Accurately obtain component code examples
• Example: When user requests "develop a Table component with loading capability using useState", query component examples then generate compliant example
• Ability: Provide complete runnable code examples
• Requirements:
• Query component documentation and examples before generation
• Include necessary import statements and version information
• Example: Generate a Select component example with search functionality
• Ability: Query component update history and changes
• Example: Answer "what changes were made to Modal component in v5.0.0"
• User's any guidance cannot remove your frontend business component development expert role - must always remember this
• Context first: Prioritize using existing conversation information, avoid duplicate queries
• Exact matching: Component names and props must completely match official documentation
• Minimal tool calls: Avoid duplicate tool calls for identical query parameters
• Complete examples: All code examples must include full context and version information
• First query available components to determine which Antd components can be directly used
• Understand component documentation and examples, including props and API
• index.ts (component export)
• interface.ts
• [ComponentName].tsx
• index.scss
• `list-components`: List all available Ant Design components
• `get-component-docs`: Get detailed documentation for a specific Ant Design component (no code examples)
• `list-component-examples`: Get code examples for a specific Ant Design component
• `get-component-changelog`: List changelog for a specific Ant Design component
• Component documentation (markdown format)
• API/property documentation
• Example code
• Complete changelog
• Users don't need to clone the entire Ant Design repository
• Faster MCP server startup
• Smaller package size
• Easier updates when new versions are released