BlatUI MCP
The BlatUI MCP server: an agent finds shadcn/ui-style Blade components, reads their code and installs them into a Laravel project.
- 264 ★ on the repository
- Last commit
Minimal access
Why this level
- Copies component files into a Laravel project and changes no application data.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/blatui-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- Copies component files into a Laravel project and changes no application data.
This is third-party code. Review the repository files before installing.
What it does
BlatUI is a shadcn/ui counterpart for the BLAT stack: Blade, Laravel, Alpine and Tailwind. A command-line tool copies components, blocks and charts into a Laravel project as plain source code that you own, and package updates never overwrite your edits. Components are plain Blade with a little Alpine.js, work with Livewire and support light and dark themes. The MCP server starts with `php artisan blatui:mcp` over stdio, and the hosted variant answers at `https://blatui.remix-it.com/mcp` over Streamable HTTP. Through it an AI editor searches and installs components, blocks and charts. Alongside are `blatui:init` for checking the setup and `blatui:doctor`, which scans Blade for known pitfalls such as typeless buttons inside forms.
Who it is for. Laravel 11–13 developers on Tailwind v4 and Alpine who build an interface with an agent from ready accessible components without React.
Good fit when
- An agent picks a dialog, a table and a chart and installs them into the project `resources/views`.
- A Livewire form needs fields with two-way `wire:model` binding.
- Before handoff a page is checked with `blatui:doctor` for typical Blade mistakes.
- A team changes the theme tokens in CSS variables for a brand style.
Not a fit when
- The project is not on Laravel or uses React or Vue.
- Tailwind v3 is installed, while the components use version 4 features only.
- You need a ready library with no copying of sources into the project.
Example request
Find a dropdown menu component and a sortable table in BlatUI, install them into the project and check the page with blatui:doctor.MCP
- Transport
- stdio, http
- Authentication
- not required
Limitations
It needs PHP 8.2 or newer, Laravel 11, 12 or 13, Tailwind CSS v4, Alpine.js 3 and Node 18 or newer. Tailwind v3 is migrated first with `npx @tailwindcss/upgrade`. In a project with Livewire or Flux do not install `alpinejs` separately and do not import `blatui.js`: Livewire starts Alpine itself, and otherwise you get a duplicate Alpine. Base styles and the chart engine are published with `vendor:publish --tag=blatui-foundations`. The license is stated as MIT, while the repository metadata does not define it.
How to disable. Remove the blatui entry from the MCP configuration and the package with `composer remove anousss007/blatui`. Copied components stay in the project as your code.
FAQ
How do I install BlatUI in a project?
Run `composer require anousss007/blatui`, then install `gehrisandro/tailwind-merge-laravel` and `mallardduck/blade-lucide-icons` and `alpinejs` with plugins through npm. After that run `php artisan vendor:publish --tag=blatui-foundations` and `php artisan blatui:init`.
How do I start the MCP server?
Locally with `php artisan blatui:mcp` over stdio. The hosted variant is available at `https://blatui.remix-it.com/mcp` over Streamable HTTP.
What does `blatui:doctor` do?
It scans Blade for known pitfalls such as typeless buttons in forms and leaked tags. The directory path is passed as an argument.
Do the components work with Livewire?
Yes, `wire:model` works on inputs, selects, checkboxes, switches, sliders, date and time pickers and file uploads with two-way binding.
Is Tailwind v4 required?
Yes. The components use `@theme inline` and oklch colors that v3 lacks. `blatui:init` detects the version.
Discussion
No questions or reviews yet.
Related
MCP serversThe hosted Watermelon UI MCP searches free React and Tailwind components, blocks and dashboards and returns source code.
An MCP server that gives agents MudBlazor docs: components, parameters, examples and the API of your exact version.
MCP server for the UI Beats catalog of animated React components: search, props, source code and install command for an agent
Shadcn UI MCP Server
Shadcn UI v4 MCP Server
An MCP server that gives the agent shadcn/ui component source, demos and blocks for React, Svelte, Vue and React Native
A skill and MCP server for the spartan/ui Angular library: the agent installs components and blocks from current docs.
21st.dev MCP server and plugin: search ready React/Tailwind components and logos and generate UI from your agent
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| BlatUI MCP (this card) | yes | not required | 264 | |
| Shadcn UI MCP Server | no | key is optional | 3,096 | serves shadcn/ui sources for React, Svelte and Vue; BlatUI MCP installs Blade components for Laravel on Alpine |
| Laravel Boost | yes | not required | 3,688 | the official Laravel MCP with database schema and documentation; BlatUI MCP adds ready interface components |
README in short
The BlatUI repository is a monorepo: the Composer package sits at the root, while the demo site and starter kit are in `apps`. Components are authored in the demo app and moved to `stubs/` by a build script.