Starwind UI MCP Server

io.github.starwind-uiPublished by GitHub account starwind-uiv0.5.1Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Starwind UI MCP server that gives AI assistants framework-aware guidance for Astro and React projects using Starwind UI v3 components, primitives, docs and…

What you can do
  • Search styled components, primitives and Pro blocks with framework metadata and filters
  • Generate initialization and component installation commands for Astro or React projects
  • Resolve exact component, primitive, Runtime, migration and framework documentation
  • Inspect a project and produce interactive-first v2-to-v3 migration guidance
  • Return readable JSON plus structured content for each tool call
When to use it
Useful when building or maintaining an Astro or React project with Starwind UI v3 and you want the assistant to look up current components, docs and setup or migration commands instead of guessing. Also handy for planning a v2-to-v3 upgrade.
Requirements
Runs locally over stdio, typically launched with npx from the @starwind-ui/mcp npm package; no authentication or environment variables are declared. Generated v3 CLI commands need Node.js 22.12.0 or newer, and init targets existing Astro 5+ or React 18+ projects. Paid Pro blocks require a purchased license key placed in .env.local.
Before you install
The server only generates commands and does not execute them, so review before running. Migration is interactive by default; setting yes: true enables backup-and-overwrite behavior. Paid Pro blocks need explicit authorization and a purchase; the STARWIND_LICENSE_KEY is sensitive and should stay out of source control, logs and client-side code. Pro blocks currently target Astro only.

Installation

In SourceWeft

  1. Open Starwind UI MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Starwind UI MCP Server]

[npm] [GitHub stars]

Official MCP Registry · io.github.starwind-ui/mcp

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.

Quick start

For the maintained client setup guide, see the Starwind UI MCP documentation.

Codex (~/.codex/config.toml):

toml
[mcp_servers.starwind_ui]command = "npx"args = ["-y", "@starwind-ui/mcp"]enabled = true

Claude Code (.mcp.json) or Cursor (.cursor/mcp.json):

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

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:

SurfaceWhat it representsMCP behavior
Styled componentsCopy-owned UI components with Astro and/or React implementationsSearch and install with starwind_search and starwind_add
PrimitivesLower-level Astro and React adapters, backed by Starwind Runtime where applicableSearch with surface: "primitive"; install with the v3 primitives add command
RuntimeFramework-neutral behavior APIsFetch 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

ToolPurpose
starwind_initGenerate v3 initialization commands for an existing Astro or React project. Pro is opt-in.
starwind_addValidate requests and generate installation or deferred-install commands for styled components, primitives, or Astro-only Pro blocks.
starwind_searchSearch styled components, primitives, and Pro blocks with framework metadata and filters.
starwind_docsResolve exact component, primitive, Runtime, migration, and framework documentation.
starwind_migrateInspect 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 buildpnpm lintpnpm test:run

Run the opt-in production manifest contract test with:

bash
RUN_LIVE_CONTRACT_TESTS=1 pnpm test:run src/utils/starwind_live_contract.test.ts

License

MIT. See LICENSE.

Security

[MseeP.ai Security Assessment Badge]

Source: README.md at commit 01986a9

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.5.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts