aura-components-mcp
Related Servers
Alternatives to aura-components-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceEnables agents to search a public skill catalogue, retrieve a skill's install prompt and command, and recommend a free-first skill for a described job while running locally over stdio and remaining read-only.385 npmMIT- AlicenseAqualityCmaintenanceEnables MCP-capable agents to browse a public design-system catalog, retrieve design continuation bundles and sequential prompt packs, import externally designed artifacts, and resume mid-flow external design runs.875 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-aware clients to query and use the you-design catalog of design systems, skills, and plugins at runtime via stdio.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients such as Claude, Claude Code and Cursor to keyword-search a directory of over 1,000 hand-picked productivity tools, apps, AI tools, courses and books, filtering by category, type, pricing and result limit, and to fetch a single listing by slug, page URL or exact name and list all categories with counts. It runs read-only over stdio with no API key, dependencies or tracking, making only a plain GET of the public catalogue.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to search skills.sh, view leaderboards, inspect skill details, retrieve third-party security audits, and browse official curated skills, with install commands for each result.41 npmMIT

plugandship-mcpofficial
AlicenseAqualityCmaintenanceEnables coding agents to search an index of 22k+ MCP servers, agent skills and coding-agent plugins directly from chat, returning matches with stars, install commands and page links, plus trending repos and curated best-of topic lists. Read-only, no API key required, usable via a hosted HTTP endpoint or locally over stdio.4MIT
TDQS
Scored across 35 tools
Four family clusters (aura_inspo_*, aura_award_*, aura_search/get pairs) are mostly distinct, and descriptions do a lot of boundary-setting. However aura_bulk_fetch is an explicit alias of aura_bundle, and install vs scaffold vs use_design_system overlap enough that an agent could misselect. With 35 tools, several boundaries (recommend vs search_all, install_component vs scaffold_page) require careful reading.
Every tool uses the aura_ prefix in lowercase snake_case, with clear verb_noun names (aura_search_components, aura_get_component, aura_install_skill). Minor deviations are noun-only names (aura_status, aura_categories, aura_icon, aura_version) and namespace prefixes (inspo/award/docs), but the convention stays readable and predictable overall.
35 tools is well above the 25+ threshold, and the surface sprawls across roughly a dozen sub-domains (components, skills, assets, systems, awards, motion, docs, inspo, audit). The redundant aura_bundle/aura_bulk_fetch alias confirms some tools do not each earn a distinct place.
Coverage is broad and coherent for a read-only catalog: search+get+install for components/skills/systems/assets, plus aggregators (search_all, recommend, related, bundle), awards, motion, docs, and visual audit. Minor gaps like no dedicated asset detail/detail-get tool exist, but core discovery-to-scaffold workflows are complete.