starwind-ui/starwind-ui-mcp

Codex: add [mcp_servers.starwind_ui] with command "npx", args ["-y", "@starwind-ui/mcp"] to ~/.codex/config.toml
Claude Code (.mcp.json) or Cursor (.cursor/mcp.json): mcpServers starwind-ui with command npx and args ["-y", "@starwind-ui/mcp"]

Usage

• •Call starwind_search to find styled components, primitives, or Pro blocks with framework metadata and filters; starwind_add generates install or deferred-install commands.
• •starwind_init targets existing Astro 5+ or React 18+ projects and lets the CLI auto-detect the framework.
• •Pro is opt-in: pass pro:true only when required; paid results include a structured proUpgrade path.
• •Migration (starwind_migrate) is interactive by default — set yes:true only when backup-and-overwrite is intended.

Key features

• ✓Distinguishes the three v3 surfaces: styled components, primitives, and Runtime behavior APIs.
• ✓Validates tool responses against the versioned ai-manifest.json, caches validated data, and falls back to a bundled v3 snapshot if the site is unavailable.
• ✓Tool calls return both readable JSON text and MCP structuredContent.
• ✓Detects package manager and project context locally; no tool ever executes the generated command.
• ✓Free @starwind-pro/* catalog blocks work after ordinary initialization.

Best for

Astro/React developers using Starwind UI v3 (or migrating from v2) whose AI agents need current component install, docs, and upgrade guidance.

Caveats

• ⚠Generated v3 CLI commands require Node.js 22.12.0 or newer.
• ⚠Starwind Pro blocks currently target Astro only — React searches omit them and add requests reject them explicitly.
• ⚠Paid Pro blocks require explicit authorization and a STARWIND_LICENSE_KEY (keep .env.local out of source control).
• ⚠Migration with yes:true performs backup-and-overwrite behavior.