Basecoat UI

MCP开发工具

提供方 未标注

开发工具 未标注 未标注 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

第三方离线stdio MCP,用于Astro/静态HTML中的Basecoat UI组合:精选模板、静态验证、无运行时网络。

一句话选型结论

按资料字段整理

Basecoat UI 属于开发工具类 MCP 服务器,传输方式未标注,鉴权方式未标注,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权未标注 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

开发

安装与配置

未标注 未标注
上游未给出传输方式
{ "mcpServers": { "basecoat-ui": { "command": "npx", "args": ["-y", "@intellmedia/basecoat-ui-mcp", "--project-root", "${workspaceFolder}"] } } }

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Basecoat UI当前 未标注 未标注 未标注 有 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

36.0 KB
来自项目仓库与上游目录的原文,未做删改

Basecoat UI MCP

Offline Model Context Protocol server for Basecoat UI (shadcn/ui look without bundling or requiring React).

Curated templates, macro layouts, rhythm tokens, and static validation for Astro, Next.js, HTML, and Tailwind CSS 4.

The server exposes a deterministic, offline registry for AI coding agents instead of requiring clients to scrape documentation. It runs over local stdio with zero runtime network requests, bounded < 2 KB responses, and bounded lexical/heuristic static source validation. The host application remains responsible for rendering, data access, authentication, sessions, credentials, OAuth, captcha, and other runtime behavior.

Install

Requires Node.js 22.14.0 or newer.

Quick Start by Client

Cursor (.cursor/mcp.json)```json

{
"mcpServers": {
"basecoat-ui": {
"command": "npx",
"args": ["-y", "@intellmedia/basecoat-ui-mcp", "--project-root", "${workspaceFolder}"]
}
}
}


#### Claude Desktop (`claude_desktop_config.json`)```json
{
  &quot;mcpServers&quot;: {
    &quot;basecoat-ui&quot;: {
      &quot;command&quot;: &quot;npx&quot;,
      &quot;args&quot;: [&quot;-y&quot;, &quot;@intellmedia/basecoat-ui-mcp&quot;, &quot;--project-root&quot;, &quot;/absolute/path/to/your/application&quot;]
    }
  }
}

Claude Code (CLI)```sh

claude mcp add basecoat-ui -- npx -y @intellmedia/basecoat-ui-mcp --project-root $(pwd)


#### Generic npx (no install)```json
{
  &quot;mcpServers&quot;: {
    &quot;basecoat-ui&quot;: {
      &quot;command&quot;: &quot;npx&quot;,
      &quot;args&quot;: [&quot;-y&quot;, &quot;@intellmedia/basecoat-ui-mcp&quot;, &quot;--project-root&quot;, &quot;/absolute/path/to/your/application&quot;]
    }
  }
}

npm```sh

npm install --global @intellmedia/basecoat-ui-mcp


Add the server to an MCP client. Use an absolute path for the host application so design context and persistent sessions belong to the intended project:```json
{
  &quot;mcpServers&quot;: {
    &quot;basecoat-ui&quot;: {
      &quot;command&quot;: &quot;basecoat-ui-mcp&quot;,
      &quot;args&quot;: [&quot;--project-root&quot;, &quot;/absolute/path/to/your/application&quot;]
    }
  }
}

The compiled entry can also be invoked directly:```json
{
"mcpServers": {
"basecoat-ui": {
"command": "node",
"args": [
"/absolute/path/to/node_modules/@intellmedia/basecoat-ui-mcp/dist/server/stdio.js",
"--project-root",
"/absolute/path/to/your/application"
]
}
}
}


Published packages include prebuilt `dist/` and the immutable semantic snapshot
under `src/semantics/`. Server startup reads that snapshot and does not write
inside the installed package. The package contract test builds first, creates
and extracts an actual npm tarball, marks the extracted package tree read-only,
starts its `dist/server/stdio.js` under a network tripwire, completes MCP
initialize and tool-list requests, and closes the connection. A source checkout
does not include `dist/`.

### From source```sh
git clone https://github.com/zygiu-zygis/basecoat-ui-mcp.git
cd basecoat-ui-mcp
npm ci
npm run build
npm start -- --project-root /absolute/path/to/your/application

--project-root takes precedence over BASECOAT_PROJECT_ROOT, which takes precedence over the launch directory. The selected directory is the host project, not the MCP installation directory. The server exposes stdio only.

Project-root configuration

The configured root controls two things:

  • DESIGN.md is read from that directory by basecoat://project/context.
  • Persistent macro sessions are stored under /.basecoat/designer/.
  • .basecoat/rhythm.json is an optional strict override. It must live under a
    real .basecoat directory inside the project root, be a regular non-symlink
    file no larger than 65,536 UTF-8 bytes, and resolve inside that root; missing
    or rejected files leave the packaged profile unchanged. Matching mapping IDs
    replace in place and keep packaged order.

Only that exact directory is used. The server does not walk parent directories. Keep .basecoat/ in the host project and back it up if design sessions are part of your workflow. The MCP server never writes host application source files.

Basecoat MCP tools

The server exposes 22 offline MCP tools organized across six architectural layers: project setup and configuration, intent-driven layout orchestration, theme-aware charts, component retrieval, macro design graphs, and semantic state contracts. Every tool result is a bounded MCP packet of at most 1,999 UTF-8 bytes. Larger result sets use cursors; responses are not sliced mid-JSON.

Complete MCP Tool Table

Tool Name Layer Description Mode
basecoat_setup_config Setup & Config Generates framework boilerplates, Tailwind CSS 4 imports, OKLCH variables, and no-flash dark mode scripts Read-only
basecoat_page_architect Intent Fast Path Plans complete layout scaffolds with container grid contracts and explicit slot topology Read-only
basecoat_compose_stack Intent Fast Path Assembles composable component stacks into canonical shells (sidebar-01..16, topbar, inset, split) with slot hydration Read-only
basecoat_rules_enforcer Intent Fast Path Enforces technical constraints across Tailwind v4, FSM state contracts, semantic tokens, and dashboard rules Read-only
basecoat_creative_director Intent Fast Path Surfaces Kanso minimalism, 4px/8px optical rhythm, density profiles, typography ladders, and contrast pairings Read-only
basecoat_component_syntax Intent Fast Path Delivers copy-pasteable HTML/Astro component markup with pre-configured FSM state variants and inline SVG icons Read-only
basecoat_list_charts Charts & Data Viz Lists and filters 56 theme-aware chart blueprints across 7 categories with keyword search Read-only
basecoat_get_chart_blueprint Charts & Data Viz Retrieves chart HTML using semantic CSS tokens (--chart-1..5) and mount scripts for 5 frameworks Read-only
basecoat_quality_inspector Quality & Audit Audits HTML/Astro markup with Score (0-100), letter grade, syntax violations, a11y omissions, and auto-fix suggestions Read-only
search_components Components Searches up to 8 compact component summaries by intent and/or query across 62 curated components Read-only
get_component_details Components Retrieves minimal component template, dependencies, and composition guidance for Astro or HTML Read-only
get_component_html Components Retrieves HTML markup template and dependencies for any curated component Read-only
validate_composition Static Analysis Statically checks up to 256 KiB of markup for migration errors, rhythm, FSM bindings, and accessibility Read-only
validate_markup Static Analysis Validates HTML/Astro markup syntax, structure, landmark ordering, and semantic constraints Read-only
search_macro_blocks Macro Graph Searches approved macro layout blocks by query, role, family, or tag across 84 blocks and aliases Read-only
get_macro_block Macro Graph Retrieves a section of a compiled macro block blueprint (manifest, structure, slots, ports, rules, etc.) Read-only
begin_design Macro Graph Creates a persistent, hash-verified design session under .basecoat/designer/ pinning profile and registry revision Mutation (idempotent)
get_design_context Macro Graph Reads focused design session views (sessions, overview, decisions, graph, rules, focus, next) Read-only
apply_design_patch Macro Graph Applies atomic graph mutations with expectedRevision and idempotent operationId Mutation (idempotent)
validate_design Macro Graph Validates draft or complete design graphs, returning diagnostic totals and paginated issues Read-only
get_rhythm_rules Semantics & Tokens Reads effective semantic rhythm profiles and approved utilities by family, supporting project-local overrides Read-only
get_fsm_recipe Semantics & State Reads finite state machine interaction states, events, transitions, guards, and actions Read-only

Intent-Driven Design Layer (Fast Path)

  1. basecoat_setup_config - Framework and styling configuration generator. Outputs ready-to-use boilerplate for 6 targets (astro, vanilla, nextjs, sveltekit, vite, htmx), 8 aesthetic style packs (vega, nova, maia, lyra, mira, luma, sera, rhea), complete OKLCH @theme inline blocks, and synchronous `` inline dark mode scripts.
  2. basecoat_page_architect - Query recipes (src/macros/authoring/recipes/*.json) and macro blocks (src/macros/authoring/blocks/*.json) by intent, recipe, or block. Delivers full layout scaffolds with explicit data-slot markers, semantic HTML skeletons, grid structures, and responsive containers. Fully covers 5 dashboard page archetypes:
    - Executive Dashboard (workspace-dashboard, executive-dashboard) - KPI stat cards, revenue chart, and recent activity.
    - E-commerce Overview (ecommerce-overview) - Sales metrics, revenue analytics, top products card, and order summary.
    - Analytics Workspace (analytics-workspace) - Filter toolbar, time-series interactive chart, and cohort analysis breakdown.
    - Data Table Detail (workspace-detail, data-table-detail) - Paginated data table with search/filters and slide-over inspection drawer.
    - Settings Split-Screen (workspace-settings, settings-split-screen) - Two-column responsive layout with vertical section navigation and form controls.
    Supports density controls (compact for high-density enterprise tools, comfortable for standard interfaces).
  3. basecoat_compose_stack - Dynamically composes 45 pre-built component stacks across 7 categories (shell-stacks, header-stacks, kpi-stacks, chart-stacks, table-stacks, overlay-stacks, form-stacks) into canonical shells (sidebar-01..sidebar-16, topbar-shell, inset-shell, split-shell) with automated slot hydration.
  4. basecoat_rules_enforcer - Enforces strict technical constraints across tailwind-v4, fsm-contracts, tokens, semantic-html, and dashboard-patterns:
    - MET-01: KPI numerals require text-2xl/text-3xl with tabular-nums and semantic trend indicators.
    - TBL-01: Data tables require wrapper, sticky blurred , and right-aligned numeric cells.
    - FRM-01: Input controls require wrappers with associated `. -NAV-01: Headers must use compacth-12orh-14(forbidding oversizedh-16). -TW4-01: Rejects deprecated Tailwind v3 utilities (bg-opacity-,flex-shrink-,@tailwinddirectives). -TOK-01: Rejects arbitrary bracket dimensions (w-[327px]) and hardcoded hex colors (#ff0000,bg-[#123456]). -FSM-01: Enforces finite state machine contracts on interactive primitives (dialog,dropdown-menu,accordion,tabs`).
  5. basecoat_creative_director - Surfaces Kanso minimalism and Basecoat design intelligence:
    - Density profiles: compact (p-4 gap-4, header h-12, table py-2), standard (p-6 gap-4/gap-6, header h-14, table py-3), and comfortable (p-6 md:p-8, header h-14).
    - Mathematical 4px/8px optical rhythm grid and typography ladders (tabular-nums on all metrics and numeric table cells).
    - Subtle 1px card ring elevation without conflicting border utilities.
    - WCAG 2.1 AA (contrast >= 4.5:1) and APCA ($L_c \ge 60$) token pairings.
  6. basecoat_component_syntax - Delivers copy-pasteable HTML or Astro component markup from src/registry/components.json with pre-configured FSM state variants (default, active, loading, disabled, open, closed, open/closed), verified inline SVG action icons (plus, edit, trash, search, chevron-down, check, external-link), and composite component patterns:
    - metric-card (metrics-summary, kpi-card) - Stat card with tabular-nums numeral and trend badge.
    - data-table (datatable) - Sticky header table wrapped in overflow-x-auto with right-aligned numeric cells.
    - sidebar-shell (sidebar-dashboard-shell) - Desktop sticky navigation with responsive flyout below md.
  7. basecoat_quality_inspector - Audits HTML/Astro compositions against dashboard audit rules: table-overflow-wrapper, kpi-metric-tabular-nums, table-numeric-alignment, a11y-focus-ring (flagging outline-none without focus visible ring), arbitrary color/dimension violations, and WCAG/APCA contrast pairings. Returns score (0-100), letter grade (A-F), structured issues, and actionable autoFixSuggestions.

Theme-Aware Charts and Data Visualization

  1. basecoat_list_charts - Discovers and filters 56 theme-aware chart blueprints across 7 categories (area, bar, line, pie, radar, radial, tooltip) with keyword search / query, layout footprint (layoutFootprint), requiredTokens, and variant summaries.
  2. basecoat_get_chart_blueprint - Retrieves chart container HTML (chart-container, role=&quot;img&quot;, accessible fallback, and glassmorphic tooltip markup with bg-background/95 backdrop-blur-sm), CSS tokens (var(--chart-1) through var(--chart-5), var(--color-border), var(--color-muted-foreground)), client options, layoutFootprint, and framework mount code for 5 frameworks (vanilla, astro, react, vue, svelte) with optional themeTokens overrides. Accepts chartId or alias id (defaults to area-default). Integrated directly into dashboard-01 and svg-area-chart (data-chart-id=&quot;area-interactive&quot;). Generated deterministically via node scripts/ingest-shadcn-charts.mjs.

Component tools

  • search_components returns up to 8 compact {id, name, intent} summaries across the 62 curated components and never returns markup. intent and query are optional; an empty search returns an empty list.
  • get_component_details returns one Astro or HTML template with dependencies and composition guidance. Oversized entries fail closed. theme-toggle resolves to theme-switcher.
  • get_component_html returns the HTML markup template and dependencies for any curated component (environment defaults to html).
  • validate_composition statically checks up to 256 KiB (262,144 UTF-8 bytes) of HTML or Astro source and returns at most 24 issues (including WCAG 2.1 / APCA token contrast, arbitrary dimensions, dialog focus traps, and aria-controls bindings). Pass code or html, and optional semanticProfile or densityProfile (comfortable|compact). It does not render, execute, resolve application modules, or certify runtime browser accessibility.
  • validate_markup statically validates HTML/Astro source syntax, container tags, landmark ordering, and semantic constraints against Basecoat guidelines.

Macro tools

The macro layer is this project's curated, project-specific composition system for shells, auth flows, data workspaces, slots, ports, rules, and recipes. It is compiled into a pinned registry snapshot. These layout contracts are not supplied automatically by shadcn or by MCP.

  1. search_macro_blocks - find compatible blueprint blocks by query, role, family, or tag across 84 blocks and aliases.
  2. get_macro_block - read a block section such as manifest, structure, slots, ports, rules, dependencies, or provenance.
  3. begin_design - create a persistent design session and pin its profile and registry revision. Pinned registries are hash-verified on load.
  4. get_design_context - read session lists or focused views such as overview, graph, rules, focus, and next.
  5. apply_design_patch - apply atomic graph changes with expectedRevision and an idempotent operationId. A committed mutation always returns a success acknowledgement; oversized optional payload may be omitted with truncated: true.
  6. validate_design - validate a draft or complete design graph and page its diagnostics.

Design sessions persist under /.basecoat/designer/. Registry revisions are content-addressed; a session keeps using its pinned revision even after the package snapshot changes. Design snapshots use the form d:@.

Curated block blueprints (84 blocks and aliases including translated shadcn/ui v4 blocks):
- Canonical Shells & Sidebars: sidebar-01 through sidebar-16, sidebar-dashboard-shell, sidebar-inset-shell, sidebar-collapsible-icon, sidebar-mobile-flyout, sidebar-nav, topbar-shell, topbar-nav, app-shell, page-header.
- Dashboards & Workspaces: dashboard-01 through dashboard-07, dashboard-workspace, dashboard-main, dashboard-activity, analytics, analytics-workspace, ecommerce-overview, tasks, tasks-table-workspace, mail, mail-workspace.
- Metrics & Data Tables: metrics-summary, data-table-rich, data-table, data-table-detail-layout, data-workspace, data-bulk-actions, data-filters, data-pager, products, billing, settings.
- Forms & Authentication: login-01 through login-05, signup-01 through signup-05, otp-01 through otp-05, form-field-group, forms, form-section, authentication, auth-sign-in, auth-sign-up, auth-split-screen, auth-recovery, auth-reset.
- Charts & Feedback: svg-area-chart, empty-state, error-boundary, newsletter-waitlist, pricing-tiers, segmented-toggle, detail-drawer-panel, product-detail-layout, settings-workspace.

Multi-block recipes (11 page recipes):
- workspace-dashboard - full analytics dashboard (KPI cards, activity chart, records table).
- ecommerce-overview - e-commerce operational dashboard with order metrics and product highlights.
- analytics-workspace - analytics dashboard with time-series charts and cohort views.
- workspace-settings - application shell with navigation, header, and settings workspace tabs.
- workspace-detail / tasks-table-workspace - data table workspace with slide-over detail inspection drawer.
- mail-workspace - multi-pane email client layout with inbox list and detail view.
- auth-flow - bidirectional authentication flow between sign-in and sign-up cards.
- auth-split-flow - split-screen auth frame pairing sign-in and sign-up with hero media.
- data-records - records page with filters, table, and pager.
- marketing-pricing - 3-tier pricing table paired with newsletter/waitlist banner.

Semantic tools

The semantic layer provides compiled rhythm profiles and finite state machine recipes:

  1. get_rhythm_rules - access approved spacing, typography, surfaces, borders, and layout patterns by profile and family filters.
  2. get_fsm_recipe - read interaction states, events, transitions, guards, and actions for dialog, navigation (collapsible-navigation), auth-flow, and tabs.

Semantic tools use the same bounded pagination as macro tools. Each rhythm record keeps the semantic token ID separate from its approved Tailwind utility. Put the utility in class; keep the semantic ID in design metadata and agent reasoning. Project overrides from /.basecoat/rhythm.json are reflected in an effective content ref and revision. FSM recipes are structural metadata, not runtime implementations.

End-to-end example

A dashboard page can follow this sequence:```text
get_design_context(view="sessions")
begin_design(designId="admin", profile="app-default", operationId="begin-admin")
get_rhythm_rules(profile="default", family="density")
search_macro_blocks(q="shell", limit=8)
apply_design_patch(
designId="admin",
expectedRevision=0,
operationId="add-dashboard",
operations=[{ op: "instantiate_recipe",
recipe: "workspace-dashboard",
pagePrefix: "admin" }]
)
get_design_context(view="overview", designId="admin")
get_macro_block(idOrRef="app-shell", section="structure", designId="admin")
get_fsm_recipe(recipe="dialog", section="transitions")


Implement the selected component leaves in the host project, then record completed regions with `apply_design_patch(record_written)`. Finish with `validate_design(mode=&quot;complete&quot;)` and `validate_composition` on the generated Astro or HTML source. After a conflict or restart, reread the session and use the returned revision and cursors.

Copy `templates/cursor/basecoat-designer.mdc` into a host project&#x27;s `.cursor/rules` for agent guidance. The MCP server does not write consumer application source files.

### Auditing or restyling an existing UI

No design session is needed. Read `basecoat://design/theming` and `basecoat://design/rhythm`, call `get_component_details` for each control you change, then run `validate_composition` on the rendered layout source including `` scripts and ``. Theme rules:

- `theme-strategy-mixed` - `@media (prefers-color-scheme: dark)` combined with the `.dark` class strategy (dark tokens leak into light mode).
- `theme-storage-key` - a theme script persists under a key other than Basecoat&#x27;s `themeMode`, creating a second resolver that drifts from `window.basecoat.theme`.

Check light and dark screenshots with an OS dark preference and empty `localStorage` before deploying.

### Source adaptation and offline import

The macro importer is intentionally local-first. It accepts a checked-out or otherwise
locally saved shadcn-style `registry-item.json`, a reviewed mapping, and a local
dependency lock:```sh
npm run import:blocks -- \
  --item=/path/to/registry-item.json \
  --mapping=/path/to/mapping.json \
  --lock=/path/to/dependency-lock.json \
  --dry-run

This command does not fetch live shadcn registry items, install packages, execute
upstream code, or make runtime network requests. Unknown, unlocked, or explicitly
unsupported dependencies produce diagnostics instead of guesses. Omitted OAuth,
captcha, session, credential, and other application features are reported as
obligations. The importer emits only the curated structural block; the host
application must implement the runtime behavior.

The mapping and resulting provenance make the boundary explicit: shadcn-style source
is an input reference, while layout contracts, slots, ports, rules, and recipes are
curated adaptations owned by this project's macro layer. They are not features
provided by shadcn or by MCP. Upstream refreshes are separate maintainer authoring
operations and never occur from the MCP server.

Basecoat MCP resources

The server exposes 8 authoritative MCP resources spanning the 3-pillar Skill Vault, core design system contracts, multi-framework integration guides, and live host project context:

Complete MCP Resource Table

Resource URI Category Description MIME Type
basecoat://skills/core Skill Vault Core Basecoat UI design philosophy, Kanso minimalism, and foundational component usage text/markdown
basecoat://skills/dashboard Skill Vault Comprehensive dashboard architecture, layout patterns, page types, sidebar configurations, and audit checklists text/markdown
basecoat://skills/charts Skill Vault Theme-aware chart blueprints, CSS token mapping (--chart-1..5), ApexCharts configuration, and multi-framework integration text/markdown
basecoat://skills/files/* Skill Vault Dynamic file access resource to read individual documentation and reference markdown files across the 96-file Skill Vault text/markdown
basecoat://design/rhythm Design System Content hierarchy, 4px/8px optical spacing rhythm, typography ladders, density profiles, and structural composition rules text/markdown
basecoat://design/theming Theming & Dark Mode Basecoat OKLCH token contract, 8 official style packs (Vega..Rhea), class-based dark mode (themeMode resolver), and no-flash bootstrap text/markdown
basecoat://integration/frameworks Integration Guide Production integration guide covering Astro, Next.js, Express, Vite, Tailwind CSS 4 setup, and framework-agnostic HTML text/markdown
basecoat://project/context Project Context Live on-demand read of the host project's DESIGN.md (bounded to 6,000 UTF-8 bytes) application/json
  • basecoat://skills/core provides foundational guidelines for building clean, minimal interfaces using Basecoat CSS, including design philosophy, atomic styling principles, and component construction.
  • basecoat://skills/dashboard provides enterprise dashboard architecture, navigation patterns, data display conventions, form layouts, and accessibility checklists.
  • basecoat://skills/charts provides complete guidance on theme-aware ApexCharts and SVG data visualization using pure Basecoat CSS color tokens (var(--chart-1) through var(--chart-5)) across 5 frameworks.
  • basecoat://skills/files/* enables dynamic lookup and retrieval of any specific markdown file within the 96-file Skill Vault (skills/basecoat, skills/basecoat-dashboard, skills/basecoat-charts).
  • basecoat://design/rhythm provides content hierarchy, spacing, typography, component-family, and structural composition rules.
  • basecoat://design/theming provides the Basecoat token contract, all 8 official style packs (Vega, Nova, Maia, Lyra, Mira, Luma, Sera, Rhea), class-based dark mode via window.basecoat.theme (themeMode key), no-flash bootstrap, and form-control/autofill pitfalls. Read it before restyling or auditing an existing UI.
  • basecoat://integration/frameworks provides Astro, Next.js, Express, Vite, Tailwind CSS 4 (including style pack imports like @import &quot;basecoat-css/vega&quot;;), selective Basecoat JavaScript, and native dialog setup.
  • basecoat://project/context reads the configured host project's DESIGN.md on demand. Output is capped at 6,000 UTF-8 bytes and truncates on a newline or sentence boundary when possible. Symlinks and non-regular files are refused.

Recommended flow:

  1. Read the rhythm and project-context resources.
  2. Decide content hierarchy and layout.
  3. Search summaries, then request details only for selected components.
  4. Read the integration resource when connecting production assets.
  5. Validate the final source.

Minimal HTML example

The host application supplies its compiled Tailwind and Basecoat stylesheet:```html
<link rel="stylesheet" href="/assets/basecoat.css">
<button type="button" class="btn" data-variant="default">Save changes</button>


### Header Control Cluster (Style Preset Selector + Theme Switcher)```html
&lt;div class=&quot;flex items-center gap-2&quot;&gt;
  &lt;select id=&quot;style-variant-select&quot; class=&quot;select h-8 w-28 text-sm leading-none&quot; aria-label=&quot;Style pack&quot;&gt;
    &lt;option value=&quot;vega&quot;&gt;Vega&lt;/option&gt;
    &lt;option value=&quot;nova&quot;&gt;Nova&lt;/option&gt;
    &lt;option value=&quot;maia&quot;&gt;Maia&lt;/option&gt;
    &lt;option value=&quot;lyra&quot;&gt;Lyra&lt;/option&gt;
    &lt;option value=&quot;mira&quot;&gt;Mira&lt;/option&gt;
    &lt;option value=&quot;luma&quot;&gt;Luma&lt;/option&gt;
    &lt;option value=&quot;sera&quot;&gt;Sera&lt;/option&gt;
    &lt;option value=&quot;rhea&quot;&gt;Rhea&lt;/option&gt;
  &lt;/select&gt;
  &lt;button type=&quot;button&quot; aria-label=&quot;Toggle dark mode&quot; data-tooltip=&quot;Toggle dark mode&quot; data-side=&quot;bottom&quot; onclick=&quot;window.basecoat.theme.toggle()&quot; class=&quot;btn size-8&quot; data-variant=&quot;outline&quot; data-size=&quot;icon&quot;&gt;
    &lt;span class=&quot;hidden dark:block&quot; aria-hidden=&quot;true&quot;&gt;&lt;svg class=&quot;lucide lucide-sun size-4&quot; viewBox=&quot;0 0 24 24&quot; fill=&quot;none&quot; stroke=&quot;currentColor&quot; stroke-width=&quot;2&quot; stroke-linecap=&quot;round&quot; stroke-linejoin=&quot;round&quot;&gt;&lt;circle cx=&quot;12&quot; cy=&quot;12&quot; r=&quot;4&quot;/&gt;&lt;path d=&quot;M12 2v2m0 16v2m-7.07-2.93 1.41-1.41m11.32-11.32 1.41-1.41M2 12h2m16 0h2m-2.93 7.07-1.41-1.41M6.34 6.34 4.93 4.93&quot;/&gt;&lt;/svg&gt;&lt;/span&gt;
    &lt;span class=&quot;block dark:hidden&quot; aria-hidden=&quot;true&quot;&gt;&lt;svg class=&quot;lucide lucide-moon size-4&quot; viewBox=&quot;0 0 24 24&quot; fill=&quot;none&quot; stroke=&quot;currentColor&quot; stroke-width=&quot;2&quot; stroke-linecap=&quot;round&quot; stroke-linejoin=&quot;round&quot;&gt;&lt;path d=&quot;M20.985 12.486a9 9 0 1 1-9.473-9.472c.405-.022.617.46.402.803a6 6 0 0 0 8.268 8.268c.344-.215.825-.004.803.401&quot;/&gt;&lt;/svg&gt;&lt;/span&gt;
  &lt;/button&gt;
&lt;/div&gt;

Basecoat 1.x uses btn with data-variant and data-size. Interactive components list the granular JavaScript modules the host must load.

Macro-Driven Dashboard Generation

The MCP server provides a robust set of macro layouts (search_macro_blocks) that enable connected LLMs to predictably assemble complex layouts (like Shadcn dashboards) out-of-the-box.

  • Layout Neutrality: Supports both sidebar (sidebar-dashboard-shell, sidebar-inset-shell) and top-bar architectures (topbar-shell, topbar-nav).
  • Strict Validation: The validate_composition tool ensures that generated layouts adhere to the Basecoat CSS theming contracts, strict spacing rhythm scales (0, 2, 4, 6, 8, 12), and proper landmark accessibility.
  • Agent Guidance: LLMs are encouraged to use search_macro_blocks to find a shell (layout wrapper), and dashboard-main or dashboard-workspace to populate the main container, guaranteeing deterministic, pixel-perfect Shadcn/ui parody without React runtime artifacts.

Registry and exclusions

The checked-in registry contains 62 curated components: all 57 shadcn/ui New York v4 primitives adapted for pure Basecoat CSS without React, plus Basecoat extensions (theme-switcher, segmented-toggle, svg-area-chart, native-select) with explicit FSM state contracts:

accordion, alert, alert-dialog, aspect-ratio, avatar, badge, breadcrumb, button, button-group, calendar, card, carousel, chart, checkbox, collapsible, combobox, command, context-menu, data-table, date-picker, dialog, drawer, dropdown-menu, empty, field, form, hover-card, input, input-group, input-otp, item, kbd, label, menubar, native-select, navigation-menu, pagination, popover, progress, radio-group, resizable, scroll-area, segmented-toggle, select, separator, sheet, sidebar, skeleton, slider, sonner, spinner, svg-area-chart, switch, table, tabs, textarea, theme-switcher, toast, toggle, toggle-group, tooltip

Comprehensive Catalog Counts

…(正文过长,页面只展示前面部分,完整内容见仓库)

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Basecoat UI 怎么安装?

在客户端按下面的安装命令接入:{ "mcpServers": { "basecoat-ui": { "command": "npx", "args": ["-y", "@intellmedia/basecoat-ui-mcp", "--project-root", "${workspaceFolder}"] } } }。装完在客户端配置里引用同一个包或端点。

Basecoat UI 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Basecoat UI 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Basecoat UI 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

Basecoat UI 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Windsurf、Codex;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Basecoat UI 能提供哪些能力?

资料显示能力标签包括 开发。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。