Comparison

Laravel MCP vs Boost vs a CMS MCP Server: Which You Need

By Lara Dashboard 5 views
Laravel MCP vs Boost vs a CMS MCP Server: Which You Need
Search for "Laravel MCP server" and you get three different things in the results. There is the official laravel/mcp package. There is Laravel Boost, which also runs an MCP server. And there are apps like CMSs that ship their own MCP server. They all use the same protocol, so it is easy to think they compete. They don't. They sit at different layers and solve different problems.
Here is the quick answer. Use laravel/mcp when you want to build an MCP server for your own Laravel app. Use Laravel Boost when you want a coding agent such as Claude Code or Cursor to understand your codebase while you develop. Use a CMS MCP server when you want an AI client to do content and admin work on a live site, like drafting posts or checking tickets. Many teams end up with all three, each in its own place.
A quick disclosure. We build Lara Dashboard, an MIT Laravel CMS that ships an MCP server. Our own repo uses all three layers, so we use it as the worked example. Package facts below come from the official Laravel docs and Packagist as of November 2026.

laravel/mcp is the toolkit, not a server you switch on

The laravel/mcp package is Laravel's official way to build MCP servers. It gives you base classes and routing. It does not give you any tools until you write them.
You install it with composer require laravel/mcp, then publish routes/ai.php with php artisan vendor:publish --tag=ai-routes. You create a server class with php artisan make:mcp-server, and add tools, resources and prompts with make:mcp-tool, make:mcp-resource and make:mcp-prompt. Each tool is a PHP class with a description, an input schema and a handle method.
Servers come in two shapes. A web server is registered with Mcp::web() and answers HTTP requests, so remote clients can reach it. A local server is registered with Mcp::local() and runs as an Artisan command that the AI client starts on your machine. For web servers, the docs describe Sanctum tokens, OAuth 2.1 through Passport, or your own middleware. Testing is covered too, with php artisan mcp:inspector and test helpers.
As of November 2026, the latest release on Packagist is v1.2.1, published 17 November 2026, under the MIT licence. It requires PHP 8.2 or newer and Laravel 12.41 or 13. The 1.x line is the current one, though older 0.x releases are still around.
Reach for laravel/mcp when you have a custom app and want AI clients to call a few of its actions. Think "look up an order", "create a refund request" or "list today's bookings". You decide the tools, the schemas and the permission checks.

Laravel Boost is a dev-time helper for your coding agent

Laravel Boost solves a different problem. It helps an AI coding agent write better Laravel code in your project. It is built on laravel/mcp, but you don't write any tools. It ships its own.
You install it as a dev dependency with composer require laravel/boost --dev, then run php artisan boost:install. The installer writes MCP config for your agent, adds Laravel guidelines to files like CLAUDE.md and AGENTS.md, and installs skills based on the packages in your composer.json. The docs list setup for Cursor, Claude Code, Codex, GitHub Copilot in VS Code and Junie.
Boost has three parts.
A local MCP server. Your agent starts it with php artisan boost:mcp. Its tools read your app's context: application info and package versions, database connections and schema, a database query tool, log entries, the last error, browser logs, absolute URLs, and a tool to record project rules.
Guidelines and skills. Guidelines load up front and cover Laravel, Livewire, Pest, Tailwind and other first-party packages. Skills load on demand when a task needs them.
A documentation search tool. Search Docs queries a hosted index of Laravel ecosystem docs, covering Laravel 10.x to 13.x and packages such as Livewire, Pest, Filament and Nova.
As of November 2026, the latest Boost release on Packagist is v2.10.4, published 29 October 2026, under the MIT licence.
The key point is the audience. Boost's users are you and your coding agent, on your laptop, while you build. It is a require-dev package. Its tools can read your schema and run database queries, which is exactly what you want locally and exactly what you don't want reachable on a production server.

A CMS MCP server is a finished product for site operations

A CMS MCP server sits at the other end. Someone has already written the tools, wired them to permissions and put them behind authentication. Its users are editors, marketers and support staff working through an AI client, on the live site.
Lara Dashboard's server is a good example because you can read the code. It is built on laravel/mcp and registered with Mcp::web('/mcp', ...) in routes/ai.php, behind Sanctum and an MCP agent token check. It is off by default, and you turn it on under Settings, then MCP. Core ships 25 tools for posts, terms, media, email templates, logs, cache, modules and a daily briefing. Modules add more through the filter.mcp.tools filter hook, which is how the CRM module adds contacts, deals and tickets. Since v1.5.0, Claude.ai can connect by URL through OAuth, as we covered in Lara Dashboard v1.5.0: Claude.ai OAuth MCP.
Every tool checks two things: the token must carry the right MCP ability, and the user behind it must hold the matching permission. If you are new to the idea, our plain-English guide to MCP servers for a CMS explains tools, tokens and OAuth in more detail.
A CMS MCP server is not for writing code. It does not know your schema or your logs in the way Boost does. It knows your content and your admin actions.

Side by side: three layers, three jobs

laravel/mcpLaravel BoostCMS MCP server
What it isToolkit to build serversDev helper with its own serverReady-made server inside an app
Who uses itDevelopers building featuresDevelopers and coding agentsEditors, marketers, support, ops
Where it runsWherever your app runsYour local machineYour live site
TransportWeb (HTTP) or local (stdio)Local (stdio)Web (HTTP)
ToolsThe ones you writeApp info, schema, queries, logs, docs searchPosts, media, terms, email, modules
Composerrequirerequire --devPart of the app
AuthSanctum, Passport OAuth or customNone needed locallyAgent tokens and OAuth
Latest (Nov 2026)v1.2.1v2.10.4Lara Dashboard v1.5.0
Read the table by row, not by column. These tools don't fight for the same slot. Boost helps you write the code. laravel/mcp is what that code uses to expose tools. A CMS MCP server is one finished result of doing that well.

Our repo uses all three, in different places

This is easiest to see in a real project. The Lara Dashboard repo on GitHub uses each layer for its own job.
laravel/mcp in require. The production MCP server at /mcp is a LaraDashboardServer class that extends Laravel\Mcp\Server. Each of the 25 core tools extends Laravel\Mcp\Server\Tool. Our develop branch still pins laravel/mcp to the 0.6 line as of November 2026, so moving to 1.x is on our list.
Laravel Boost in require-dev. The repo has a .mcp.json that starts php artisan boost:mcp for coding agents, and our CLAUDE.md contains Boost guidelines. Contributors get schema and docs context while they work. None of that ships to production sites.
The CMS server for site work. Once a site is live, a team can connect Claude or Cursor to /mcp with a limited user. The agent can draft posts, upload covers and read the daily briefing. It never sees the database directly. Our walkthrough on AI agents on your CMS with Cursor and Claude shows that flow.
If you build a module, the layers meet. You use Boost while you code it. You write MCP tools with laravel/mcp classes. Then you register them through the filter hook so they appear in the CMS server. Our post on Laravel hooks and filters shows the hook, and build a Laravel module step by step covers the module itself.

Trade-offs and when not to use each one

Each layer has a clear place, and each one goes wrong when you use it outside that place.
Don't expose Boost on a server. Boost's tools read your schema and logs and can run database queries. Keep it in require-dev, install production with composer install --no-dev, and don't point a remote client at it.
Don't build from scratch what already exists. If your app is a CMS or admin panel, writing 25 tools, a permission map, token management and OAuth yourself is a lot of security-sensitive work. laravel/mcp makes it possible, not small.
Don't use a CMS server as a coding agent. A CMS MCP server is for content and admin actions. It won't tell your agent about migrations or failing tests. That is Boost's job.
When not to use Lara Dashboard. If your product is not content-shaped and you only need three tools on top of an existing app, plain laravel/mcp in that app is simpler. If you already run another CMS that your team likes, check whether it has an MCP server before you switch. And if nobody on your team uses an AI client day to day, none of these layers is urgent.
The protocol still moves. MCP revisions keep changing details like sessions and client registration. Whichever layer you use, budget time to follow package updates over the next year.

Self-check: which one do you need?

  1. Do you want a coding agent to understand your Laravel project while you build? Install Laravel Boost as a dev dependency.
  2. Do you want AI clients to call a few actions in your own custom app? Build a server with laravel/mcp.
  3. Do you want editors or support staff to work on a live site through Claude or Cursor? Use an app that ships an MCP server, or build one with care.
  4. Is every remote MCP server behind authentication, with per-tool permission checks?
  5. Is Boost excluded from production installs?
  6. Will agents on the live site connect as a dedicated, limited user?
  7. Can you revoke a token or OAuth grant in one place?
  8. Do you know which laravel/mcp version your app and its packages depend on?
If you answered yes to the first three, you need all three layers. That is normal. Keep each one in its lane.

Verdict

laravel/mcp, Laravel Boost and a CMS MCP server are not three options for one job. laravel/mcp is how you build MCP servers in Laravel. Boost is a local MCP server that makes your coding agent smarter about your project. A CMS MCP server is a finished, permission-checked server for day-to-day site work. Pick by audience and by where it runs. If your next Laravel build needs content, media, roles and an agent-ready admin from day one, try Lara Dashboard. You get a production MCP server built on laravel/mcp, and you can keep using Boost while you extend it.

FAQ

Is Laravel Boost the same as laravel/mcp?

No. laravel/mcp is the package for building MCP servers. Boost is a separate dev package that uses laravel/mcp to run its own local server, plus guidelines, skills and a docs search tool for coding agents.

Can I use Laravel Boost in production?

It is meant as a dev dependency and installs with --dev. Its tools can read your schema and run database queries, so we keep it out of production installs and never expose it to remote clients.

Do I need laravel/mcp to use a CMS MCP server?

Not as a site owner. The CMS ships its server already. In Lara Dashboard, laravel/mcp is a dependency in composer.json, so it is installed with the app. You only write laravel/mcp code if you add your own tools.

Which AI clients work with these servers?

Boost's docs list Cursor, Claude Code, Codex, GitHub Copilot in VS Code and Junie. A web MCP server like Lara Dashboard's works with clients that support remote MCP, such as Claude.ai, Claude Desktop, Claude Code and Cursor.

Can a Lara Dashboard module add its own MCP tools?

Yes. A module writes tool classes that extend the laravel/mcp Tool class and adds them through the filter.mcp.tools filter hook. It can also map its permissions to token abilities with a second filter.

Is laravel/mcp stable?

As of November 2026, it is on the 1.x line, with v1.2.1 released on 17 November 2026. Earlier 0.x releases still exist, so check which version your app and packages pin.
Laravel CMS Open source Module Architecture

Try Lara Dashboard for Free

Explore every feature live — no sign-up required.

Launch Live Demo