Extract reusable component libraries and design tokens from Vue applications
MCP server for AI-assisted Vue component extraction and design system analysis. This is the intelligence layer for vue-harvest. It picks up where the CLI leaves off, handling the components in the 30-70% confidence range that need reasoning to extract safely. The server communicates over stdio using the Model Context Protocol. The server exposes 12 tools: ------|-------------| | Runs the full…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
analyze-projectNo description publishedThis tool published no description. Forge does not invent one.
list-componentsNo description publishedThis tool published no description. Forge does not invent one.
inspect-componentNo description publishedThis tool published no description. Forge does not invent one.
extract-componentNo description publishedThis tool published no description. Forge does not invent one.
deep-analyzeNo description publishedThis tool published no description. Forge does not invent one.
suggest-refactorNo description publishedThis tool published no description. Forge does not invent one.
generate-wrapperNo description publishedThis tool published no description. Forge does not invent one.
adapt-and-extractNo description publishedThis tool published no description. Forge does not invent one.
batch-triageNo description publishedThis tool published no description. Forge does not invent one.
coupling-reportNo description publishedThis tool published no description. Forge does not invent one.
analyze-design-systemNo description publishedThis tool published no description. Forge does not invent one.
get-design-tokensNo description publishedThis tool published no description. Forge does not invent one.
analyze-new-projectNo description publishedThis tool published no description. Forge does not invent one.
pathNo description publishedThis tool published no description. Forge does not invent one.
extraction-sprintNo description publishedThis tool published no description. Forge does not invent one.
refactor-componentNo description publishedThis tool published no description. Forge does not invent one.
componentNo description publishedThis tool published no description. Forge does not invent one.
extract-design-systemNo description publishedThis tool published no description. Forge does not invent one.
0 of 18 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for AI-assisted Vue component extraction and design system analysis. This is the intelligence layer for vue-harvest. It picks up where the CLI leaves off, handling the components in the 30-70% confidence range that need reasoning to extract safely. The server communicates over stdio using the Model Context Protocol. The server exposes 12 tools: ------|-------------| | Runs the full vue-harvest pipeline on a project. Required before using other tools. Takes a argument. | | Lists…
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.