Tune it live. Every preset is pure CSS variables.
"Default" follows the body font.
Copy your complete theme and paste it as your resources/css/app.css — the Tailwind import, every token and the @theme mapping are all included, so it works as-is.
Connect the BlatUI MCP server and your agent can search, read and install components, blocks and charts — straight into your Laravel project. Works with Claude Code, Cursor, VS Code, Windsurf, Codex and any MCP client.
Use the hosted server for zero-install discovery, or the local one to read components straight from your project.
One public, stateless endpoint. Point any MCP-capable editor at it — the URL never changes:
https://blatui.remix-it.com/mcp
Pick your editor — same server, slightly different config file:
claude mcp add -t http blatui https://blatui.remix-it.com/mcp
{
"servers": {
"blatui": { "type": "http", "url": "https://blatui.remix-it.com/mcp" }
}
}
VS Code 1.101+. Note the key is servers (not mcpServers). You can also run the MCP: Add Server command and pick HTTP.
{
"mcpServers": {
"blatui": { "url": "https://blatui.remix-it.com/mcp" }
}
}
[mcp_servers.blatui]
url = "https://blatui.remix-it.com/mcp"
Or run codex mcp add. TOML, not JSON.
{
"mcpServers": {
"blatui": { "serverUrl": "https://blatui.remix-it.com/mcp" }
}
}
Windsurf uses serverUrl for remote servers.
{
"mcpServers": {
"blatui": { "type": "streamable-http", "url": "https://blatui.remix-it.com/mcp" }
}
}
Streamable HTTP transport. Some clients label the type http — both point at the same endpoint.
Prefer to serve component source straight from your own copy (offline-friendly)? Install the package, then point any editor at the stdio server. Install once:
composer require anousss007/blatui
Register php artisan blatui:mcp with your editor. In Claude Code:
claude mcp add -s local -t stdio blatui php artisan blatui:mcp
Every other editor — same config file as above, but a command/args pair instead of a URL:
{
"mcpServers": {
"blatui": { "command": "php", "args": ["artisan", "blatui:mcp"] }
}
}
VS Code nests it under servers; Codex uses [mcp_servers.blatui] with command + args — same idea, local stdio.
The server exposes tools, resources and prompts.
search_registrylist_componentsget_componentget_exampleinstall_commandRead any item's Blade source by URI:
blatui://component/{name}blatui://block/{name}blatui://chart/{name}use-componentscaffold-pageBlatUI ships first-class Laravel Boost guidelines and an agent skill. If your project uses Boost, your AI already knows how to use BlatUI — no extra setup. Install Boost and select the features:
composer require laravel/boost --dev
php artisan boost:install
Because anousss007/blatui ships
resources/boost/guidelines/core.blade.php and a
blatui-development skill, Boost loads BlatUI's conventions
(the x-ui. namespace, blatui:add,
theming) into your agent's context automatically. The BlatUI MCP server complements Boost — Boost knows
your app; BlatUI knows every component.
Everything the MCP server returns is also plain HTTP — usable from any script or agent:
curl https://blatui.remix-it.com/registry.json # every component, block, chart
curl https://blatui.remix-it.com/r/button.json # one item, Blade source inlined
curl https://blatui.remix-it.com/llms.txt # concise index for LLMs