Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Wireweave is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
MCP server for Wireweave DSL - Thin client for API Server
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user wireweave-mcp '--' npx -y @wireweave/mcp-server
# 2 — ask your agent for something these tools do
# wireweave_parse, wireweave_validate, wireweave_grammar and 34 more
Wireweave costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Wireweave as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user wireweave-mcp '--' npx -y @wireweave/mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
37 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Parse Wireweave DSL source code into an AST (Abstract Syntax Tree)
No parameter schema on file.
Validate Wireweave DSL syntax without generating output. Use strict mode to also check for unknown attributes.
No parameter schema on file.
Get the Wireweave DSL grammar documentation and syntax reference
No parameter schema on file.
Get the comprehensive LLM guide for Wireweave DSL. This is the PRIMARY resource for learning the language - includes syntax, components, patterns, and best practices. Call this FIRST before generating wireframes.
No parameter schema on file.
Get common layout patterns for wireframes including headers, sidebars, forms, cards, and more. Use these as building blocks.
No parameter schema on file.
Get Wireweave code examples. Use this to learn patterns and best practices for different UI types.
No parameter schema on file.
List Wireweave DSL components with their categories, attributes, and examples. Use this to discover available components for wireframe generation. Filter by category (layout, navigation, form, etc.) when narrowing the search.
No parameter schema on file.
Render Wireweave DSL to HTML code. Returns the HTML content directly. This is an alias for wireweave_render_html with explicit naming.
No parameter schema on file.
Validate Wireweave DSL for UX best practices. Returns issues with severity levels and actionable recommendations.
No parameter schema on file.
Get available UX rule categories and their descriptions
No parameter schema on file.
Compare two Wireweave DSL sources and return the differences between them
No parameter schema on file.
Export Wireweave DSL to JSON format
No parameter schema on file.
Export Wireweave DSL to Figma-compatible format
No parameter schema on file.
Analyze Wireweave DSL for statistics and metrics including component usage, tree structure, accessibility score, and complexity
No parameter schema on file.
List all your Wireweave projects. Projects help organize your wireframes. WORKFLOW: Call this first before saving wireframes. If the list is empty, ask the user whether to create a new project (call wireweave_cloud_create_project) or use the default project.
No parameter schema on file.
Create a new project to organize wireframes. Use this when the user wants to organize their wireframes into a specific project. The project can have a custom name, description, and color.
No parameter schema on file.
Update an existing project
No parameter schema on file.
List your saved wireframes. Optionally filter by project or tags.
No parameter schema on file.
Get a specific wireframe by ID, including its code and metadata
No parameter schema on file.
Update an existing wireframe. Creates a new version automatically. Free (v2.0+).
No parameter schema on file.
Delete a wireframe permanently
No parameter schema on file.
Get version history of a wireframe
No parameter schema on file.
Restore a wireframe to a previous version. Free (v2.0+).
No parameter schema on file.
Create a shareable link for a wireframe. Free (v2.0+).
No parameter schema on file.
List share links for a wireframe
No parameter schema on file.
Compare two versions of a wireframe and return the differences. Useful for reviewing changes without loading full code.
No parameter schema on file.
Check your current credit balance and subscription status
No parameter schema on file.
Get detailed subscription information including plan features
No parameter schema on file.
View your credit transaction history
No parameter schema on file.
Get current pricing information for plans, credit packs, and feature costs
No parameter schema on file.
Browse public wireframe gallery for inspiration
No parameter schema on file.
Analyze existing wireframe code and suggest UX improvements based on best practices.
No parameter schema on file.
Wireweave DSL code to analyze
No parameter schema on file.
Convert a UI description or sketch concept into Wireweave DSL code.
No parameter schema on file.
Detailed description of the UI layout and components
No parameter schema on file.
Optional style preference (minimal, detailed, mobile-first)
No parameter schema on file.
Create a new wireframe from a natural language description. Generates Wireweave DSL code.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Wireweave or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.8.2. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Wireweave can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.