Required MCP Servers
This project’s MCP (Model Context Protocol) servers are defined in the root
.mcp.json file and load automatically: .claude/settings.json sets
"enableAllProjectMcpServers": true, so no manual claude mcp add step is
needed.
Laravel Boost MCP
Section titled “Laravel Boost MCP”Purpose: Laravel development tools - database access, Artisan commands, error logs, Tinker execution, and documentation search.
How it runs: Laravel Boost is a Composer dev dependency (laravel/boost v2 in backend/composer.json). The server is wired in .mcp.json as:
cd backend && ./vendor/bin/sail artisan boost:mcpSail containers must be running for the server to start.
Used By: All backend agents (@laravel-core-agent, @filament-admin-agent, @laravel-testing-agent, @laravel-debug-agent)
Key Tools:
application-info- Get app info, packages, modelsdatabase-schema- Read complete database schemadatabase-query- Execute read-only SQL queriessearch-docs- Search Laravel ecosystem docs (version-specific)tinker- Execute PHP in Laravel contextlist-routes- List all application routeslast-error- Get last error details
Chrome DevTools MCP
Section titled “Chrome DevTools MCP”Purpose: Browser automation and debugging for testing frontend, checking console errors, inspecting network requests.
How it runs: Configured in .mcp.json as a stdio server running npx chrome-devtools-mcp@latest.
Use Cases:
- Login flow testing
- Console error detection
- Network request inspection
- Form interaction testing
- Visual regression testing
Key Tools:
navigate_page- Navigate to URLstake_snapshot- Capture page accessibility snapshotfill_form- Fill form fieldsclick- Click elementslist_console_messages- Get console logslist_network_requests- Inspect network traffic
Nightwatch MCP
Section titled “Nightwatch MCP”Purpose: Query Laravel Nightwatch production monitoring data.
How it runs: Configured in .mcp.json as an HTTP server pointing to https://nightwatch.laravel.com/mcp.
Local Analytics MCP
Section titled “Local Analytics MCP”The repository also contains analytics-mcp/ (the volare-analytics-mcp
Google Analytics MCP server). It is not registered in .mcp.json - it is
an optional local project you can run and register yourself if needed.
Verification
Section titled “Verification”The project’s .claude/settings.json includes MCP permissions:
{ "permissions": { "allow": [ "mcp__laravel-boost", "mcp__chrome-devtools" ] }, "enableAllProjectMcpServers": true}Troubleshooting
Section titled “Troubleshooting”MCP Not Found:
- Ensure you launched Claude Code from the project root (where
.mcp.jsonlives) - Restart Claude Code
- Verify in Claude’s MCP settings
Laravel Boost Issues:
- Check
.envfile exists inbackend/ - Verify Sail is running (
cd backend && ./vendor/bin/sail ps). TheSessionStarthook runsscripts/setup_env.shto prepare the environment on startup.
Chrome DevTools Issues:
- Ensure Chrome browser is installed
- Check no firewall blocking local connections
Support
Section titled “Support”- Laravel Boost: https://github.com/laravel/boost
- Chrome DevTools MCP: https://github.com/ChromeDevTools/chrome-devtools-mcp
- Claude MCP Docs: https://docs.anthropic.com/en/docs/mcp