Aura UI is an MCP server published by io.github.BlueStarSystem, hosted at aura-ui.com. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 5 tools, including list-components-tool, search-components-tool, get-component-tool, add-component-tool, filament-theme-tool.
Discover and install Aura UI Blade components for Laravel, Livewire and Tailwind CSS 4.
Nothing else in the archive shares these values.
Inferred from the host name and headers: what a server runs on, not who runs it.
List all available Aura UI components (free and Pro), with their Blade tag, tier, and a one-line description. Use this to discover what UI components exist before writing markup.
| Parameter | Type | Description |
|---|---|---|
| tier | string | Optional. Filter components by tier: "free" or "pro". |
{
"name": "list-components-tool",
"title": "List Components Tool",
"description": "List all available Aura UI components (free and Pro), with their Blade tag, tier, and a one-line description. Use this to discover what UI components exist before writing markup.",
"inputSchema": {
"type": "object",
"properties": {
"tier": {
"enum": [
"free",
"pro"
],
"type": "string",
"description": "Optional. Filter components by tier: \"free\" or \"pro\"."
}
}
},
"annotations": {}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Search Aura UI components by keyword (matches name, title and description). Returns matching components with their Blade tag and tier. Use this when you need a component for a purpose, e.g. "date", "table", "notification".
| Parameter | Type | Description |
|---|---|---|
| query * | string | Keyword(s) to search for across component names and descriptions. |
{
"name": "search-components-tool",
"title": "Search Components Tool",
"description": "Search Aura UI components by keyword (matches name, title and description). Returns matching components with their Blade tag and tier. Use this when you need a component for a purpose, e.g. \"date\", \"table\", \"notification\".",
"inputSchema": {
"type": "object",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"description": "Keyword(s) to search for across component names and descriptions."
}
}
},
"annotations": {}
}Get full details for a single Aura UI component by name (e.g. "button", "date-picker"): its Blade tag, tier, a copy-pasteable usage example, and the complete Markdown documentation including all props. Call this before generating Aura markup for a component.
| Parameter | Type | Description |
|---|---|---|
| name * | string | The component name, e.g. "button", "modal", "date-picker". |
{
"name": "get-component-tool",
"title": "Get Component Tool",
"description": "Get full details for a single Aura UI component by name (e.g. \"button\", \"date-picker\"): its Blade tag, tier, a copy-pasteable usage example, and the complete Markdown documentation including all props. Call this before generating Aura markup for a component.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "The component name, e.g. \"button\", \"modal\", \"date-picker\"."
}
}
},
"annotations": {}
}Get everything needed to install an Aura UI component or block into a Laravel project: the `php artisan aura:add` command, the resolved transitive dependency tree, the file list, and (optionally) the Blade source of each file. Call this when you are ready to install a component you found via list/search/get.
| Parameter | Type | Description |
|---|---|---|
| name * | string | The component or block name, e.g. "button", "date-picker", "hero-split". |
| with_source | boolean | Include the Blade source of each file (default true). |
{
"name": "add-component-tool",
"title": "Add Component Tool",
"description": "Get everything needed to install an Aura UI component or block into a Laravel project: the `php artisan aura:add` command, the resolved transitive dependency tree, the file list, and (optionally) the Blade source of each file. Call this when you are ready to install a component you found via list/search/get.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "The component or block name, e.g. \"button\", \"date-picker\", \"hero-split\"."
},
"with_source": {
"type": "boolean",
"description": "Include the Blade source of each file (default true)."
}
}
},
"annotations": {}
}Describe the Aura Filament theme: the design presets available for a Filament v4/v5 admin panel, plus the documentation topics covering install, layout modes, custom form fields, table columns, dashboard widgets and email theming. Use this when the user is theming or building a Filament panel.
| Parameter | Type | Description |
|---|---|---|
| topic | string | Optional. A Filament documentation topic name, e.g. "presets", "widgets", "table-columns". |
{
"name": "filament-theme-tool",
"title": "Filament Theme Tool",
"description": "Describe the Aura Filament theme: the design presets available for a Filament v4/v5 admin panel, plus the documentation topics covering install, layout modes, custom form fields, table columns, dashboard widgets and email theming. Use this when the user is theming or building a Filament panel.",
"inputSchema": {
"type": "object",
"properties": {
"topic": {
"type": "string",
"description": "Optional. A Filament documentation topic name, e.g. \"presets\", \"widgets\", \"table-columns\"."
}
}
},
"annotations": {}
}Aura UI is a Blade component library for Laravel + Livewire + Alpine.js + Tailwind CSS 4. Use list-components to discover components, search-components to find one by purpose, and get-component to fetch the Blade tag, a usage example, and full docs before generating markup. Components are used as Blade tags like <x-aura::button>. Always prefer an Aura component over hand-written Tailwind markup. Use add-component to get the install command, dependencies, and source for a component.
Names, descriptions and schemas were written by the server and are shown as data.