Blatui

io.github.anousss007Published by GitHub account anousss007v1.0.0Updated Nov 9, 2026

shadcn/ui for Laravel Blade — discover, read and install BlatUI components, blocks and charts.

VerifiedStreamable HTTPWeb executableDeveloper ToolsMedia & Design

Overview

AI-generated overview

BlatUI registry server that lets an assistant find, read and install Laravel Blade UI components, blocks and charts.

What you can do
  • List BlatUI components with titles and one-line descriptions, optionally filtered by category
  • Search components, blocks and charts by name, title or description
  • Read a component's full Blade source, dependencies, required packages and install command
  • Read the full Blade source of a block or chart plus the components and packages it needs
  • Build the exact php artisan blatui:add command with required composer and npm packages for chosen components
When to use it
Useful when building or extending a Laravel app with the BLAT stack (Blade, Laravel, Alpine, Tailwind) and you want the assistant to pull in ready-made, accessible UI components, blocks or charts with correct dependencies instead of writing markup from scratch.
Requirements
A remote MCP endpoint; no authentication, environment variables or headers are declared. The components it returns target projects with PHP 8.2+, Laravel 11-13, Tailwind CSS v4, Alpine.js 3 and Node 18+, plus the BlatUI composer package and peer packages.
Before you install
The server only serves registry content, but the install commands it produces add packages and copy files into your project, so review them before running. Components are copied into your codebase and are yours to maintain; upgrades are manual and can overwrite customized files unless you check diffs.

Installation

In SourceWeft

  1. Open Blatui in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.anousss007%2Fblatui/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "blatui": {
      "type": "http",
      "url": "https://blatui.remix-it.com/mcp"
    }
  }
}

README

BlatUI

shadcn/ui for the BLAT stack — Blade · Laravel · Alpine · Tailwind

A CLI that copies open-source, copy-paste UI components you own straight into your Laravel project.

[Latest Version] [CI] [License] [Accessibility: WCAG AA]

155 components · 614 variants · 64 blocks · 70 charts · accessible (WCAG AA) · Livewire-ready · fully themeable · light + dark · MIT

Live demo & docs → blatui.remix-it.com

🧩 This is the BlatUI monorepo. The Composer package is the repo root (src/ + stubs/) — Packagist reads it directly, so composer require anousss007/blatui is unchanged and the apps/ are stripped from the dist tarball. Components are authored in apps/demo/ and generated into stubs/. See Contributing before editing a component.


Why BlatUI

  • Accessible by default. WAI-ARIA roles, complete keyboard navigation & focus management, and WCAG AA color contrast — modeled on shadcn/ui's Base UI behavior, verified in a real browser and audited with axe-core. Accessibility isn't an add-on; it ships in every component.
  • You own the code. Components are copied into your project — not hidden in vendor/. Edit them however you like; updating the package never overwrites your edits.
  • The BLAT stack. Pure Blade components, a sprinkle of Alpine.js for interactivity, Tailwind CSS v4 for styling. No React, no build-step lock-in.
  • Livewire-ready. wire:model works on every form control — inputs, selects, checkboxes, switches, sliders, date/time pickers, file uploads and more — with full two-way binding. A free, you-own-the-code alternative to Flux Pro. See the Livewire guide →
  • Faithful to shadcn/ui. Same design language, component APIs and blocks — ported to the Laravel way.
  • Themeable to the core. Every token is a CSS variable.

Requirements

  • PHP 8.2+ · Laravel 11, 12 or 13
  • Tailwind CSS v4 · Alpine.js 3 · Node 18+

Installation

bash
# 1. Install the CLIcomposer require anousss007/blatui
# 2. Peer packages used by the componentscomposer require gehrisandro/tailwind-merge-laravel mallardduck/blade-lucide-iconsnpm install -D alpinejs @alpinejs/anchor @floating-ui/dom @alpinejs/collapse @alpinejs/focus
# 3. Publish the foundations (theme tokens + Alpine/chart/calendar engine)php artisan vendor:publish --tag=blatui-foundations#   → resources/css/blatui.css      (oklch design tokens, presets, light/dark)#   → resources/js/blatui.js        (greenfield bootstrap — boots Alpine for you)#   → resources/js/blatui-core.js   (engine: registerBlatUI, for apps already running Alpine)
# 4. Verify your setupphp artisan blatui:init

Point your two Vite entrypoints at the published foundations — replace each file's contents:

css
/* resources/css/app.css */@import "./blatui.css";
js
// resources/js/app.jsimport "./blatui.js";

blatui.css brings Tailwind, the design tokens and the @theme mapping; blatui.js boots Alpine + its plugins and lazy-loads ApexCharts. Run blatui:init to confirm everything (packages, tokens, imports) is wired up.

The foundations are published once and become yours — tweak the tokens, drop the chart engine if you don't need charts, etc. blatui:init will tell you what's still missing.

Installing into an existing project

Everything is additive — you don't replace your files.

  • Tailwind v4 is required. BlatUI uses v4-only features (@theme inline, oklch). On Tailwind v3, migrate first with npx @tailwindcss/upgrade; blatui:init detects the version.
  • CSS: add @import "./blatui.css"; to your existing app.css, below @import "tailwindcss";.
  • JS — already running Alpine? Don't import blatui.js (it would boot a second Alpine). Register BlatUI into your own instance instead, before you start it:
js
import Alpine from 'alpinejs'import { registerBlatUI } from './blatui-core.js'
registerBlatUI(Alpine)   // plugins + theme store + chart/calendar engineswindow.Alpine = AlpineAlpine.start()
  • JS — using Livewire or Flux? Livewire bundles and starts Alpine for you, so don't npm install alpinejs (that's the duplicate-Alpine trap) and don't import blatui.js. Install only the plugins — npm install -D @alpinejs/anchor @floating-ui/dom @alpinejs/collapse @alpinejs/focus (add apexcharts only if you use charts) — and register BlatUI onto Livewire's Alpine via the alpine:init hook:
js
import { registerBlatUI } from './blatui-core.js'
document.addEventListener('alpine:init', () => {    registerBlatUI(window.Alpine)})

BlatUI registers a theme store for dark mode. If Flux already drives dark mode, pass registerBlatUI(window.Alpine, { darkMode: false }) so the two don't both toggle .dark.

Adding components

bash
# Add one or more — dependencies are resolved automaticallyphp artisan blatui:add button card input
# See everything you can add — components, blocks & chartsphp artisan blatui:list
# Details for a single componentphp artisan blatui:list select
# Everything at oncephp artisan blatui:add --all

Components land in resources/views/components/ui/ as Blade tags:

blade
<x-ui.card class="max-w-sm">    <x-ui.card-header>        <x-ui.card-title>Welcome back</x-ui.card-title>        <x-ui.card-description>Sign in to continue.</x-ui.card-description>    </x-ui.card-header>    <x-ui.card-content class="space-y-3">        <x-ui.input type="email" placeholder="[email protected]" />        <x-ui.button class="w-full">Sign in</x-ui.button>    </x-ui.card-content></x-ui.card>

blatui:add prints any extra composer/npm packages a component needs (e.g. charts pull in apexcharts).

Keeping components up to date

You own the copied files, so an upgrade is never automatic — blatui:update shows you what changed and lets you decide, file by file:

bash
# What would change across everything you have installed?php artisan blatui:update --dry-run --diff
# Update, confirming each file that differs from the version we shipphp artisan blatui:update
# Just these families, no questions asked (your version is kept as .bak)php artisan blatui:update button card --force

A file that differs is either your customisation or an outdated copy — nothing on disk tells the two apart, so BlatUI never overwrites one without showing the diff and asking. --force still writes a .bak next to each file it replaces (opt out with --no-backup). Files a family gained in a newer release are simply added.

Running Pint or Prettier over resources/views? Your formatter rewrites the layout of every component you copied, and all of them then read as changed. They are counted separately as same content, reformatted, and --ignore-whitespace leaves them out:

bash
php artisan blatui:update --dry-run --ignore-whitespace

The CSS/JS foundations are published, not copied — re-sync those with vendor:publish --tag=blatui-foundations --force; blatui:init tells you when the engine has fallen behind.

Blocks & charts

Blocks (dashboards, sidebars, login pages…) and the 70 charts are copy-paste from the demo site — they're full-page compositions, not primitives, so you grab the exact source you want rather than installing it:

👉 Browse blocks & charts on the live demo

Commands

CommandDescription
blatui:initDoctor — checks packages, Tailwind v4, theme tokens, Alpine/engine wiring
blatui:list [component]List all component families, or detail one
blatui:add <components...>Copy components (+ deps) into your project
blatui:update [components...]Diff installed components against this version and update them (--dry-run, --diff, --force, --ignore-whitespace)
blatui:doctor [path]Scan your Blade for known footguns (typeless buttons in forms, leaked tags)
blatui:mcpRun the MCP server (stdio) so an AI editor can search and install components
vendor:publish --tag=blatui-foundationsPublish theme CSS + JS engine

Contributing

BlatUI is a monorepo — one repo, one PR, one CI. The Composer package is the repo root; the demo/docs site and starter kit are apps that live alongside it (excluded from the published package via .gitattributes).

composer.json  src/  stubs/   → the published package (this is what `composer require` gets)apps/demo/                     → authors AND renders every component; the live docs siteapps/starter/                  → the Laravel starter kitscripts/build-package.sh       → regenerates stubs/ from apps/demo (CI enforces it)

Components are authored in apps/demo/resources/views/components/ui/ (the only place they render, so it's the source of truth); stubs/ is generated — don't hand-edit it. After changing a component, run bash scripts/build-package.sh and commit both. CI fails if they drift. Full guide: CONTRIBUTING.md.

Credits

BlatUI is a port of shadcn/ui to the Laravel/Blade ecosystem. Thanks to shadcn and contributors. Icons by Lucide. Charts by ApexCharts.

License

MIT — free for personal and commercial use.

Source: README.md at commit f4e4297

Tools

5

list_components

List every BlatUI component with its title and one-line description. Optionally filter by category.

Parameterscategory

search_registry

Search BlatUI components, blocks and charts by name, title or description.

Parameterstypequeryrequired

get_component

Get a component's full Blade source, dependencies, required packages and install command.

Parametersnamerequired

get_example

Get the full Blade source of a block or chart, plus the components and packages it needs.

Parameterskindrequirednamerequired

install_command

Build the exact `php artisan blatui:add` command plus required composer/npm packages for one or more components.

Parametersnamesrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.