Element Plus Docs MCP
Related Servers
Alternatives to Element Plus Docs MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for see-u-ui component library, allowing AI assistants to query component props/events/slots/examples on demand.38 npm1MIT
- FlicenseBqualityBmaintenanceA local-only MCP server that provides AI coding agents with up-to-date documentation for specific libraries or tools during feature implementation, including search tools, multi-version support, and user-defined library entries.2-
- AlicenseCqualityDmaintenanceA documentation server based on MCP protocol designed for various development frameworks that provides multi-threaded document crawling, local document loading, keyword searching, and document detail retrieval.347MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that provides developer knowledge and utility tools including local documentation search, text summarization, safe arithmetic calculation, unit conversion, and knowledge-base resources.-
- AlicenseAqualityCmaintenanceAn MCP server that allows users to efficiently search and reference user-configured documents through document listing, grep searching, semantic searching with OpenAI Embeddings, and full document retrieval.43MIT
- AlicenseNot gradedqualityCmaintenanceProvides a local MCP server for searching and retrieving documentation from 22+ open-source projects, enabling AI coding assistants to access up-to-date docs without network dependency.11 npm2MIT
TDQS
Scored across 3 tools
Each tool has a clear, distinct purpose: listing components, retrieving a specific component's documentation, and searching across documentation. There is no functional overlap between the tools.
All tools follow a verb_noun pattern with snake_case, but there is a minor inconsistency in singular vs plural usage ('doc' vs 'docs'). This is a small deviation from an otherwise consistent convention.
Three tools is well-scoped for a documentation server, covering the essential actions of browse, retrieve, and search without unnecessary bloat.
The tool surface covers the core documentation needs: list components, fetch a specific doc, and search across all docs. There are no obvious gaps for its stated purpose.