list_components
List every BlatUI component with its title and one-line description. Optionally filter by category.
category
io.github.anousss007由 GitHub 账号 anousss007 发布v1.0.0更新于 Nov 9, 2026
shadcn/ui for Laravel Blade — discover, read and install BlatUI components, blocks and charts.
BlatUI 组件注册表服务器,让助手查找、阅读并安装 Laravel Blade 的 UI 组件、区块和图表。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.github.anousss007%2Fblatui/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"blatui": {
"type": "http",
"url": "https://blatui.remix-it.com/mcp"
}
}
}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
🧩 This is the BlatUI monorepo. The Composer package is the repo root (
src/+stubs/) — Packagist reads it directly, socomposer require anousss007/blatuiis unchanged and theapps/are stripped from the dist tarball. Components are authored inapps/demo/and generated intostubs/. See Contributing before editing a component.
vendor/. Edit them however you like; updating the package never overwrites your edits.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 →Point your two Vite entrypoints at the published foundations — replace each file's contents:
blatui.cssbrings Tailwind, the design tokens and the@thememapping;blatui.jsboots Alpine + its plugins and lazy-loads ApexCharts. Runblatui:initto 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:initwill tell you what's still missing.
Everything is additive — you don't replace your files.
@theme inline, oklch). On
Tailwind v3, migrate first with npx @tailwindcss/upgrade; blatui:init detects the version.@import "./blatui.css"; to your existing app.css, below @import "tailwindcss";.blatui.js (it would boot a second Alpine).
Register BlatUI into your own instance instead, before you start it: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: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.
Components land in resources/views/components/ui/ as Blade tags:
blatui:add prints any extra composer/npm packages a component needs
(e.g. charts pull in apexcharts).
You own the copied files, so an upgrade is never automatic — blatui:update
shows you what changed and lets you decide, file by file:
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:
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 (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
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).
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.
BlatUI is a port of shadcn/ui to the Laravel/Blade ecosystem. Thanks to shadcn and contributors. Icons by Lucide. Charts by ApexCharts.
MIT — free for personal and commercial use.
来源:README.md,提交 f4e4297
List every BlatUI component with its title and one-line description. Optionally filter by category.
categorySearch BlatUI components, blocks and charts by name, title or description.
typequery必填Get a component's full Blade source, dependencies, required packages and install command.
name必填Get the full Blade source of a block or chart, plus the components and packages it needs.
kind必填name必填Build the exact `php artisan blatui:add` command plus required composer/npm packages for one or more components.
names必填已满足适用检查项的 90%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
请在仓库或注册中心条目中声明许可证。
# 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/* resources/css/app.css */@import "./blatui.css";// resources/js/app.jsimport "./blatui.js";import Alpine from 'alpinejs'import { registerBlatUI } from './blatui-core.js'
registerBlatUI(Alpine) // plugins + theme store + chart/calendar engineswindow.Alpine = AlpineAlpine.start()import { registerBlatUI } from './blatui-core.js'
document.addEventListener('alpine:init', () => { registerBlatUI(window.Alpine)})# 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<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># 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 --forcephp artisan blatui:update --dry-run --ignore-whitespacecomposer.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)