@vizejs/musea-mcp-server
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 1 of 4 tools tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @vizejs/musea-mcp-server@0.765.0
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
4 tools that take no input and look read-only were called once with nothing. 1 returned a result.
get_palette | No usable answer MCP error -32602: Provide one of: path, title, component, query, or ref |
list_components | Returned a result under 0.1 s · 2 characters |
get_component | No usable answer MCP error -32602: Provide one of: path, title, component, query, or ref |
get_tokens | No usable answer MCP error -32602: No tokens path provided and none auto-detected. Looked for: tokens/, design-tokens/, style-dictionary/ directories. |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
analyze_component path, title, component, query, ref
Statically 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_palette path, title, component, query, ref
Derive 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_components category, tag, status, component, limit, includeVariants, sortBy
List components registered in the design system. Returns titles, categories, tags, status, variant names, and related resource URIs.
get_component path, title, component, query, ref, includeAnalysis, includePalette, includeDocumentation
Get full details of a design-system component: metadata, variants, source-component analysis, palette data, documentation, and related resource URIs.
get_variant path, title, component, query, ref, variant, includeAnalysis
Retrieve a single variant (template and metadata) from a component, resolving the component by path, title, component name, or fuzzy query.
8 more tools
search_components query, category, tag, status, component, limit
Ranked full-text search over component titles, descriptions, categories, tags, component names, and variant names.
recommend_components task, category, tag, status, component, limit
Intent-oriented component recommendation. Useful when the user describes a task or UX goal rather than knowing exact component names.
generate_variants componentPath, maxVariants, includeDefault, includeBooleanToggles, includeEnumVariants
Analyze a Vue component's props and auto-generate an .art.vue file containing appropriate variant combinations (default, boolean toggles, enum values, etc.).
generate_csf path, title, component, query, ref
Convert an .art.vue file into Storybook CSF 3.0 code for integration with existing Storybook setups.
generate_docs path, title, component, query, ref, includeSource, includeTemplates
Generate Markdown documentation for a design-system component from its .art.vue definition.
generate_catalog includeSource, includeTemplates
Produce a single Markdown catalog covering every component in the design system, grouped by category.
get_tokens tokensPath, format
Read design tokens (colors, spacing, typography, etc.) from a Style Dictionary-compatible JSON file or directory. Auto-detects common paths if not specified.
search_tokens query, tokensPath, type, limit
Search flattened design tokens by token name, category path, value, or description. Much more practical than loading the full token tree for large systems.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=22 |
| Source | github.com/ubugeeei-prod/vize |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-mX/D21ZYtCqf8KDEWXN/N8hNPzBjnMTXjuFDs/5wiP/8q3F/BTTB+91rFKTHFCnHkNKh2mb327q2lrzJRXTzMg== |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 0.765.0 | 2026-11-16 | Starts with no setup | 13 |
| 0.751.0 | 2026-11-12 | Starts with no setup | 13 |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40vizejs/musea-mcp-server)
New version out? Ask for a fresh report.