Laravel-Debugbar

This MCP server provides access to Laravel Debugbar data through a standardized JSON-RPC protocol. It collects debug information generated by Laravel Debugbar and exposes it via a set of tools that you can call through the MCP protocol, such as clearing logs, retrieving a hierarchical request tree, and fetching detailed log data. The tools are designed to help AI agents analyze debugging data, identify slow queries, and inspect exceptions or route information. Typical workflows include clearing existing logs, triggering a browser action to generate new logs, then querying the request tree to locate the target request and using debugbar_get_logs to obtain structured details (queries, models, views, and more).

Prerequisites:

• A Laravel project with Laravel Debugbar installed (composer require barryvdh/laravel-debugbar --dev)
• PHP 8.0+ (as per compatibility)
• Access to your project files where the MCP server will run (e.g., the .ladebugermcp directory)

Installation steps:

1. Create the MCP folder within your Laravel project: mkdir .ladebugermcp

2. Add the MCP server file to the folder (download mcp-server.php and place it in .ladebugermcp/).

3. Ensure Debugbar logs are written to storage/debugbar/*.json by configuring Debugbar accordingly in your Laravel project. For example, reference the debugbar storage location in your config and verify permissions.

4. Configure the MCP server entry in your environment. If you are running via a Node-based wrapper, ensure you have the MCP server script accessible (e.g., path/to/mcp-server.js) and that the wrapper can execute PHP-based server logic or integrate with a compatible bridge.

5. Start the MCP server using your chosen wrapper/runner. For local development, run the wrapper command that invokes the mcp-server.js script, which will communicate with the PHP-based MCP server (mcp-server.php) as configured.

6. In your IDE or integration tool, add the MCP configuration pointing to the local wrapper as described in the README, using the appropriate command and arguments for your environment.

Tips and common issues:

• The MCP server is intended for local development only. Do not deploy on public or production servers.
• Ensure storage/debugbar contains JSON logs and that file permissions allow the MCP wrapper to read them.
• If you see path-related errors, double-check the path to mcp-server.php in your configuration and ensure the wrapper can reach it.
• When updating configuration, restart the MCP service to apply changes.
• The Tools section exposes a set of commands (debugbar_clear, debugbar_get_request_tree, debugbar_get_logs). Use these in sequence to analyze browser interactions: clear logs, perform a browser action to generate new logs, then fetch the request tree and detailed logs.
• Session data in debugbar_get_logs can be disabled by default due to potential size; enable only when needed.