Starwind UI MCP Server vs Basecoat UI MCP
A side-by-side look at the Starwind UI MCP Server and Basecoat UI MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Starwind UI MCP Server for developer tools work as a local process; choose Basecoat UI MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Starwind UI MCP Server when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
starwind_init, starwind_add, starwind_search.
Choose Basecoat UI MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
search_components, get_component_details, get_component_html.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 65/100 · Great | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 35 | 38 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | 33 |
| Full listing | View Starwind UI MCP Server | View Basecoat UI MCP |
Tools & capabilities
Starwind UI MCP Server tools 5
starwind_initGenerates 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.starwind_addGenerates validated Starwind UI v3 install commands for styled components, vendored primitives, or Starwind Pro blocks, with optional Astro or React targeting.starwind_searchSearches Starwind UI v3 styled components, Primitive adapters, and Starwind Pro blocks with framework-aware results.starwind_docsFetches current Starwind UI v3 documentation across styled components, primitives, Runtime, migration, and Astro or React framework guides.starwind_migrateGenerates 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.
Basecoat UI MCP tools 33
search_componentsFind up to 8 compact component summaries by intent and/or query (either field may be omitted). Valid component IDs include: button, card, dialog, dropdown-menu, table, tabs, badge, avatar, input, select, etc. Next step: Call get_component_details or basecoat_component_syntax with the selected component id.get_component_detailsGet one minimal component template, dependencies, and composition tips for Astro or HTML. Valid IDs: any of the 57 Basecoat components (button, card, dialog, dropdown-menu, table, tabs, badge, etc.). When called with {}, returns the top-level component catalog index. Next step: Call validate_composition or basecoat_quality_inspector after integrating markup.get_component_htmlFetch HTML markup template and dependencies for a Basecoat component. Valid IDs: any of 57 Basecoat components. When called with {}, returns the top-level component catalog index. Next step: Call validate_composition or basecoat_quality_inspector to audit.validate_composition[STAGE 4: QUALITY AUDIT] Statically check HTML/Astro source for Basecoat migration errors, semantic rhythm, FSM bindings, missing scripts, nested cards, spacing and hierarchy issues. Pass code or alias html and optionally a semanticProfile and densityProfile. Does not render or evaluate dynamic code. Next step: Fix any errors/warnings reported in the diagnostic output.validate_markup[STAGE 4: QUALITY AUDIT] Alias of validate_composition. Statically check HTML/Astro source for Basecoat migration errors, semantic rhythm, FSM bindings, missing scripts, nested cards, spacing and hierarchy issues. Next step: Fix any errors/warnings reported in the diagnostic output.search_macro_blocksSearch approved macro layout blocks by query, role, family, or tag. Optional design/page/slot context filters to slot-compatible roles. Returns summaries and immutable refs only; use cursors for more.get_macro_blockRetrieve one section of a compiled macro block blueprint (manifest, structure, slots, ports, rules, dependencies, provenance). Follow next cursors until complete. Optional designId pins aliases to that session registry.begin_designCreate a persistent design session under the host project root. Pass designId, profile (alias or ref), operationId, and optional decisions. Pins and hash-verifies the packaged macro registry. Idempotent for the same operationId. Oversized optional receipt fields may be omitted with truncated:true after commit.get_design_contextRead a focused design view: sessions (no designId), overview, decisions, graph, rules, focus, or next. Pin revision on first read; continuations must match. Does not create sessions.apply_design_patchApply one atomic list of design graph operations with expectedRevision and operationId. Replay with the same operationId returns the original receipt. A committed mutation always acknowledges success; oversized optional fields may be omitted with truncated:true. Does not write application source files.validate_designValidate a design session (or one page) in draft or complete mode. Returns totals plus paginated diagnostics. A plan-ready graph is not proof of rendered correctness.get_rhythm_rulesRead the effective semantic rhythm profile by family, including project-local overrides under a contained .basecoat/rhythm.json. Semantic IDs and approved implementation utilities are returned separately. Results are content-addressed and cursor-paginated; changed effective revisions invalidate prior cursors.- +21 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Starwind UI MCP Server
{
"mcpServers": {
"starwind-ui-mcp-server": {
"command": "npx",
"args": [
"-y",
"@starwind-ui/mcp"
]
}
}
}
Basecoat UI MCP
{
"mcpServers": {
"basecoat-ui-mcp": {
"command": "npx",
"args": [
"-y",
"@intellmedia/basecoat-ui-mcp"
]
}
}
}
Frequently asked questions
Starwind UI MCP Server is categorized under Developer Tools and uses a local stdio subprocess. Basecoat UI MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Starwind UI MCP Server for developer tools work and Basecoat UI MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Starwind UI MCP Server has no declared pricing — check the project's own site. Basecoat UI MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add starwind-ui-mcp-server and basecoat-ui-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Starwind UI MCP Server has a quality signal of 65/100 (Great) with 0 views, 0 installs and 35 GitHub stars. Basecoat UI MCP has 65/100 (Great) with 0 views, 0 installs and 38 GitHub stars.