Basecoat UI MCP logo

Basecoat UI MCP

Offline stdio tools for Basecoat UI templates, layout composition, design rules, and static HTML or Astro validation.

Install Basecoat UI MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "basecoat-ui-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@intellmedia/basecoat-ui-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 33 tools correctly ().

Overview

Basecoat UI MCP MCP server provides an offline stdio registry for Basecoat UI templates, layout blueprints, rhythm rules, and validation. It serves deterministic MCP tool responses from a packaged semantic snapshot and can read project context and persist design sessions under a configured project root. Use it when an AI coding client needs Basecoat-oriented composition guidance without network access; it does not render pages or modify application source files.

Use cases

  • Search Basecoat UI templates for an Astro or HTML implementation
  • Compose dashboards and authentication flows from curated layout blocks
  • Validate HTML or Astro composition without rendering the application
  • Inspect spacing and typography rules for a project design
  • Persist and validate multi-block design sessions

Key features

  • Offline local stdio transport
  • Astro and HTML component templates
  • Macro layout blocks and page recipes
  • Static HTML and Astro composition validation
  • Persistent project-scoped design sessions
  • Compiled rhythm and interaction-state rules

Tools33

What Basecoat UI MCP lets your agent do. Expand a tool for its parameters.

Verified live~13.5k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

12/12 checks healthy over the last 54d

What it can do

From the 33 tools this server returned when we ran it; 33 declare their own safety hints.

Runs commands · 2Handles credentials · 5Makes network requests · 1Read-only tools · 31
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age29 days
Maintainers1

Observed 2026-10-25 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · @intellmedia/basecoat-ui-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars17Stargazers on the source repository.
npm downloads393Package downloads in the last 30 days.
Last commit6d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed33Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Basecoat UI MCP works

What Basecoat UI MCP MCP server does

Basecoat UI MCP MCP server gives AI coding clients structured design information for Basecoat UI, which follows a shadcn/ui visual direction without requiring React. Its registry covers Astro and HTML component templates, reusable application layout blocks, multi-block recipes, spacing and typography profiles, and interaction-state recipes.

The server is intended for design assistance rather than runtime application behavior. It does not render interfaces, execute submitted code, resolve application modules, access external services, or write host project source files. Authentication, data access, sessions, credentials, OAuth, and captcha remain responsibilities of the host application.

How it works

Basecoat UI MCP MCP server runs locally over stdio and uses a compiled, pinned registry snapshot. Runtime operation makes no network requests. Responses are bounded to 1,999 UTF-8 bytes for macro and semantic operations; cursor-based pagination is used when a result set is larger than one response. Component searches return compact metadata rather than markup, while component detail requests can return an Astro or HTML template with dependencies and composition notes.

A project root links the server to the application being designed. The server reads DESIGN.md from that directory and stores persistent macro design sessions in <project-root>/.basecoat/designer/. An optional .basecoat/rhythm.json can replace matching rhythm mappings when it satisfies the file, size, location, and symlink checks described by the project. The server does not search parent directories.

Design sessions retain the registry revision selected when they begin. Graph mutations require an expected revision and an idempotent operation identifier, allowing clients to apply controlled changes and validate the resulting design graph.

Setup and configuration

Node.js 22.14.0 or newer is required. Install the published package with npx, install it globally with npm, invoke the compiled stdio entry directly, or build from source after cloning the repository. The MCP client configuration must launch the package as a local command.

Set --project-root to an absolute path for the host application. This option takes precedence over BASECOAT_PROJECT_ROOT, which takes precedence over the process launch directory. The selected path is the application root, not the directory containing the MCP package. The server exposes stdio only.

For example, a generic configuration can launch npx -y @intellmedia/basecoat-ui-mcp --project-root /absolute/path/to/your/application. When using a global installation, launch basecoat-ui-mcp with the same project-root argument. Published packages contain prebuilt dist/ files and the semantic snapshot; a source checkout must be built before starting the server.

Tools and capabilities

Basecoat UI MCP MCP server exposes three groups of tools:

  • Component tools search the catalog, retrieve one template, and statically inspect up to 256 KiB of HTML or Astro source. Composition validation reports up to 24 issues and accepts optional semantic and density profiles. It does not certify accessibility.
  • Macro tools search and inspect blueprint blocks, start and read persistent design sessions, apply atomic graph patches, and validate design graphs with paged diagnostics. Available blocks cover shells, navigation, authentication, dashboards, settings, forms, data views, marketing, content, and utility patterns.
  • Semantic tools provide approved rhythm rules and finite-state-machine recipes. Rhythm data covers spacing, typography, surfaces, borders, and layout patterns; FSM recipes describe states, events, transitions, guards, and actions for supported interactions.

The registry also includes recipes for analytics dashboards, settings workspaces, detail drawers, authentication flows, split-screen authentication, and pricing pages. Component lookup maps theme-toggle to theme-switcher.

Limitations and notes

The server is offline and deterministic, but its guidance comes from a packaged registry rather than the application’s live component implementation. Oversized component entries fail closed, and oversized optional design payloads may be omitted with a truncation indicator. Validation is static: it neither renders the page nor runs application behavior. Keep .basecoat/ in the host project if design sessions need to persist, and back up that directory as part of the project workflow.

Written by AllMCPs with AI assistance from the project’s README and listing data. How we build listings

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Basecoat UI MCP

Basecoat UI MCP is an MCP server that connects AI coding clients to an offline Basecoat UI registry and a selected local project. Its main tools search components, retrieve templates, validate HTML or Astro composition, manage macro design sessions, and provide rhythm rules plus finite-state-machine recipes.

Install it with `npx -y @intellmedia/basecoat-ui-mcp` in the client configuration, install the package globally with npm, or build it from source. Node.js 22.14.0 or newer is required, and the client must launch the server over local stdio.

Set the project root with the `--project-root` argument, using an absolute application path. The argument takes precedence over `BASECOAT_PROJECT_ROOT`, which takes precedence over the launch directory. The root controls project context and persistent design-session storage.

Yes, it runs without runtime network requests. The server reads its packaged registry locally and communicates with the MCP client over stdio, although the host application remains responsible for its own runtime services and data access.

No, its composition validator performs static checks on HTML or Astro source and does not render, execute, resolve application modules, or certify accessibility. It accepts up to 256 KiB of source and returns at most 24 issues.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewBasecoat UI MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/basecoat-ui-mcp?style=directory)](https://allmcps.com/mcp/basecoat-ui-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/basecoat-ui-mcp"><img src="https://allmcps.com/api/badge/basecoat-ui-mcp?style=directory" alt="Basecoat UI MCP on AllMCPs" /></a>