Integrate Starwind UI with AI Code Assistants

Starwind UI MCP Server is a TypeScript MCP server for Starwind UI and Starwind Pro (Astro component libraries), giving AI coding tools like Codex, Claude Code, and Cursor a compact, intent-based set of four tools rather than a wrapper for every CLI command. starwind_init generates init commands for new Starwind UI projects, defaulting to Pro. starwind_docs fetches live documentation from starwind.dev with caching and topic filtering. starwind_add generates validated install commands with package manager detection. starwind_search searches standard Starwind UI components and Starwind Pro blocks with CLI-shaped filters, returning grouped standard-component and Pro-block results, with Pro block results filterable by plan, category, limit, and offset. The server deliberately does not expose standalone tools for less common or destructive CLI operations like setup, update, or remove - for Starwind Pro setup on an already-initialized project, it instead returns the guidance command starwind@latest setup --yes via starwind_add or starwind_search, while a brand-new Pro project uses starwind@latest init --defaults --pro via starwind_init. Supporting features: live documentation pulled from starwind.dev's llms.txt, component validation against live component metadata with a refreshed fallback list if that's unavailable, automatic detection of npm/yarn/pnpm as the project's package manager, and caching with sensible rate limits to keep repeated documentation and search calls efficient.

Use it when building an Astro project with Starwind UI or Starwind Pro and want an AI coding assistant to initialize a project, generate correct install commands for a component, search available components and Pro blocks, or pull current documentation - all matched to the project's actual package manager. It's scoped specifically to Starwind UI/Pro on Astro, not a general component-library or framework-agnostic UI tool, and it won't run less-common CLI operations like update or remove directly - those come back as guidance commands to run yourself.

Input is a project-initialization request, a component or Pro block name to install, a search query with optional plan/category/limit/offset filters, or a documentation topic. Output is a validated, package-manager-correct command to run, live documentation content, or grouped search results across standard components and Pro blocks.

Configured via each client's own MCP config - ~/.codex/config.toml for Codex, .mcp.json for Claude Code, .cursor/mcp.json for Cursor - all launching the server the same way:

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

Astro developers using Starwind UI or Starwind Pro who want their AI coding assistant to generate correct, package-manager-aware install commands and search or pull documentation automatically, without memorizing the Starwind CLI or manually checking the docs site.