A powerful MCP server inspector and documentation UI for Laravel — tools reference, interactive playground, scope explorer, and client connect guides.
ovac/laravel-mcp-inspector is a Laravel package for a powerful mcp server inspector and documentation ui for laravel — tools reference, interactive playground, scope explorer, and client connect guides..
It currently has 0 GitHub stars and 15 downloads on Packagist.
Install it with composer require ovac/laravel-mcp-inspector.
Discover more Laravel packages by ovac
or browse all Laravel packages to compare alternatives.
Last updated
A powerful, beautiful inspection and documentation UI for Laravel MCP servers. Think of it as Scalar or Swagger UI, but purpose-built for the Model Context Protocol.
composer require ovac/laravel-mcp-inspector
The package auto-registers its service provider via Laravel's package discovery.
Once installed, visit:
https://your-app.test/mcp/inspector
The inspector reads your MCP tool definitions directly from your Laravel config (default key: mcp_user_public). No HTTP calls to the MCP manifest — this is what makes it fast and reliable.
Publish the config file:
php artisan vendor:publish --tag=mcp-inspector-config
// config/mcp-inspector.php
return [
'enabled' => env('MCP_INSPECTOR_ENABLED', true),
'route_prefix' => 'mcp',
'route_middleware' => ['web'],
'config_key' => 'mcp_user_public',
'title' => 'MCP Inspector',
'theme' => 'auto', // auto|dark|light
];
| Key | Default | Description |
|-----|---------|-------------|
| enabled | true | Enable/disable the inspector. Set to false in production if needed. |
| route_prefix | mcp | URL prefix. Inspector available at /{prefix}/inspector. |
| route_middleware | ['web'] | Middleware for the inspector route. Add auth to restrict access. |
| config_key | mcp_user_public | The Laravel config key containing your MCP server definition. |
| title | MCP Inspector | Title shown in the inspector UI header. |
| theme | auto | Default theme: auto, dark, or light. |
php artisan vendor:publish --tag=mcp-inspector-views
The published view will be in resources/views/vendor/mcp-inspector/.
The inspector expects your MCP config to follow this structure:
// config/mcp_user_public.php
return [
'name' => 'My MCP Server',
'version' => '1.0.0',
'description' => 'API tools for my application.',
'tokens_url' => '/api/mcp/tokens',
'mcp_endpoint' => '/mcp',
'tools' => [
[
'name' => 'get_user',
'description' => 'Retrieve a user by their ID.',
'inputSchema' => [
'type' => 'object',
'properties' => [
'user_id' => [
'type' => 'integer',
'description' => 'The user ID.',
],
],
'required' => ['user_id'],
],
'annotations' => [
'scope' => 'users:read',
'risk' => 'low',
'readOnlyHint' => true,
],
],
],
'scopes' => [
[
'name' => 'users:read',
'description' => 'Read user data.',
'tools' => ['get_user'],
],
],
];
For production, you should:
MCP_INSPECTOR_ENABLED=false// config/mcp-inspector.php
'route_middleware' => ['web', 'auth'],
composer test
See CHANGELOG.md for recent changes.
MIT License. See LICENSE for details.
Built with care by Ariama Victor (Gidipex).