Laravel Boost Is the Missing Piece Between AI Coding Tools and Real Laravel Apps

Laravel finally shipped something I've wanted since the "vibe coding" wave got serious: a first-party way for AI agents to see your Laravel app the way a senior teammate would.

It's called Laravel Boost. And if you write Laravel for a living, and you already use Cursor, Claude Code, Copilot, or another MCP-capable agent, this is worth a careful look.

Claims below are checked against the Laravel Boost docs and the Boost overview as of 18 Sep 2026. Where marketing copy and docs differ, I follow the docs.

What Boost Actually Is

Boost is not another chat wrapper.

Per the official docs, it combines:

Install from Composer as a dev dependency, then run the installer:

composer require laravel/boost --dev
php artisan boost:install

Docs also document php artisan boost:update (and optional Composer post-update-cmd / --discover) so guidelines stay aligned with the packages you actually have installed.

MCP tools (from the docs)

The Laravel 13.x Boost docs list these MCP tools:

Note: the Boost marketing page mentions a broader set (for example route inspection, Artisan, and Tinker). I'm sticking to the documented MCP tool table above so this post doesn't overclaim.

In plain language: the agent stops inventing your folder structure and starts reading what the framework exposes.

Why This Matters More Than Another Model Release

I've written before about Cursor, Claude, Gemini, and "vibe coding." The pattern is familiar: models get better, demos look magical, then production reality shows up.

The weak point was never only "is the model smart enough?"

It was context.

Without app-aware context, AI will invent columns, miss tenant scoping, suggest patterns your codebase doesn't use, and confidently refactor the wrong layer.

Boost attacks that failure mode the way the docs describe it:

That's the difference between "AI that writes PHP" and "AI that writes your Laravel."

How I'd Use It on a Real Project

On a logistics or ERP-style Laravel codebase, I'd start small:

The infer-conventions skill is documented for brownfield apps: it sweeps the codebase and proposes rules from what the code already does, and it asks for approval before writing rules (unless you tell it otherwise). I'd review every proposed rule. Mixed patterns should stay mixed until the team decides, not until an agent averages them into something nobody owns.

The Parts That Make Me Careful

I'm optimistic. I'm not careless.

Database access is power. The docs explicitly include Database Schema and Database Query tools. On a machine with production credentials in .env, that is a governance problem, not a cool demo. Keep Boost on local/dev databases. Treat MCP like any other privileged local tooling.

Generated files vs. committed rules. Docs say .mcp.json, generated guideline files, and boost.json can be gitignored because they regenerate on boost:install / boost:update. Project rules under .ai/rules should be committed so the team shares them. That split matters: regenerate tooling config, version the decisions.

It won't save weak fundamentals. Boost makes agents more accurate about Laravel. It does not replace knowing why an N+1 query hurts, when a queue job should be idempotent, or how authorization should be structured. Same rule I keep repeating: AI without fundamentals just helps you ship debt faster.

Don't outsource architecture. Use Boost to accelerate boilerplate, tests, refactors, and doc lookups. Keep the hard trade-offs, boundaries, consistency, operational risk, in human hands.

Boost vs. "Just Paste More Context"

You can already dump schema.sql into chat. I've done it. It works until the dump is stale, the conversation is long, and the agent forgets half of it.

Boost is different because the tools are live and wired into the agent's loop, docs search is package-aware, rules persist across sessions and teammates, and skills load only when relevant (docs: reduces context bloat vs always-on guidelines).

That's the grown-up version of stuffing a README into every prompt.

Who Should Install It This Week

Install it if:

Wait (or sandbox carefully) if:

Closing Thoughts

Laravel Boost feels like Laravel doing what Laravel does best: removing friction without pretending the hard parts disappeared.

If AI coding tools made us architects instead of typists, Boost is one of the first official tools that gives those architects a map of the actual building, and the map is written down in the docs, not only in a launch tweet.

I'll be trying it on a real project soon, not for a demo, but for the boring wins: fewer hallucinated columns, better refactors, and rules the next agent won't forget.

If you've already wired Boost into Cursor or Claude Code, tell me what broke first. Those war stories are usually more useful than the launch posts.

Sources (checked 2026-09-18)