All servers / Design / Musea MCP server
Musea MCP server
MCP server for building Vue.js design systems - component analysis, documentation, variant generation, and design tokens
Tested by ConnectATDScore 94 out of 100. Tested 2026-11-18 on package version 0.781.0. Package: @vizejs/musea-mcp-server · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 16 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (8.0 seconds including download)
- Tools offered: 13
- Last published: 2026-11-18
- Weekly downloads (npm): 10,303
- License: MIT · Direct dependencies: 4
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
analyze_component5 of 5 parameters describedStatically analyze a Vue SFC to extract its props and emits. Accepts a Vue component path directly, or an art-file reference that resolves to the linked component source.
get_palette5 of 5 parameters describedDerive an interactive props palette (control types, defaults, ranges, options) for a component described by an Art file. Falls back to SFC analysis when native palette inference is sparse.
list_components7 of 7 parameters describedList components registered in the design system. Returns titles, categories, tags, status, variant names, and related resource URIs.
get_component8 of 8 parameters describedGet full details of a design-system component: metadata, variants, source-component analysis, palette data, documentation, and related resource URIs.
get_variant7 of 7 parameters describedRetrieve a single variant (template and metadata) from a component, resolving the component by path, title, component name, or fuzzy query.
search_components6 of 6 parameters describedRanked full-text search over component titles, descriptions, categories, tags, component names, and variant names.
recommend_components6 of 6 parameters describedIntent-oriented component recommendation. Useful when the user describes a task or UX goal rather than knowing exact component names.
generate_variants5 of 5 parameters describedAnalyze a Vue component's props and auto-generate an .art.vue file containing appropriate variant combinations (default, boolean toggles, enum values, etc.).
generate_csf5 of 5 parameters describedConvert an .art.vue file into Storybook CSF 3.0 code for integration with existing Storybook setups.
generate_docs7 of 7 parameters describedGenerate Markdown documentation for a design-system component from its .art.vue definition.
generate_catalog2 of 2 parameters describedProduce a single Markdown catalog covering every component in the design system, grouped by category.
get_tokens2 of 2 parameters describedRead design tokens (colors, spacing, typography, etc.) from a Style Dictionary-compatible JSON file or directory. Auto-detects common paths if not specified.
search_tokens4 of 4 parameters describedSearch flattened design tokens by token name, category path, value, or description. Much more practical than loading the full token tree for large systems.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.