Application InfoLABSCO SUMMARY
Stops the agent guessing — both at your application and at Laravel.
Two halves work together: the MCP tools let an agent inspect the running application, from schema and models to the last error and the browser's own logs, while the docs tool answers Laravel questions from a knowledge base scoped to the package versions actually installed. Guidelines load upfront, so the conventions are in context before the first line is written.
What it is
A dev-dependency package that installs an MCP server plus AI guidelines and agent skills into a Laravel application. php artisan boost:install writes the MCP configuration and the guideline files for the agents you select.
What you get
- Application Info — PHP and Laravel versions, the database engine, ecosystem packages with versions, and your Eloquent models
- Database Connections, Database Schema and Database Query — inspect the connections, read the schema, run a query
- Last Error and Read Log Entries, taken from the application's own log files
- Browser Logs — logs and errors from the browser
- Get Absolute URL, so relative paths become URLs that actually resolve
- Search Docs — a hosted documentation API over more than 17,000 pieces of Laravel-specific information, with semantic search scoped to the packages you have installed
- AI guidelines for the ecosystem: the framework, Livewire, Inertia, Flux UI, Folio, Herd, Pennant, Pest, PHPUnit, Pint, Sail, Tailwind CSS, Volt and Wayfinder
Requirements
A Laravel application and Composer: composer require laravel/boost --dev, then php artisan boost:install. The server itself runs as php artisan boost:mcp over stdio, and php artisan boost:update refreshes guidelines and skills as your packages move.
Setup effort
Follow the published steps — composer require laravel/boost --dev
USE CASES
01
Debugging what just broke
Read the last error from the log, pull the surrounding entries, and check the browser's logs for the client half.
02
Writing a query against a schema the agent has never seen
Inspect the available connections, read the schema, then run the query and get the rows back.
03
Getting the current answer instead of a remembered one
The docs tool searches a knowledge base scoped to your installed packages, so the pattern it suggests matches the version you actually run.
04
Keeping generated code in house style
Guidelines for the framework and each ecosystem package load upfront; add your own under .ai/guidelines/ and they are included on the next boost:install.
05
Getting URLs that resolve
Relative paths are converted to absolute, so the agent stops emitting links that go nowhere.
9 tools
Listed in project docs. Your client may show a different list.
Browser LogsDatabase ConnectionsDatabase QueryDatabase SchemaGet Absolute URLLast ErrorRead Log EntriesSearch DocsBEFORE YOU INSTALL
What to know first
Tools you get
9 tools named in the project's documentation. These nine come from older documentation. Laravel's product page advertises 15 tools, including Tinker, Artisan command, route and configuration tools, so expect more. Boost's Agent Skills and AI Guidelines are not MCP tools.
INSTALLATION
Connect your client
Server setup
TERMINAL
composer require laravel/boost --dev
php artisan boost:install # installs the MCP server + coding guidelines and writes .mcp.json / CLAUDE.md / AGENTS.md / boost.jsonIn your editor, enable the generated laravel-boost MCP server (or run the client-specific add command, e.g. claude mcp add -s local -t stdio laravel-boost php artisan boost:mcp)
MCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add -s local -t stdio laravel-boost php artisan boost:mcpCodex
CODEX · TERMINAL
codex mcp add laravel-boost -- php "artisan" "boost:mcp"Gemini CLI
GEMINI CLI · TERMINAL
gemini mcp add -s project -t stdio laravel-boost php artisan boost:mcpAny MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"laravel-boost": {
"command": "php",
"args": [
"artisan",
"boost:mcp"
]
}
}
}
