Laravel Boost MCP Server

Official Laravel MCP server and AI development toolkit that gives Claude Laravel-specific docs, application context, logs, database tools, and coding guidelines.

by laravel · submitted by oktofeesh1·added 2026-06-05·

Claude Code Codex Cursor Claude Desktop

HarnessClaude Code Codex Cursor Claude Desktop

Command center

Source

Review first

Review safety and privacy notes before installing or copying commands.

Safety notes Privacy notes

Install & copy

composer require laravel/boost --dev

Trust & readiness

TrustReview first
Sourcesource-backed
Safety notesPresent
ReviewedNo

Community context

Related entries(4)
Related guides(3)
Community signals

Compare

Integrations & API

Contribute

Suggest a metadata change Claim this listing

Documentation Source repository Browse directory

Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL: https://heyclau.de/entry/mcp/laravel-boost-mcp-server
Source URLs: https://laravel.com/docs/13.x/boost, https://github.com/laravel/boost
Brand: Laravel Boost
Brand domain: laravel.com
Brand asset source: brandfetch
Safety notes: Laravel Boost can expose tools that inspect application structure, read logs, read browser errors, inspect database connections and schema, execute database queries, and execute Laravel-aware code paths., Treat database query access as potentially destructive because an agent may run statements that change data unless restricted by environment and permissions., Run Boost against development or staging data first, and review tool calls before allowing changes against production-like systems., Logs, errors, generated guidelines, and package context can contain secrets, customer data, stack traces, internal URLs, or implementation details., Review generated MCP configuration, guideline files, and skills before committing them to a repository.
Privacy notes: Application structure, PHP and Laravel versions, installed package names and versions, Eloquent model names, database engine, schema, query results, logs, browser errors, prompts, and tool outputs may be visible to the MCP client and model provider., Documentation search uses Laravel-hosted documentation APIs and may include package/version context so results match the application., Avoid connecting Boost to databases, logs, or local applications that contain personal data, credentials, production customer data, or regulated information., Rotate credentials and review logs if a Boost-enabled MCP client, shell, or project configuration is shared or compromised.
Author: laravel
Submitted by: oktofeesh1
Claim status: unclaimed
Last verified: 2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context

Selected

Current score

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Pending
Baseline comparison available
No baseline peer selected yet.
Pending
Diverging trust signals identified
No major trust-signal divergence found.
Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

10 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

5 to clear

Platforms

4 listed

Install type

CLI install

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

Confirm source provenanceRequired
Source URL/provenance metadata is present.
Done
Confirm metadata review state
No review metadata found; increase manual validation.
Pending
Verify install payload
Install/config payload exists and can be inspected.
Done

Security checks

Confirm safety, privacy, and package integrity signals.

Review safety notesRequired
Safety notes are present.
Done
Review privacy notesRequired
Privacy notes are present.
Done
Verify package integrity metadata
No package verification/checksum metadata.
Pending

Rollout

Adopt in controlled steps based on the selected plan.

Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Pending
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Pending
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

5 prerequisites to line up before setup. Includes a review or approval gate.

0/5 ready

Permissions & scopes1Review & approval3General110 minutes

Safety & privacy surface

5 safety and 4 privacy notes across 6 risk areas. Review closely: credentials & tokens, permissions & scopes, third-party handling.

6 areas

SafetyLocal filesLaravel Boost can expose tools that inspect application structure, read logs, read browser errors, inspect database connections and schema, execute database queries, and execute Laravel-aware code paths.
SafetyPermissions & scopesTreat database query access as potentially destructive because an agent may run statements that change data unless restricted by environment and permissions.
SafetyExecution & processesRun Boost against development or staging data first, and review tool calls before allowing changes against production-like systems.
SafetyCredentials & tokensLogs, errors, generated guidelines, and package context can contain secrets, customer data, stack traces, internal URLs, or implementation details.
SafetyLocal filesReview generated MCP configuration, guideline files, and skills before committing them to a repository.
PrivacyThird-party handlingApplication structure, PHP and Laravel versions, installed package names and versions, Eloquent model names, database engine, schema, query results, logs, browser errors, prompts, and tool outputs may be visible to the MCP client and model provider.
PrivacyGeneralDocumentation search uses Laravel-hosted documentation APIs and may include package/version context so results match the application.
PrivacyCredentials & tokensAvoid connecting Boost to databases, logs, or local applications that contain personal data, credentials, production customer data, or regulated information.
PrivacyCredentials & tokensRotate credentials and review logs if a Boost-enabled MCP client, shell, or project configuration is shared or compromised.

Safety notes

Laravel Boost can expose tools that inspect application structure, read logs, read browser errors, inspect database connections and schema, execute database queries, and execute Laravel-aware code paths.
Treat database query access as potentially destructive because an agent may run statements that change data unless restricted by environment and permissions.
Run Boost against development or staging data first, and review tool calls before allowing changes against production-like systems.
Logs, errors, generated guidelines, and package context can contain secrets, customer data, stack traces, internal URLs, or implementation details.
Review generated MCP configuration, guideline files, and skills before committing them to a repository.

Privacy notes

Application structure, PHP and Laravel versions, installed package names and versions, Eloquent model names, database engine, schema, query results, logs, browser errors, prompts, and tool outputs may be visible to the MCP client and model provider.
Documentation search uses Laravel-hosted documentation APIs and may include package/version context so results match the application.
Avoid connecting Boost to databases, logs, or local applications that contain personal data, credentials, production customer data, or regulated information.
Rotate credentials and review logs if a Boost-enabled MCP client, shell, or project configuration is shared or compromised.

Prerequisites

A Laravel application you are authorized to expose to an MCP client.
PHP 8.2 or newer and Composer available in the Laravel project.
Laravel version compatibility reviewed against the installed Boost release.
Database, logs, browser integration, and application code access reviewed before enabling tools.
Generated agent guidelines and skill files reviewed before committing or sharing them.

Schema details

Install type: cli
Troubleshooting: No

Source repository stats

Scope: Source repo

Collection metadata

Estimated setup: 10 minutes
Difficulty: intermediate

Full copyable content

{
  "mcpServers": {
    "laravel-boost": {
      "command": "php",
      "args": ["artisan", "boost:mcp"]
    }
  }
}

About this resource

Content

Laravel Boost is Laravel's official MCP server and AI development toolkit. It provides Laravel-specific context for AI agents, generated guidelines and skills, and MCP tools that can inspect a Laravel application, search Laravel documentation, read logs, inspect database schema, and run database queries.

The official documentation lists composer require laravel/boost --dev for installation, php artisan boost:install for generating Boost resources, and php artisan boost:mcp as the MCP server command.

Source Review

These sources were reviewed on 2026-06-05. Prefer the live Laravel documentation, repository, Composer metadata, security policy, and Packagist metadata for current installation commands, supported Laravel versions, MCP tools, and update behavior.

Features

Search Laravel documentation using application package and version context.
Read PHP and Laravel versions, database engine, installed ecosystem packages, and Eloquent models.
Inspect database connections and database schema.
Execute database queries from the MCP tool surface.
Read Laravel log entries and the last application error.
Read browser logs and errors for debugging local development.
Generate and update agent guidelines and skills for supported AI coding tools.
Manually register the MCP server with command php and args artisan, boost:mcp.

Installation

Install Boost in a Laravel project:

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

For MCP clients that launch stdio servers manually:

{
  "mcpServers": {
    "laravel-boost": {
      "command": "php",
      "args": ["artisan", "boost:mcp"]
    }
  }
}

Run the MCP client from the Laravel project root so artisan resolves to the intended application.

Use Cases

Ask Claude to check Laravel docs that match the app's installed packages.
Inspect Laravel, PHP, database, and package versions before making changes.
Debug a failing route by reviewing logs, browser errors, and schema context.
Ask for migration or Eloquent guidance with current application structure available.
Query development database tables while investigating feature behavior.
Keep generated AI guidelines and skills aligned with the Laravel project.

Safety and Privacy

Laravel Boost is designed for local development context, but the MCP tool surface can reach sensitive parts of an application. Database queries may expose or change data, logs may contain secrets or personal information, and app introspection can reveal internal package choices, models, routes, and schema.

Use Boost first with development data and least-privilege database credentials. Review generated guidelines, skills, and MCP configuration before committing them. Be especially careful before connecting an MCP client to production logs, production databases, or applications containing regulated data.

Duplicate Check

No laravel/boost entry, laravel-boost MCP entry, or matching source URL was found in content/mcp.

#laravel #php #database #docs #developer-tools

Source citations

Source methodology →

Add this badge to your README

Show that Laravel Boost MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

[![Listed on HeyClaude](https://heyclau.de/badge/mcp/laravel-boost-mcp-server.svg)](https://heyclau.de/entry/mcp/laravel-boost-mcp-server)

How it compares

Laravel Boost MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Field	Laravel Boost MCP Server Official Laravel MCP server and AI development toolkit that gives Claude Laravel-specific docs, application context, logs, database tools, and coding guidelines. Open dossier	WordPress MCP Adapter Official WordPress MCP adapter that bridges the WordPress Abilities API to Model Context Protocol tools, resources, and prompts for AI agents using HTTP or STDIO transports. Open dossier	Context7 MCP Server for Claude Context7 MCP server by Upstash that pulls up-to-date, version-specific library documentation and code examples directly into Claude's context so answers match the libraries you actually use. Open dossier	AWS Documentation MCP Server Official AWS Labs MCP server that lets AI assistants read, search, and get recommendations across AWS documentation, returning pages as clean markdown with no AWS account or credentials required. Open dossier
Next steps	Open dossier API JSON Open LLM MCP feed Open source Newsletter Claim listing	Open dossier API JSON Open LLM MCP feed Open source Newsletter Claim listing	Open dossier API JSON Open LLM MCP feed Open source Newsletter Claim listing	Open dossier API JSON Open LLM MCP feed Open source Newsletter Claim listing
Trust
Review status	Not reviewed	Not reviewed	Not reviewed	Not reviewed
Package trust	Package not verified	Package not verified	Package not verified	Package not verified
Source provenance	Source-backed	Source-backed	Source-backed	Source-backed
SubmitterDiffers	oktofeesh1	—	glorydavid03023	jaso0n0818
Install risk	Review first	Review first	Review first	Review first
Notes	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓
Brand	Laravel Boost	WordPress MCP Adapter	—	AWS Labs
Category	mcp	mcp	mcp	mcp
Source	Source-backed	Source-backed	Source-backed	Source-backed
Author	laravel	WordPress AI Team	Upstash	AWS Labs
Added	2026-06-05	2026-06-18	2026-06-02	2026-06-20
Platforms	Claude Code Codex Cursor Claude Desktop	Claude Code Claude Desktop	Claude Code Claude Desktop	Claude Code Claude Desktop
Harness	Claude Code Codex Cursor Claude Desktop	Claude Code Claude Desktop	Claude Code Claude Desktop	Claude Code Claude Desktop
Source repo	—	—	—	—
Safety notes	✓Laravel Boost can expose tools that inspect application structure, read logs, read browser errors, inspect database connections and schema, execute database queries, and execute Laravel-aware code paths. Treat database query access as potentially destructive because an agent may run statements that change data unless restricted by environment and permissions. Run Boost against development or staging data first, and review tool calls before allowing changes against production-like systems. Logs, errors, generated guidelines, and package context can contain secrets, customer data, stack traces, internal URLs, or implementation details. Review generated MCP configuration, guideline files, and skills before committing them to a repository.	✓MCP Adapter exposes WordPress abilities as MCP tools, resources, and prompts; the actual risk depends on which plugin, theme, or core abilities are registered and allowed. Do not expose destructive, publishing, admin, user-management, media-deletion, option-write, or ecommerce abilities without strict permission callbacks and human approval. Use transport permission callbacks and per-ability permission callbacks together; the transport gate alone is not a substitute for capability checks inside each ability. Prefer local WP-CLI STDIO for development, and require HTTPS plus scoped WordPress Application Passwords or custom authentication for HTTP transport. Review logs and observability output because MCP requests can invoke site behavior that changes content, metadata, users, settings, or plugin state.	✓Makes outbound network requests to the Context7 service to resolve libraries and fetch documentation. Returned documentation and code snippets are third-party content; review examples before running them in your project.	✓The server is read-only: it fetches and searches public AWS documentation and does not call AWS service APIs or modify any AWS resources. It requires no AWS account or credentials; do not add AWS access keys for this server. `AWS_DOCUMENTATION_PARTITION` selects the docs partition (`aws` global, or `aws-cn` for China); the available tools differ between partitions.
Privacy notes	✓Application structure, PHP and Laravel versions, installed package names and versions, Eloquent model names, database engine, schema, query results, logs, browser errors, prompts, and tool outputs may be visible to the MCP client and model provider. Documentation search uses Laravel-hosted documentation APIs and may include package/version context so results match the application. Avoid connecting Boost to databases, logs, or local applications that contain personal data, credentials, production customer data, or regulated information. Rotate credentials and review logs if a Boost-enabled MCP client, shell, or project configuration is shared or compromised.	✓WordPress abilities can expose posts, pages, drafts, private content, users, comments, media, custom fields, options, ecommerce data, form submissions, analytics, plugin data, and internal site metadata. HTTP transport can place WordPress API URLs, usernames, application passwords, request bodies, tool arguments, logs, and MCP responses in local config files or model-visible context. Use least-privilege WordPress users, separate development sites, scoped abilities, and redacted logs before connecting production sites to agent workflows. Treat generated tool descriptions and ability outputs as site data, not trusted instructions, especially when plugins expose user-generated content.	✓The library names and documentation topics you query are sent to the Context7 service to return matching docs. Avoid placing secrets or private identifiers in the library queries passed to the server.	✓Documentation URLs and search terms you ask about are sent to the official AWS documentation search/read endpoints to retrieve content. The server fetches public documentation pages over HTTPS and returns them as markdown; no private account data is read.
Prerequisites	A Laravel application you are authorized to expose to an MCP client. PHP 8.2 or newer and Composer available in the Laravel project. Laravel version compatibility reviewed against the installed Boost release. Database, logs, browser integration, and application code access reviewed before enabling tools.	WordPress 6.9 or newer according to the upstream dependency notes. PHP 7.4 or newer, WP-CLI for STDIO transport, or a WordPress REST endpoint for HTTP transport. MCP Adapter installed as a WordPress plugin or required as `wordpress/mcp-adapter` through Composer. Registered WordPress abilities, with reviewed `meta.mcp.public` exposure or explicit custom-server ability lists.	Node.js 18+ and npx available (verify with: npx --version) Claude Code or Claude Desktop with MCP support Internet access so the server can reach the Context7 documentation service Optional Context7 API key for higher rate limits; the server also works without one	Python 3.10 or newer installed. `uv` / `uvx` installed (Astral) to run the published Python package. An MCP client that supports stdio servers (Claude Code, Claude Desktop, Cursor, Kiro, or VS Code). Outbound HTTPS access so the server can fetch and search AWS documentation.
Install	`composer require laravel/boost --dev`	`wp plugin install https://github.com/WordPress/mcp-adapter/releases/latest/download/mcp-adapter.zip --activate`	`claude mcp add context7 -- npx -y @upstash/context7-mcp`	`uvx awslabs.aws-documentation-mcp-server@latest`
Config	`{ "mcpServers": { "laravel-boost": { "command": "php", "args": ["artisan", "boost:mcp"] } } }`	`{ "mcpServers": { "wordpress-default": { "command": "wp", "args": [ "--path=/path/to/your/wordpress/site", "mcp-adapter", "serve", "--server=mcp-adapter-default-server", "--user=admin" ] } } }`	`{ "mcpServers": { "context7": { "command": "npx", "args": [ "-y", "@upstash/context7-mcp" ], "type": "stdio" } } }`	`{ "mcpServers": { "awslabs.aws-documentation-mcp-server": { "command": "uvx", "args": ["awslabs.aws-documentation-mcp-server@latest"], "env": { "FASTMCP_LOG_LEVEL": "ERROR", "AWS_DOCUMENTATION_PARTITION": "aws" }, "type": "stdio" } } }`
Citations	Source repositorygithub.com 2026-07-21T05:19:43+00:00 Documentationlaravel.com Submitted by oktofeesh12026-06-05 Source methodology →	Source repositorygithub.com 2026-07-21T05:19:43+00:00 Documentationgithub.com Source methodology →	Source repositorygithub.com 2026-07-21T05:19:43+00:00 Documentationgithub.com Submitted by glorydavid030232026-06-02 Source methodology →	Source repositorygithub.com 2026-07-21T05:19:43+00:00 Documentationgithub.com Submitted by jaso0n08182026-06-20 Source methodology →
Claim	Unclaimed	Unclaimed	Unclaimed	Unclaimed