MCP server

Basecoat UI MCP: Offline shadcn Look Without React for AI Agents

Basecoat UI MCP is an offline server that gives an AI coding agent 41 Basecoat templates, layout blocks and a validator for plain HTML, Astro and Next.js pages.

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

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is Basecoat UI MCP?

Basecoat UI MCP is a local stdio server for Basecoat UI, the shadcn/ui look built without React. It serves curated component templates, macro layout blocks, rhythm and theming rules, and a static validator, all offline, so an AI coding agent assembles Astro, Next.js or HTML pages from known parts.

Basecoat UI MCP is an offline Model Context Protocol server for Basecoat UI, which gives the shadcn/ui look without React. Instead of scraping documentation, the agent queries a fixed registry of templates, layout blocks and rules for Astro, Next.js, HTML and Tailwind CSS 4.

It runs over local stdio with zero runtime network requests. Every macro and semantic response is bounded to 1,999 UTF-8 bytes, and larger result sets come back through cursors, so a reply is never cut off in the middle of JSON.

What changes in your agent's output

  • Pages are built from 41 curated templates, from accordion and alert through card, chart, checkbox and combobox, instead of hand-written markup.
  • Layouts come from named blocks such as app-shell, auth-sign-in and pricing-tiers, plus six multi-block recipes like workspace-dashboard.
  • Spacing, type and surface choices follow rhythm rules, with the semantic token kept apart from the approved Tailwind utility.
  • Generated Astro or HTML is checked by validate_composition before you review it.

Design sessions and validation

  1. Call begin_design to open a persistent session that pins its profile and registry revision.
  2. Instantiate a recipe with apply_design_patch, passing an expectedRevision and an idempotent operationId.
  3. Write the component leaves in your own project, then record finished regions with record_written.
  4. Finish with validate_design in complete mode and validate_composition on the generated source.

Who it is for

Best for

  • Astro, Next.js and plain HTML projects on Tailwind CSS 4 without a React runtime. Related: shadcn-mcp.
  • Teams that keep a DESIGN.md, which the server reads on demand through basecoat://project/context. Related: design-md.
  • Agents that need a repeatable theming contract, including all 8 style packs and class based dark mode.

Not for

  • Anyone who wants React components. The README positions Basecoat as the no React route.
  • Projects that need runtime behavior from the server. The host application owns rendering, data, authentication and sessions.
  • Accessibility certification. The validator does not render, execute code or certify accessibility.

Use it with UiChemy

Basecoat output is plain HTML and Tailwind, so it carries over to WordPress more easily than React does. UiChemy's AI to WordPress imports an AI build, and Composer edits it inside Elementor or Gutenberg. Click Get Started on uichemy.com.