Starwind MCP Server

The Starwind UI MCP Server

Local serverstdioTypeScript

What is the Starwind MCP server?

The Starwind UI MCP Server. Exposed over MCP by the starwind mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Select your MCP client and add the Starwind UI server configuration. For the full maintained setup guide, see the Starwind UI MCP Server docs.

The Model Context Protocol (MCP) is a protocol for extending AI capabilities through local servers. This implementation provides Starwind UI-specific tools to enhance AI assistant capabilities when working with Starwind UI. For more information about MCP itself, please visit the official documentation.

  • Live Documentation — - Fetches up-to-date docs from starwind.dev/llms.txt
  • Component Validation — - Validates components against live component metadata with a refreshed fallback list
  • Starwind Search — - Search and discover standard components and Pro blocks by query, category, plan, limit, or offset
  • Compact Tool Surface — - Keeps uncommon or destructive CLI operations as command guidance instead of standalone MCP tools
  • Package Manager Detection — - Auto-detects npm, yarn, or pnpm
  • Caching & Rate Limiting — - Efficient caching with sensible rate limits

Its toolset

Everything the assistant can do here goes through one of these:

  • starwind_init — Generates init commands for new Starwind UI projects, Pro by default
  • 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 Starwind UI components and Starwind Pro blocks with CLI-shaped filters

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

When to reach for it

This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Starwind's toolset — starwind_init, starwind_docs, starwind_add and 1 more — is a fair guide to whether it matches your workflow. It is maintained by chatflowdev; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the starwind mcp server does with a few real requests.

Available tools

ToolWhat it does
starwind_initGenerates init commands for new Starwind UI projects, Pro by default
starwind_docsFetches live documentation from starwind.dev with caching and topic filtering
starwind_addGenerates validated install commands with package manager detection
starwind_searchSearches Starwind UI components and Starwind Pro blocks with CLI-shaped filters

How to install the Starwind MCP server

**Claude Code:**

```json title=".mcp.json"
{
  "mcpServers": {
    "starwind-ui": {
      "command": "npx",
      "args": ["-y", "@starwind-ui/mcp"],
      "env": {}
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Starwind to starwind init.
  • Use Starwind to starwind docs.
  • Use Starwind to starwind add.

Frequently asked questions

It connects Starwind to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (starwind_init, starwind_docs, starwind_add, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Starwind directly.