Starwind UI MCP Server
Starwind UI v3 MCP server: the agent searches components for Astro and React, reads current docs and prepares install commands
- 35 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The server fetches a manifest and documentation from the Starwind site, and that response should be treated as data
- The migration tool with the yes option backs up and overwrites project files
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/starwind-ui-mcp-serverDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The server fetches a manifest and documentation from the Starwind site, and that response should be treated as data
- The migration tool with the yes option backs up and overwrites project files
This is third-party code. Review the repository files before installing.
What it does
Starwind UI is a component library at version 3 for Astro and React, and Starwind Pro adds paid blocks. The MCP server gives an agent current facts about them so it does not invent component names or cite outdated versions. There are five tools. `starwind_search` finds styled components, primitives and Pro blocks with framework support metadata. `starwind_docs` returns documentation for an exact component, primitive, the Runtime layer, migration or a framework. `starwind_init` builds initialization commands for an existing Astro 5 or React 18 and newer project. `starwind_add` validates a request and outputs install commands for components, primitives or Astro-only Pro blocks. `starwind_migrate` inspects a project and prepares safe, interactive steps for moving from version 2 to version 3. The server checks data against the versioned ai-manifest.json on the Starwind site, caches the validated result and falls back to a bundled version 3 snapshot when the site is unavailable. No tool runs the generated commands itself.
Who it is for. Frontend developers on Astro and React adopting Starwind UI who want Claude Code, Codex or Cursor to install components from current documentation.
Good fit when
- A new Astro project has to be initialized for Starwind UI v3 with the right package manager
- You need a button, dialog or table and the agent picks a matching component in a React or Astro version
- The project is still on version 2 and must move to the third with a backup and confirmations
- You want free Pro blocks and the agent has to show which install without a license
Not a fit when
- The project uses neither Astro nor React: `starwind_init` targets those two frameworks
- You want paid Pro blocks for React: they currently target Astro only, and a React add request is rejected
- The agent must run the installation itself: the tools output commands and do not run them
Example request
Initialize Starwind UI v3 in this Astro project, find the dialog component and show the command to install it.MCP
- Transport
- stdio
- Authentication
- not required
Environment variables
STARWIND_LICENSE_KEYsecret- Starwind Pro license key for paid blocks, set in the project's .env.local
Limitations
The generated version 3 commands need Node.js 22.12.0 or newer. Paid Pro blocks need authorization with a STARWIND_LICENSE_KEY license key, and the pro flag goes in only when required. Free Pro blocks install after ordinary initialization.
Pro blocks currently target Astro. Migration is interactive by default, and the yes option enables overwrite with a backup, so set it only on purpose. Data comes from the manifest on the Starwind site, and the server falls back to a bundled version 3 snapshot when the site is unavailable.
How to disable. Remove the starwind-ui block from .mcp.json, .cursor/mcp.json or ~/.codex/config.toml and restart the client. Components already installed stay in the project as your own code.
FAQ
How do I connect Starwind UI MCP to Claude Code or Cursor?
Add a starwind-ui block with command npx and args -y @starwind-ui/mcp to .mcp.json for Claude Code or .cursor/mcp.json for Cursor. For Codex add an mcp_servers.starwind_ui section with the same command and args to ~/.codex/config.toml. Then restart the client.
What three layers does Starwind UI v3 have?
Styled components you own as a copy in the project, primitives with Astro and React adapters, and Runtime, the framework-neutral behavior APIs. The server gives each layer its own path: search and add, search with surface primitive, and documentation.
Do I need a Pro license?
Free blocks of the @starwind-pro catalog install after ordinary initialization. Paid ones need a license key in STARWIND_LICENSE_KEY. Search results for paid blocks include an upgrade path with purchase and installation links.
What does `starwind_migrate` do?
It inspects the project and outputs safe, interactive steps for moving from version 2 to version 3. The yes option enables backup-and-overwrite mode and should be set only on purpose.
Does the server run the installation itself?
No. The tools return ready commands that account for the detected package manager, and you or the agent decide separately whether to run them.
Discussion
No questions or reviews yet.
Related
MCP serversStarwind UI
starwind-ui
Portable UI components for Astro, React and Vue on Tailwind: the CLI adds the ones you need to the project as source. Version 3.3.2, with agent skills
The Arc UI MCP server: an agent searches animated React components, reads docs and props and gets the shadcn install command.
Chakra UI MCP server: a reference for components, props and theme tokens, plus code review for moving from version 2 to 3
21st.dev MCP server and plugin: search ready React/Tailwind components and logos and generate UI from your agent
MCP server for the UI Beats catalog of animated React components: search, props, source code and install command for an agent
MCP server of a React component library for agent interfaces: the agent finds a component and adds it to your project
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Starwind UI MCP Server (this card) | yes | not required | 35 | |
| Shadcn UI MCP Server | no | key is optional | 3,098 | shadcn/ui components for React and other frameworks |
| Starwind UI | no | 764 | the Starwind command line that carries out installs and migration | |
| daisyUI | no | 42,823 | a Tailwind plugin with component classes |
README in short
The README covers a quick start for Codex, Claude Code and Cursor, the three layers of Starwind UI v3, the tools table, requirements, the upgrade from free to Pro, development commands and the MIT license.