⌘K

Boost

MCP Server & Tools

The wire-boost MCP server and the tools it exposes to AI agents.

On this page

Wire Boost provides an MCP server built on Laravel MCP. It is registered under the local handle wire-boost and started with:

php artisan wire-boost:mcp

Agents normally start it for you from the configuration written by wire-boost:install.

WireStack tools

These are the reason to use Wire Boost — they let an agent inspect your actual wire components and the component vocabulary.

Tool Description
application-info PHP / Laravel / Livewire versions, installed wire package versions, and key effective config.
list-wire-components Discover the app Livewire components that build a wire table, form, or infolist.
describe-table Resolve a table's columns, filters, header/row/bulk actions, default sort, and searchability.
describe-form Resolve a form's flattened field schema (name, label, type, wrapping layout).
describe-infolist Resolve an infolist's entry schema.
validate-wire-component Build a component and report unknown colors, unregistered icons, and names the model cannot resolve.
list-component-types List the built-in types for a category: columns, filters, fields, actions, infolist-entries, panel-entries, widgets, modals, layouts.
describe-component-api List the public fluent API of a component type — signatures, defaults, and the values each parameter accepts (an FQCN or a short name like badge-column).
list-icons Icon names registered with the wire IconManager (for ->icon()).
wire-config The effective wire-* configuration, or a single dotted key.
search-wire-docs Search the full wireStack documentation and return the most relevant sections.
fetch-wire-doc Read a documentation section (or a document outline) in full, by id.

Example

Asking an agent to add a status column to a table typically goes:

  1. list-component-types with category: columns → sees badge-column exists.
  2. describe-component-api with class: badge-column → learns ->color() and the colors it accepts.
  3. describe-table on your component → matches the existing column conventions.
  4. Writes BadgeColumn::make('status')->color(...).
  5. validate-wire-component on your component → confirms the color, icon and attribute all resolve.

The entire English documentation ships inside the package — not a summary of it — so the tools work in your app without network access or a checkout of the wire repo.

search-wire-docs indexes it by section, not by file, and ranks with BM25 plus a bonus for terms that match a section's heading or its document title. A result carries an id, a breadcrumb (BadgeColumn > Badge Colors), the owning package and a snippet:

{
  "id": "docs/table/columns/badge.md#badge-colors",
  "breadcrumb": "BadgeColumn > Badge Colors",
  "package": "wire-table",
  "score": 25.13,
  "snippet": "Set the pill colour with the color helper."
}

Pass that id to fetch-wire-doc to read the section in full. Passing a document id (docs/table/columns/badge.md) returns its outline instead — whole pages run to tens of kilobytes, so an outline plus targeted section fetches is cheaper and more accurate. Add full: true for the entire page.

Filter by package with package: wire-table (the wire- prefix is optional). Add your own Markdown to the index with wire-boost.docs.paths; see Configuration.

Validation

validate-wire-component exists because the three most common faults in generated wire code do not throw, so a test that asserts the component renders stays green:

Fault What actually happens
->color('bleu') Color::resolve() falls back to gray — the badge just renders gray.
->icon('heroicon-nope') Nothing renders where the icon should be.
TextColumn::make('titel') The cell renders blank.

The tool builds the component, then checks it against the canonical vocabularies — the Color enum, the registered IconManager names, and the model's real attributes (columns, casts, $appends, accessors and relation paths). Each finding names the target and suggests the near miss:

{
  "severity": "warning",
  "rule": "unknown-attribute",
  "target": "columns.titel",
  "message": "[posts] has no attribute [titel]; it will render blank.",
  "suggestions": ["title"]
}

Attribute checks need a reachable database table; without one they are skipped (reported as such) rather than guessed at. Columns that compute their own value via ->state() are never flagged.

General tools (Laravel Boost parity)

Tool Description
database-schema Tables and columns, optionally for one table or connection.
database-connections Configured connections and the default.
database-query Execute a read-only SELECT (disabled by default).
last-error The most recent error from the log file.
read-log-entries The last N log lines.
get-absolute-url Convert a relative path to an absolute URL.
list-artisan-commands Available Artisan commands and descriptions.
list-routes Application routes with methods, URI, name, and action.
tinker Evaluate PHP in the app context (disabled by default).
browser-logs Recent browser console entries from the configured log file.

Safety

database-query and tinker execute code or read arbitrary data, so they are off by default. Enable them explicitly:

WIRE_BOOST_DATABASE_QUERY=true
WIRE_BOOST_TINKER=true

See Configuration for the full wire-boost config reference.