
Vize Musea MCP Server: Setup for Claude, Cursor and Other Apps
Lets Claude, Cursor and other assistants look up your Vue components, props, variants and design tokens in Vize Musea.
This is the Vize project's own server for Musea, its Vue component gallery. Your assistant can list and search your components, read props and variants, recommend a component for a task, read design tokens, and draft variants, Storybook stories and docs.
It runs on your computer against one project folder and needs Node.js 22 or newer. The README installs it with Vite+ (the vp command). Vize describes itself as experimental, so expect changes.
Good for
- Vue developers who use Vize and its Musea component gallery
- Design system teams who keep components and tokens in one project
- Front-end developers who want an assistant to pick real components instead of inventing them
Works in
12 should work
Tap an app to see how to set it up and any known problems.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Client does not support this transport.
Client does not support this transport.
Install vize MCP
Claude Code
- 1
Copy this prompt.
Add the vize MCP server to Claude Code. Run this command: claude mcp add musea -- /absolute/path/to/vp -C /absolute/path/to/project exec musea-mcp /absolute/path/to/project Then check that it loaded and tell me if I need to sign in or restart.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires Node.js 22+, Vite+ (vp) installed, vp install -D @vizejs/musea-mcp-server in the project.
Install Vite+ once, then run vp install -D @vizejs/musea-mcp-server in your Vue project. Replace both /absolute/path entries with real paths. The Claude Desktop config is the Vize README's example, and the configs for other apps are adapted from it by PlugWiki.
Built from the package data we hold. Not yet tested by us.
Tools
Lists the components in your design system
Returns each registered component with its title, category, tags, status, variant names and resource links.
Try: “List the components in our design system.”
Files ·
list_componentsSearches components by text
Ranks components by how well their titles, descriptions, categories, tags, names and variants match your words.
Try: “Find components related to date pickers.”
Files ·
search_componentsSuggests components for a task
Picks components that fit a goal you describe, when you do not know their names.
Try: “Which components should I use for a settings form?”
Files ·
recommend_componentsGets everything about one component
Returns a component's details, variants, props analysis, palette data, docs and related links.
Try: “Show me the Button component with all its variants.”
Files ·
get_componentGets one variant of a component
Returns one variant's template and details. You can find the component by path, title, name or a fuzzy search.
Try: “Show the disabled variant of Button.”
Files ·
get_variantLists a component's props and events
Reads a Vue single-file component and extracts the props and emitted events, from a path or an art file reference.
Try: “What props and events does Modal.vue have?”
Files ·
analyze_componentShows controls for trying out a component's props
Works out the control type, default, range and options for each prop of a component from its art file.
Try: “Which controls should the Button playground offer?”
Files ·
get_paletteDrafts an art file with variants
Reads a component's props and returns a draft .art.vue file with sensible variants, such as default, boolean toggles and enum values.
Try: “Draft variants for the Badge component.”
Files ·
generate_variantsConverts an art file to Storybook code
Turns an .art.vue file into Storybook CSF 3.0 code for an existing Storybook setup.
Try: “Convert Button.art.vue to Storybook stories.”
Files ·
generate_csfWrites Markdown docs for a component
Builds Markdown documentation for a component from its art file.
Try: “Write docs for the Card component.”
Files ·
generate_docsBuilds a catalog of all components
Produces one Markdown catalog covering every component, grouped by category.
Try: “Make a catalog of our design system.”
Files ·
generate_catalogReads design tokens
Reads colors, spacing, type and other tokens from a Style Dictionary compatible JSON file or folder, and finds common paths if you give none.
Try: “What color tokens do we have?”
Files ·
get_tokensSearches design tokens
Searches tokens by name, category path, value or description, which is lighter than loading the whole token tree.
Try: “Find tokens with the value #0a5.”
Files ·
search_tokens
Read from the source code
Permissions
low risk · 2 things to watch
Low risk
The 13 tools only read your project files and return text, so the risk is low. Point it at the project folder you want shared with the assistant, because tokens and component source go to your AI app.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
It reads files in your project
The tools read component, art and token files under the project root you give. The generate tools return content and do not write files in the version checked. npmjs.com
Vize is experimental
The Vize README warns of breaking changes and behavior that differs from Vue. Pin the package version if you rely on it. github.com
Security advisories
No published security advisories as of Nov 1, 2026.
Technical details
| Sign-in and keys | No sign-in or API key. |
|---|
Questions
Is the Vize Musea MCP server official?
Yes. It is published by the Vize project as part of its Musea component gallery.
What do I need before I install it?
Node.js 22 or newer, a Vue project that uses Musea, and Vite+ (the vp command), which the README uses to install and run it. Install the package in the project first.
Why does the config need absolute paths?
The README says to use absolute paths for the vp program and the project, so the app can start the server from anywhere.
Can it change my files?
No tool in the published package writes files. The generate tools return drafts of art files, stories and docs as text for you to save.
Does it need an API key?
No. It runs locally against your project folder with no sign-in.
How do I point it at my design tokens?
Pass a tokens path option or set MUSEA_TOKENS_PATH. If you give none, it looks in common places.
Information
updated Nov 2, 2026
- Publisher
- Official
- Package
@vizejs/musea-mcp-server- Registry
- npm
- Transport
- stdio
- Auth
- None
- Version
- 0.614.0
- License
- MIT
- Last commit
- Oct 31, 2026
- Open issues
- 107
Sources
Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.
Show all 2Hide
- www.npmjs.com · npmjs.com
- github.com · github.com