starwind_initLABSCO SUMMARY
Keeps an assistant from writing Starwind code out of date: docs come from the live site, install commands from your actual project.
The distinction it enforces is the one people get wrong — styled components, primitives and Runtime are separate surfaces with separate install paths, and the server answers per surface instead of blurring them. Nothing is executed for you: you get the command with the right package manager filled in and run it yourself.
What it is
A server for Starwind UI v3 and Starwind Pro that keeps the library's three surfaces — styled components, primitives and the Runtime — distinct, and validates every answer against the site's versioned AI manifest.
What you get
- Live documentation pulled from starwind.dev — component and primitive pages, Runtime APIs, theming, installation and migration
- Search across styled components, primitives and Pro blocks, with framework metadata and Pro plan and category filters, paginated
- The correct installation command for the components you name, built for the package manager detected in your project
- Initialization commands for an existing Astro or React project, with Pro opt-in rather than assumed
- Migration guidance from v2 to v3 that inspects the project first and stays interactive unless you say otherwise
- Answers validated against the versioned ai-manifest.json and cached, falling back to a bundled v3 snapshot when the site is unreachable
- Both readable JSON and structured content on every call, and no tool ever executes the command it generates
Requirements
Nothing to authorize for the free catalogue. Runs from npm as @starwind-ui/mcp over stdio. The CLI commands it generates need Node.js 22.12.0 or newer, and initialization targets an existing Astro 5+ or React 18+ project. Paid Pro blocks need a licence key in .env.local, which the setup command scaffolds; free Pro catalogue blocks install without one. Pro blocks currently target Astro — React searches leave them out and React installs reject them.
Setup effort
One command — npx -y @starwind-ui/mcp
USE CASES
01
Adding a component without guessing the API
Search for it, read its current documentation, then get the install command for your package manager.
02
Starting Starwind in a project you already have
Generate the initialization command for the existing Astro or React app, with Pro left off unless you ask for it.
03
Moving a project from v2 to v3
Have the project inspected and get step-by-step migration guidance that stays interactive by default.
04
Working out which surface a piece of behaviour belongs to
Search primitives specifically, or fetch the Runtime documentation, instead of assuming it is a styled component.
05
Deciding whether a Pro block is worth it
Search the catalogue with the plan filters — free blocks install directly, paid results come back with the upgrade path attached.
5 tools
Listed in project docs. Your client may show a different list.
starwind_addstarwind_searchstarwind_docsstarwind_migrateBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation. starwind_migrate, the v2-to-v3 migration tool, did not register on a default launch; the documentation does not say what enables it.
Requires
npx on PATH
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @starwind-ui/mcpMCP Clients
Codex
CODEX · TOML
[mcp_servers.starwind_ui]
command = "npx"
args = ["-y", "@starwind-ui/mcp"]
enabled = trueClaude Code, Cursor
JSON
{
"mcpServers": {
"starwind-ui": {
"command": "npx",
"args": [
"-y",
"@starwind-ui/mcp"
]
}
}
}
