F
licenseNot graded
qualityD
maintenanceEnables AI assistants to access documentation of Vue UI components, including props, events, and slots, for generating correct usage code.
7
-
Element-UI MCP Server
by yun8711
Related Servers
Alternatives to Element-UI MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides AI assistants with comprehensive Ant Design component documentation, examples, API references, and best practices. Supports multiple versions and enables natural language queries for React UI component development.9 npm3-
- AlicenseAqualityDmaintenanceProvides access to Ant Design component library documentation and information for automated code generation. Enables searching components by category or keyword, retrieving component props, examples, API documentation, and available icons.64 npmISC
- AlicenseNot gradedqualityDmaintenanceFetches and structures Ant Design v4 component documentation into JSON format, enabling AI agents to search, analyze, and retrieve component metadata, APIs, and examples.MIT
- FlicenseNot gradedqualityDmaintenanceMCP server providing AI assistants with comprehensive documentation about @deay/ui components, including props, examples, best practices, and Figma design specifications.-
- AlicenseAqualityDmaintenanceProvides reference information for Flux UI components, enabling AI assistants to access component documentation and examples from the Flux UI design system.413 npm93MIT
TDQS
B3.3/5.0
Scored across 8 tools
Disambiguation2/5
Multiple tools have unclear boundaries and significant overlap. For example, get_component already includes events, props, slots, and examples in its output, making get_component_events, get_component_props, get_component_slots, and get_component_examples largely redundant. This creates ambiguity for an agent trying to select the right tool, as it might not know when to use the comprehensive get_component versus the specific sub-tools.
Naming Consistency5/5
The tool names follow a highly consistent verb_noun pattern throughout, with all tools using snake_case and starting with 'get_' or 'list_' or 'search_' followed by a clear noun. This predictability makes it easy for an agent to understand and navigate the tool set without confusion.
Tool Count3/5
With 8 tools, the count is borderline for the server's purpose of accessing Element-UI component information. While it covers various aspects, the redundancy among tools makes it feel heavy and over-specified, as a more streamlined set could achieve the same functionality with fewer tools, reducing complexity for agents.
Completeness4/5
The tool set provides comprehensive coverage for retrieving and searching Element-UI component details, including listings, searches, and detailed breakdowns of properties, events, slots, and examples. A minor gap is the lack of tools for creating, updating, or deleting components, but this is reasonable given the server's likely read-only documentation focus, so agents can still perform core lookup tasks effectively.
Maintenance
ActivityInactive
ResponsivenessNo issues