de en es ja ko ru zh

Starwind UI MCP Server

Name: Starwind UI MCP Server
Author: starwind-ui

by starwind-ui

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Starwind UI v3 および Starwind Pro のためのTypeScript Model Context Protocolサーバーです。AIクライアントに対して、AstroおよびReactプロジェクト向けの現在のフレームワーク対応ガイダンスを提供します。

クイックスタート

メンテナンスされているクライアントセットアップガイドについては、Starwind UI MCP ドキュメントを参照してください。

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

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

Claude Code (.mcp.json) または Cursor (.cursor/mcp.json):

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

設定を変更した後は、クライアントを再起動するか、MCPサーバーをリロードしてください。

Related MCP server: shadcn-ui MCP Server

v3モデル

Starwind UI v3には3つの関連するサーフェスがあります。MCPはそれらを区別します：

サーフェス	意味	MCPの動作
Styled components	Astroおよび/またはReactの実装を持つコピー所有のUIコンポーネント	`starwind_search` と `starwind_add` で検索およびインストール
Primitives	低レベルのAstroおよびReactアダプター。該当する場合はStarwind Runtimeをバックエンドとする	`surface: "primitive"` で検索。v3の `primitives add` コマンドでインストール
Runtime	フレームワークに依存しない動作API	Runtimeトピックまたはサーフェスを使用して `starwind_docs` で取得

サーバーはこれらのレイヤーをバージョン管理された ai-manifest.json に対して検証し、検証済みデータをキャッシュします。サイトが利用できない場合は、バンドルされたv3スナップショットにフォールバックします。

ツール

ツール	目的
`starwind_init`	既存のAstroまたはReactプロジェクト向けにv3初期化コマンドを生成します。Proはオプトインです。
`starwind_add`	リクエストを検証し、styled components、primitives、またはAstro専用Proブロックのインストールまたは遅延インストールコマンドを生成します。
`starwind_search`	フレームワークメタデータとフィルターを使用して、styled components、primitives、およびProブロックを検索します。
`starwind_docs`	正確なコンポーネント、primitive、Runtime、移行、およびフレームワークのドキュメントを解決します。
`starwind_migrate`	プロジェクトを検査し、安全でインタラクティブを優先したv2からv3への移行ガイダンスを生成します。

ツール呼び出しは、読み取り可能なJSONテキストとMCP structuredContent の両方を返します。

要件と動作

生成されたv3 CLIコマンドにはNode.js 22.12.0以降が必要です。
starwind_init は既存のAstro 5+またはReact 18+プロジェクトを対象としており、framework が指定されない限りCLIがフレームワークを自動検出します。
無料の @starwind-pro/* カタログブロックは、通常の初期化後に動作します。有料ブロックには明示的な承認が必要です。pro: true は必要な場合にのみ渡してください。
Starwind Proブロックは現在Astroを対象としています。React検索ではそれらが除外され、React追加リクエストでは明示的に拒否されます。
移行はデフォルトでインタラクティブです。yes: true は、バックアップして上書きする動作が意図されている場合にのみ設定してください。
パッケージマネージャーとプロジェクトのコンテキストは、可能な場合はローカルで検出され、addコマンドは解決されたパッケージマネージャーをCLIに渡します。どのツールも生成されたコマンドを実行しません。

無料版からProへのアップグレード

MCPは、有料セットアップを強制することなくProを発見可能に保ちます。検索結果はProカタログにリンクし、無料のProブロックは直接インストール可能なままです。有料の結果には、購入およびインストールリンクを含む構造化された proUpgrade パスが含まれます。

既存のAstroプロジェクトの場合、MCPは以下を推奨します：

pnpm dlx starwind@latest setup --yes

セットアップコマンドはプロジェクトのパッケージマネージャーを自動検出するため、--package-manager フラグは必要ありません。これによりProレジストリと .env.local が準備されます。STARWIND_LICENSE_KEY プレースホルダーを購入したキーに置き換え、返された deferredCommand を実行してください。このキーは機密情報として扱ってください。.env.local をソース管理から除外し、キーをログやクライアント側コードに決して公開しないでください。pro: true で初期化されたプロジェクトは、代わりに同等の init --pro コマンドを受け取ります。

開発

pnpm build
pnpm lint
pnpm test:run

オプトインのプロダクションマニフェストコントラクトテストを実行するには：

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

ライセンス

MIT。LICENSE を参照してください。

セキュリティ

Available Tools

5 tools

starwind_addA

Generates validated Starwind UI v3 install commands for styled components, vendored primitives, or Starwind Pro blocks, with optional Astro or React targeting.

ParametersJSON Schema

Name	Required	Description
`to`	No	Primitive destination passed to --to.
`cwd`	No
`pro`	No	Configure paid Pro authorization during optional init.
`init`	No	Prepend project initialization for a new setup.
`surface`	No	Defaults to styled.
`framework`	No	Optional framework override.
`overwrite`	No	Allow the CLI to overwrite existing files.
`components`	Yes	Names to install, or a single 'all'/'--all' item.
`packageManager`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes	Structured Starwind installation result.

TDQS

A3.5/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must fully disclose behavior. It states 'generates validated... commands' but does not clarify whether the tool only outputs commands or also executes them. Parameters like 'init' and 'overwrite' suggest potential side effects, yet the description omits any discussion of safety, authentication, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that efficiently conveys the core purpose without unnecessary words. Every element earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 9 parameters and an output schema. While the description covers the high-level purpose, it lacks details on parameter relationships, the fact that 'components' can be 'all', and whether the tool executes commands or just generates them. The output schema exists, so return values are not missing, but the behavioral and contextual gaps reduce completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 78%, so the schema already documents most parameters. The description adds no additional meaning beyond the schema. Baseline 3 is appropriate as the description does not improve understanding of the two undocumented parameters (cwd, packageManager).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('generates') and resource ('validated Starwind UI v3 install commands') and clearly distinguishes from siblings like starwind_init (initialization) and starwind_search (search) by focusing on component installation with optional framework targeting.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for adding components after setup, but does not explicitly state when to use this tool versus starwind_init or starwind_migrate. No when-not-to-use or alternative guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

starwind_docsB

Fetches current Starwind UI v3 documentation across styled components, primitives, Runtime, migration, and Astro or React framework guides.

ParametersJSON Schema

Name	Required	Description
`full`	No	Use the full aggregate reference when no exact page is found.
`topic`	No
`surface`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes	Structured Starwind documentation result.

TDQS

B3.4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full responsibility for behavioral disclosure. The word 'Fetches' implies a safe, read-only operation, but the description does not explicitly state that it produces no side effects, requires authentication, or has any rate limits. This is adequate but lacks the explicitness needed for agents to confidently assess risk.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, focused sentence that leads with the verb 'Fetches' and immediately conveys the resource. It packs multiple categories without wasted words. While slightly long due to enumeration, every clause adds relevant scope. No unnecessary repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema (so return values need not be detailed) and the absence of annotations, the description covers the tool's scope adequately. However, it omits guidance on how the 'full' parameter differs from a non-full request, when to use different surfaces, and how to combine parameters effectively. The context is sufficient for basic use but lacks depth for complex queries.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is low (33%: only the 'full' parameter has a description). The description adds contextual meaning by enumerating categories that align with the 'surface' enum values, helping an agent understand what each surface likely refers to. However, 'topic' remains entirely undefined, and the relationship between 'topic' and 'surface' is not clarified. The description partially compensates for the schema gap but leaves ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Fetches'), the resource ('current Starwind UI v3 documentation'), and the scope across multiple categories (styled components, primitives, Runtime, migration, framework guides). This sharply distinguishes it from sibling tools like starwind_init, starwind_add, starwind_search, or starwind_migrate, which serve different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus the sibling tool starwind_search, or when to avoid it. It lists what the tool fetches but does not explain prerequisites, exclusion criteria, or the relationship between the surface enum values and the listed categories. An agent must guess the intended usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

starwind_initA

Generates a Starwind UI v3 initialization command for an existing Astro or React project. The CLI auto-detects the framework unless an override is provided. Paid Pro authorization is opt-in and currently targets Astro.

ParametersJSON Schema

Name	Required	Description
`cwd`	No	Project directory used for package manager and framework detection.
`pro`	No	Configure paid Starwind Pro authorization. Defaults to false.
`framework`	No	Optional CLI framework override.
`packageManager`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes	Structured Starwind initialization result.

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It discloses that the tool generates a command (not directly modifying anything), mentions auto-detection behavior, and notes Pro is opt-in targeting Astro. This is strong coverage of behavioral effects, missing only potential side effects or return format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler. Front-loaded with the core action, then specifics on auto-detection and Pro. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists (not shown but flagged as present), the description does not need to detail return values. It covers generation scope, framework detection, and Pro behavior. Completeness is high; minor gap could be a note that this does not install dependencies or modify files directly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 75% (3 of 4 parameters described). The description adds context that 'pro' is opt-in and targets Astro, and that 'framework' override is optional. The 'packageManager' parameter lacks any description enrichment, but the overall additive value is moderate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool generates a Starwind UI v3 initialization command for existing Astro or React projects. This specific verb+resource combination clearly distinguishes it from siblings like 'starwind_add', 'starwind_search', 'starwind_docs', and 'starwind_migrate'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions CLI auto-detects the framework unless overridden, and that Pro authorization is opt-in targeting Astro. This provides clear context for when to override vs. not, though it does not explicitly state when this tool is preferred over siblings or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

starwind_migrateB

Generates the safe Starwind UI v3 migration command for a legacy Astro project. Interactive migration is the default; non-interactive overwrite behavior must be explicitly requested.

ParametersJSON Schema

Name	Required	Description
`cwd`	No	Legacy Starwind project directory to inspect.
`yes`	No	Add --yes to create a backup and overwrite registered conflicts without prompts.
`packageManager`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes	Structured Starwind migration guidance.

TDQS

B3.3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full weight for behavioral disclosure. It reveals that the tool has interactive and non-interactive modes, but omits critical details: what 'safe' means, whether it actually executes migration or just prints a command, what happens during overwrite (backup? destructive?), and any permission or side-effect notifications. Given the complexity of migration, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose. Every word earns its place. No fluff or redundancy. The structure efficiently communicates the core action and key behavioral choice.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite an output schema being present, the description leaves major ambiguities: does the tool execute migration or just output a command? How does the packageManager parameter affect behavior? What is the interactive workflow? The description is too sparse for an agent to reliably invoke the tool, especially given the absence of annotations to provide safety cues.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 67% (cwd and yes have descriptions, packageManager does not). The main description adds no parameter information beyond the schema. For packageManager, there is no description in either the schema or the description, leaving the agent unaware of its role. The description fails to compensate for the missing parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool generates a migration command for a specific context ('Starwind UI v3 migration command for a legacy Astro project'). The verb 'generates' and resource 'migration command' are precise. The interactive vs. non-interactive nuance further clarifies behavior. This easily distinguishes it from sibling tools like starwind_init or starwind_add.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description hints at usage context (legacy Astro projects) and default behavior (interactive), but does not explicitly state when NOT to use this tool versus alternatives, nor mention prerequisites or conditions. For example, it is unclear if starwind_migrate should be used over starwind_init for an existing project. The description provides some context but lacks exclusions or comparative guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

starwind_searchC

Searches Starwind UI v3 styled components, Primitive adapters, and Starwind Pro blocks with framework-aware results.

ParametersJSON Schema

Name	Required	Description
`cwd`	No	Project directory used to detect existing Pro setup.
`plan`	No
`limit`	No	Pro result limit; defaults to 20 and caps at 50.
`query`	No
`offset`	No
`surface`	No	Defaults to all.
`category`	No
`framework`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes	Structured layered Starwind search result.

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description bears full burden for behavioral disclosure. It only states what the tool searches but does not confirm it's read-only, describe side effects, authentication needs, rate limits, or any other behavioral characteristics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that efficiently conveys the tool's action and scope. It could be slightly improved by structuring with lists or brief usage notes, but it is not verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (8 parameters, many without descriptions), the description is insufficient. It does not mention filtering dimensions like surface, category, plan, or how the output is structured, despite the output schema existing. The agent would lack context to leverage all features.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is low at 38% (3 of 8 parameters have descriptions). The tool description adds no parameter-level meaning beyond the schema's sparse descriptions. It does not explain the role of query, category, offset, plan, or framework in search behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches across specific resources (Starwind UI v3 styled components, Primitive adapters, Starwind Pro blocks) with framework-aware results. This distinguishes it from sibling tools (init, add, docs, migrate) which are not search functions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, limitations, or exclusions. The context is purely implicit from the tool name and siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

5 tool updatesv0.5.0Aug 18, 2026

Changedstarwind_add11 fields changed

changedInput schema / properties / components / description

Previous value: -"Array of component names to install (e.g., ['button', 'card', 'dialog']). Use '--all' as a single item to install all components."New value: +"Names to install, or a single 'all'/'--all' item."

addedInput schema / properties / components / minItems
```
Added value: +1
```

removedInput schema / properties / cwd / description

Removed value: -"Working directory for package manager detection. Defaults to current directory."

addedInput schema / properties / framework

Added value: +{
+  "description": "Optional framework override.",
+  "enum": [
+    "astro",
+    "react"
+  ],
+  "type": "string"
+}

changedInput schema / properties / init / description

Previous value: -"Whether to include the init command for new projects. Set to true if Starwind UI has not been initialized in the project yet."New value: +"Prepend project initialization for a new setup."

addedInput schema / properties / overwrite

Added value: +{
+  "description": "Allow the CLI to overwrite existing files.",
+  "type": "boolean"
+}

removedInput schema / properties / packageManager / description

Removed value: -"Override the auto-detected package manager. Use this if package manager detection fails or you want to force a specific one."

changedInput schema / properties / pro / description

Previous value: -"Set to true for Starwind Pro projects. This adds --pro to the init command. Required when using @starwind-pro/ blocks. Auto-detected if components contain @starwind-pro/ prefix."New value: +"Configure paid Pro authorization during optional init."

addedInput schema / properties / surface

Added value: +{
+  "description": "Defaults to styled.",
+  "enum": [
+    "styled",
+    "primitive"
+  ],
+  "type": "string"
+}

addedInput schema / properties / to

Added value: +{
+  "description": "Primitive destination passed to --to.",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {
+      "additionalProperties": {},
+      "description": "Structured Starwind installation result.",
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

Changedstarwind_docs4 fields changed

changedInput schema / properties / full / description

Previous value: -"Whether to fetch the full documentation with complete code examples. Defaults to false for a more concise version."New value: +"Use the full aggregate reference when no exact page is found."

addedInput schema / properties / surface

Added value: +{
+  "enum": [
+    "auto",
+    "component",
+    "primitive",
+    "guide",
+    "runtime"
+  ],
+  "type": "string"
+}

removedInput schema / properties / topic / description

Removed value: -"Optional topic to filter documentation (e.g., 'button', 'accordion', 'theming', 'installation'). Leave empty to get all documentation."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {
+      "additionalProperties": {},
+      "description": "Structured Starwind documentation result.",
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

Changedstarwind_init5 fields changed

changedInput schema / properties / cwd / description

Previous value: -"Working directory for package manager detection. Defaults to current directory."New value: +"Project directory used for package manager and framework detection."

addedInput schema / properties / framework

Added value: +{
+  "description": "Optional CLI framework override.",
+  "enum": [
+    "astro",
+    "react"
+  ],
+  "type": "string"
+}

removedInput schema / properties / packageManager / description

Removed value: -"Override the auto-detected package manager. Use this if package manager detection fails or you want to force a specific one."

changedInput schema / properties / pro / description

Previous value: -"Whether to initialize with Starwind Pro support. Defaults to TRUE. Pro setup enables both standard components AND Pro blocks. Only set to false if you specifically want standard-only setup."New value: +"Configure paid Starwind Pro authorization. Defaults to false."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {
+      "additionalProperties": {},
+      "description": "Structured Starwind initialization result.",
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

Addedstarwind_migrate

Changedstarwind_search9 fields changed

removedInput schema / properties / category / description

Removed value: -"Filter Starwind Pro blocks by category."

addedInput schema / properties / cwd

Added value: +{
+  "description": "Project directory used to detect existing Pro setup.",
+  "type": "string"
+}

addedInput schema / properties / framework

Added value: +{
+  "enum": [
+    "astro",
+    "react",
+    "all"
+  ],
+  "type": "string"
+}

changedInput schema / properties / limit / description

Previous value: -"Maximum number of Pro blocks to return. Defaults to 20, maximum 50."New value: +"Pro result limit; defaults to 20 and caps at 50."

removedInput schema / properties / offset / description

Removed value: -"Offset for paginating Pro block results. Defaults to 0."

removedInput schema / properties / plan / description

Removed value: -"Filter Starwind Pro blocks by plan type."

removedInput schema / properties / query / description

Removed value: -"Search query for components and Pro blocks."

addedInput schema / properties / surface

Added value: +{
+  "description": "Defaults to all.",
+  "enum": [
+    "styled",
+    "primitive",
+    "all"
+  ],
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {
+      "additionalProperties": {},
+      "description": "Structured layered Starwind search result.",
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

10 tool updatesv0.4.0Jun 29, 2026
- Removedfetch_llm_data
- Removedget_documentation
- Removedget_package_manager
- Removedinit_project
- Removedinstall_component
- Addedstarwind_add
- Addedstarwind_docs
- Addedstarwind_init
- Addedstarwind_search
- Removedupdate_component
6 tool updatesAug 18, 2025
- First observedfetch_llm_data
- First observedget_documentation
- First observedget_package_manager
- First observedinit_project
- First observedinstall_component
- First observedupdate_component

Deploy Server

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A3.6/5.0

Scored 2026-08-18 08:20 across 5 tools

Disambiguation4/5

Each tool has a clear, distinct purpose: initialization, adding components, searching, documentation, and migration. The only minor ambiguity is between starwind_init and starwind_add, as both generate CLI commands. However, starwind_init is specifically for project initialization, while starwind_add handles component and block installation, which is a reasonable distinction.

Naming Consistency4/5

All tools follow a consistent starwind_ prefix followed by an imperative verb (init, add, search, docs, migrate). This is a clean, predictable pattern. The slight deduction is because the imperative verb is not strictly a verb_noun pattern (e.g., starwind_search instead of starwind_search_components), but this is a minor and common stylistic choice.

Tool Count5/5

With 5 tools, the server is very well-scoped. It covers the core actions a developer would need when using the Starwind UI library within an MCP context: initializing, adding components, searching, and migrating. Each tool clearly earns its place, and the count feels appropriate for the scope of managing and interacting with a UI component library.

Completeness4/5

The tool set covers the primary development workflow: initializing, adding components, searching, accessing documentation, and managing migrations. This provides a comprehensive foundation. The only arguably missing piece might be a tool for direct configuration management or status checks. However, for an MCP interface, this set is remarkably complete and avoids common gaps in lifecycle management.

Maintenance

ActivitySlowing

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Related MCP Connectors

hithereiamaliff-mcp-nextcloudOAuth
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
238
mcp COAuth
com.wix
A Model Context Protocol server for Wix AI tools
Developer Tools Content Management Systems App Automation
215
Svelte MCP A
dev.svelte
The official Svelte MCP server providing docs and autofixing tools for Svelte development
Developer Tools Documentation Access Code Analysis
42332
slhad-aha-mcp
ai.smithery
A TypeScript MCP server for Home Assistant, enabling programmatic management of entities, automati…
Home Automation & IoT App Automation
2

Related MCP Servers

MCP Server
Developer Tools Code Analysis Coding Agents
antfu
A
license
Not graded
quality
D
maintenance
A server that helps AI models better understand Vite/Nuxt applications, providing enhanced context awareness for development support.
Updated 7 months ago (2026-03-01 06:08 UTC)
911
MIT
shadcn-ui MCP Server
Documentation Access Developer Tools
ymadd
A
license
A
quality
D
maintenance
Helps AI assistants access shadcn/ui component documentation and examples through a TypeScript-based MCP server that provides reference information for component details, usage examples, and search capabilities.
Updated a year ago (2025-04-14 06:54 UTC)
4
921 npm
60
MIT
shadcn-ui MCP Server
Documentation Access Developer Tools
totodev999
A
license
A
quality
D
maintenance
Provides reference information for shadcn/ui components through a Model Context Protocol server that helps AI assistants access component documentation and examples.
Updated a year ago (2025-06-09 01:00 UTC)
4
921 npm
MIT
MCP Design System Extractor
Developer Tools Content Management Systems
freema
A
license
A
quality
B
maintenance
Server that enables AI assistants to interact with Storybook design systems. Extract component HTML, analyze styles, and help with design system adoption and refactoring.
Updated 23 days ago (2026-09-19 11:39 UTC)
9
198 npm
70
MIT

クイックスタート

v3モデル

ツール

要件と動作

無料版からProへのアップグレード

開発

ライセンス

セキュリティ

Available Tools

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches