# Starwind UI MCP Server [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/starwind-ui/starwind-ui-mcp  
**GitHub Stars:** 35  
**npm Downloads (last month):** 1005  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/starwind-ui-mcp-server

## Description
Framework-aware Starwind UI v3 tools for Astro and React setup, components, docs, and migration.

## Tools
Capabilities this server exposes over MCP:

- **starwind_init** — Generates a Starwind UI v3 initialization command for an existing Astro or React project. The CLI auto-detects the framework unless an override is provided. Paid Pro authorization is opt-in and currently targets Astro.
- **starwind_add** — Generates validated Starwind UI v3 install commands for styled components, vendored primitives, or Starwind Pro blocks, with optional Astro or React targeting.
- **starwind_search** — Searches Starwind UI v3 styled components, Primitive adapters, and Starwind Pro blocks with framework-aware results.
- **starwind_docs** — Fetches current Starwind UI v3 documentation across styled components, primitives, Runtime, migration, and Astro or React framework guides.
- **starwind_migrate** — Generates the safe Starwind UI v3 migration command for a legacy Astro project. Interactive migration is the default; non-interactive overwrite behavior must be explicitly requested.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "starwind-ui-mcp-server": {
    "command": "npx",
    "args": ["-y","@starwind-ui/mcp"]
  }
}
```

## Documentation

## What Starwind UI MCP Server MCP server does

Starwind UI MCP Server MCP server gives AI clients structured access to Starwind UI v3 and Starwind Pro information for Astro and React projects. Its tools cover project initialization, component and primitive discovery, documentation lookup, component installation command generation, and migration planning from v2 to v3.

The server keeps Starwind UI v3 surfaces separate. Styled components are copy-owned UI pieces with Astro and/or React implementations. Primitives are lower-level framework adapters, with some behavior backed by Starwind Runtime. Runtime APIs provide framework-neutral behavior documentation. This distinction affects which searches, installation commands, and documentation requests are valid.

## How it works

The server checks requests and catalog information against Starwind UI's versioned `ai-manifest.json`. Validated data is cached for reuse. If the remote site cannot be reached, the server uses a bundled v3 snapshot instead.

Tool responses include readable JSON text and MCP `structuredContent`. Generated commands are returned for the client or developer to review; the server does not run them. Local project context and the package manager are detected when possible, and generated add commands pass the resolved package manager to the Starwind CLI.

`starwind_init` targets existing Astro 5+ or React 18+ projects and can detect the framework unless one is supplied. Node.js 22.12.0 or newer is required for the generated v3 CLI commands. Pro behavior is opt-in rather than enabled by default.

## Setup and configuration

Install the server through an MCP client using the npm package command. Codex can define an MCP server whose command is `npx` with arguments `-y` and `@starwind-ui/mcp`. Claude Code and Cursor use the same command in their respective MCP JSON configuration files. Restart or reload the client after changing its configuration.

Starwind UI MCP Server MCP server does not execute initialization or installation output. Review the generated command and run it in the target project when appropriate. For paid Pro blocks, authorization is required. In an existing Astro project, the returned setup flow prepares the Pro registry and `.env.local`; the purchased `STARWIND_LICENSE_KEY` must replace the placeholder and remain out of source control, logs, and client-side code.

## Tools and capabilities

- `starwind_init`: Generates v3 initialization commands for an existing Astro or React project, with optional Pro setup.
- `starwind_add`: Validates requests and creates installation or deferred-install commands for styled components, primitives, and Astro-only Pro blocks.
- `starwind_search`: Finds styled components, primitives, and Pro blocks using framework metadata and filters.
- `starwind_docs`: Retrieves exact component, primitive, Runtime, migration, and framework documentation.
- `starwind_migrate`: Inspects a project and creates interactive-first v2-to-v3 migration guidance.

React searches exclude Pro blocks because those blocks currently target Astro. React add requests for Pro blocks are rejected. Free `@starwind-pro/*` catalog blocks can be installed after ordinary initialization, while paid blocks expose structured upgrade information and require explicit authorization.

## Limitations and notes

Migration is interactive by default. Set `yes: true` only when backup-and-overwrite behavior is intended. The tools generate commands but do not execute them, so project changes remain under the developer's control. The server supports the Starwind UI v3 model and its documented Astro, React, Runtime, migration, and Pro distinctions; requests outside those surfaces may be rejected during validation.

The project is licensed under MIT. Development commands listed by the project include `pnpm build`, `pnpm lint`, and `pnpm test:run`.

_Full upstream README: https://allmcps.com/mcp/starwind-ui-mcp-server/readme_