Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Framework-aware Starwind UI v3 tools for Astro and React setup, components, docs, and migration.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"starwind-ui": {
"command": "npx",
"args": [
"-y",
"@starwind-ui/mcp"
]
}
}
}Run this in your terminal
claude mcp add starwind-ui -- npx -y @starwind-ui/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"starwind-ui": {
"command": "npx",
"args": [
"-y",
"@starwind-ui/mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"starwind-ui": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@starwind-ui/mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account starwind-ui, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.5.1) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Detailing Manager
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Connect your auto detailing studio's tasks, cars, clients and revenue to Claude or ChatGPT.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
For the maintained client setup guide, see the Starwind UI MCP documentation.
Codex (~/.codex/config.toml):
[mcp_servers.starwind_ui]
command = "npx" args = ["-y", "@starwind-ui/mcp"] enabled = true
Claude Code (.mcp.json) or Cursor (.cursor/mcp.json):
{
"mcpServers": { "starwind-ui": { "command": "npx", "args": ["-y", "@starwind-ui/mcp"] } } }
Restart the client or reload its MCP servers after changing the configuration.
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.
| 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.
starwind_init targets existing Astro 5+ or React 18+ projects and lets the CLI auto-detect the framework unless framework is supplied.@starwind-pro/* catalog blocks work after ordinary initialization. Paid blocks require explicit authorization; pass pro: true only when it is required.yes: true only when backup-and-overwrite behavior is intended.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:
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.
pnpm build
pnpm lint pnpm test:run
Run the opt-in production manifest contract test with:
RUN_LIVE_CONTRACT_TESTS=1 pnpm test:run src/utils/starwind_live_contract.test.ts
MIT. See LICENSE.