livewire-flux-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_flux_docsA | Fetch documentation for Livewire Flux components or layouts from fluxui.dev |
| list_flux_componentsB | List all available Flux components from the documentation |
| list_flux_layoutsB | List all available Flux layouts from the documentation |
| list_flux_component_iconsA | List all available Heroicons for use with flux:icon component, with variants and usage examples |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct action: fetching docs, listing components, listing layouts, and listing icons. No overlap in purpose.
All tools use snake_case with a consistent verb_flux_noun pattern. The icon tool is slightly longer but still follows the same style.
Four tools is well-scoped for a documentation explorer: list components, layouts, icons, and fetch details. Each tool earns its place.
The set covers browsing all available resources (components, layouts, icons) and retrieving their documentation. No obvious gaps for the stated purpose.