Framework-aware Starwind UI v3 tools for Astro and React setup, components, docs, and migration.
io.github.starwind-ui/mcp — Model Context Protocol (MCP) Server
The io.github.starwind-ui/mcp server provides framework-aware Starwind UI v3 tools focused on Astro and React setup, including components, documentation, and migration support. It is described as a Model Context Protocol server (mcp-server) for developers using the model context protocol.
🛠️ Key Features
Starwind UI v3 tooling
Astro and React setup support
Components, docs, and migration tooling
MCP server packaging for use with Model Context Protocol
🚀 Use Cases
Set up Starwind UI v3 in Astro or React projects
Retrieve component-related resources for implementation
Follow or reference Starwind UI documentation
Migrate to Starwind UI v3 with provided migration tooling
⚡ Developer Benefits
Uses Model Context Protocol server integration (mcp, mcp-server)
TypeScript-oriented ecosystem alignment
Developer tools oriented toward coding agents and agent workflows
⚠️ Limitations
Scope is specifically tied to Starwind UI v3 and Astro/React
No additional tooling counts or capabilities beyond the excerpted areas are provided
A TypeScript Model Context Protocol server for Starwind UI v3 and Starwind Pro. It gives AI clients current, framework-aware guidance for Astro and React projects.
Restart the client or reload its MCP servers after changing the configuration.
v3 model
Starwind UI v3 has three related surfaces. The MCP keeps them distinct:
Surface
What it represents
MCP behavior
Styled components
Copy-owned UI components with Astro and/or React implementations
Search and install with starwind_search and starwind_add
Primitives
Lower-level Astro and React adapters, backed by Starwind Runtime where applicable
Search with surface: "primitive"; install with the v3 primitives add command
Runtime
Framework-neutral behavior APIs
Fetch with starwind_docs using the Runtime topic or surface
The server validates these layers against the versioned ai-manifest.json, caches validated data, and falls back to a bundled v3 snapshot if the site is unavailable.
Tools
Tool
Purpose
starwind_init
Generate v3 initialization commands for an existing Astro or React project. Pro is opt-in.
starwind_add
Validate requests and generate installation or deferred-install commands for styled components, primitives, or Astro-only Pro blocks.
starwind_search
Search styled components, primitives, and Pro blocks with framework metadata and filters.
starwind_docs
Resolve exact component, primitive, Runtime, migration, and framework documentation.
starwind_migrate
Inspect a project and generate safe, interactive-first v2-to-v3 migration guidance.
Tool calls return both readable JSON text and MCP structuredContent.
Requirements and behavior
Generated v3 CLI commands require Node.js 22.12.0 or newer.
starwind_init targets existing Astro 5+ or React 18+ projects and lets the CLI auto-detect the framework unless framework is supplied.
Free @starwind-pro/* catalog blocks work after ordinary initialization. Paid blocks require explicit authorization; pass pro: true only when it is required.
Starwind Pro blocks currently target Astro. React searches omit them, and React add requests reject them explicitly.
Migration is interactive by default. Set yes: true only when backup-and-overwrite behavior is intended.
Package-manager and project context are detected locally when possible, and add commands pass the resolved package manager to the CLI. No tool executes the generated command.
Upgrading from free to Pro
The MCP keeps Pro discoverable without forcing paid setup. Search results link to the Pro catalog, free Pro blocks remain directly installable, and paid results include a structured proUpgrade path with purchase and installation links.
For an existing Astro project, the MCP recommends:
bash
pnpm dlx starwind@latest setup --yes
The setup command auto-detects the project's package manager, so it does not need a --package-manager flag. It prepares the Pro registry and .env.local; replace the STARWIND_LICENSE_KEY placeholder with the purchased key, then run the returned deferredCommand. Treat the key as sensitive: keep .env.local out of source control and never expose the key in logs or client-side code. A project initialized with pro: true receives the equivalent init --pro command instead.
Development
bash
pnpm build
pnpm lint
pnpm test:run
Run the opt-in production manifest contract test with:
