appCN
Related Servers
Alternatives to appCN
No user-submitted related servers found.
Related Servers
- AlicenseCqualityFmaintenanceMCP server for searching npm packages146 npm16MIT
- AlicenseAqualityDmaintenanceMCP server that gives LLMs access to up-to-date mobile SDK documentation, package registry info, and GitHub issues.613 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the hy-app component library, enabling AI editors to search components, retrieve APIs and examples, check platform support, access hooks and tools, and validate component usage.7 npmMIT
- AlicenseAqualityBmaintenanceMCP server that lets AI agents search and inspect shadcn components from the encode-ui registry, returning metadata, source code, and install commands.851 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server for the NS UI React component registry. Search components, inspect source and details, list categories, get install commands, and retrieve design-token conventions.13 npm34MIT
- AlicenseNot gradedqualityDmaintenanceUnified MCP server for searching, analyzing, and managing packages across npm, JSR, Deno, and multiple CDN providers with auto-detection.MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing, searching, retrieving full component details, getting install commands, and reading design guidance. There is no meaningful overlap—even list_components and search_components differ explicitly by browse vs. intent-based discovery.
All tool names follow a consistent lowercase snake_case verb_noun convention: get_install_command, get_design_guide, list_components, search_components, get_component. The pattern is uniform and predictable.
Five tools is well-scoped for a component library server: discovery via list/search, detailed retrieval, install support, and design guidance. Each tool earns its place without redundancy or bloat.
The tool surface covers the full workflow of discovering, selecting, retrieving, installing, and correctly styling a component. With list, search, get, install, and design-guide tools, agents have everything needed to integrate appCN components without dead ends.