This package provides a Model Context Protocol (MCP) server integration for the Laravel DebugBar, allowing you to capture and analyze debug information from your Laravel application through the MCP protocol.
Install the package via Composer:
composer require sebdesign/laravel-debugbar-mcp-server
The package uses Laravel's auto-discovery feature. Once installed, the service provider will be automatically registered.
If you're not using auto-discovery, add the service provider to your config/app.php
file:
'providers' => [
// ...
Sebdesign\DebugbarMcpServer\DebugbarMcpServerServiceProvider::class,
],
Publish the configuration file to customize the MCP server settings:
php artisan vendor:publish --provider="Sebdesign\DebugbarMcpServer\DebugbarMcpServerServiceProvider" --tag="config"
This will create a debugbar-mcp-server.php
file in your config directory. You can modify the following settings:
Example configuration:
return [
'enabled' => env('DEBUGBAR_MCP_SERVER_ENABLED', true),
'host' => env('DEBUGBAR_MCP_SERVER_HOST', '127.0.0.1'),
'port' => env('DEBUGBAR_MCP_SERVER_PORT', 9912),
'options' => [
'backlog' => 102400,
],
];
Start the MCP server using the provided Artisan command:
php artisan debugbar:mcp-server
You can specify different host and port if needed:
php artisan debugbar:mcp-server --host=0.0.0.0 --port=8080
Once the server is running, MCP clients can connect to it using the configured host and port. The server will send debug information collected by Laravel DebugBar to connected clients.
The MCP server automatically integrates with Laravel DebugBar. It captures all debug information that would normally be displayed in the browser's debug bar and makes it available through the MCP protocol.
The MCP server supports the following commands:
Example:
php artisan debugbar:mcp-server status
If you encounter connection issues, ensure:
The MCP server logs its activity to Laravel's standard logging system. Check your logs for more detailed information about any issues.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"cursor-rules-mcp": {
"command": "npx",
"args": [
"-y",
"cursor-rules-mcp"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.