antd-components-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-component-docsB | 获取 Ant Design 特定组件的详细文档 适用场景：
|
| list-component-examplesB | 获取 Ant Design 特定组件的代码示例 适用场景：
|
| get-component-changelogB | 列出 Ant Design 特定组件的更新日志 适用场景：
|
| list-componentsA | 当用户请求一个新的用户界面（UI）使用 Ant Design 组件时使用此工具。 此工具仅返回可用的组件列表。 调用此工具后，你必须编辑或添加文件，以便将代码片段集成到代码库中 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| system-description | 专业的 Ant Design 组件库专家助手提示词 |
| system-pages-development | 专业的 Ant Design 组件页面开发专家提示词 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: get-component-changelog retrieves version history, get-component-docs provides API documentation, list-component-examples shows code samples, and list-components enumerates available components. There is no overlap in functionality, and an agent can easily distinguish between them based on their specific use cases.
All tool names follow a consistent verb_noun pattern with hyphens: get-component-changelog, get-component-docs, list-component-examples, and list-components. The verbs 'get' and 'list' are used appropriately, and the naming structure is uniform throughout the set.
With 4 tools, this server is well-scoped for its purpose of providing Ant Design component information. Each tool serves a distinct and essential function (changelog, docs, examples, listing), and there are no extraneous tools. The count is appropriate for the domain, allowing comprehensive coverage without bloat.
The tool set covers key aspects of Ant Design components: listing, documentation, examples, and changelogs. This supports common developer workflows like learning, implementing, and upgrading. A minor gap is the lack of tools for searching or filtering components, but the core needs are well-addressed, and agents can work effectively with the provided tools.