Overview
What is Laravel Kick?
Laravel Kick is an MCP server and REST API for Laravel application introspection. It connects an MCP client directly to a Laravel app, enabling health checks, log reading, queue inspection, and command execution through natural conversation.
How to use Laravel Kick?
Install via Composer (composer require stumason/laravel-kick), then add KICK_ENABLED=true and a secure KICK_TOKEN to .env. Configure an MCP client (e.g., Claude Desktop) using mcp-remote with an HTTP-only transport and an Authorization header containing the token. Ask the LLM prompts like "Check the health of my app" or "Show me the last 20 ERROR entries in the logs."
Key features of Laravel Kick
- MCP server and REST API for Laravel introspection
- Health check for database, cache, storage, and Redis
- System stats: CPU, memory, disk, uptime
- Log reading with filtering and PII scrubbing
- Queue status overview and retry of failed jobs
- Artisan command listing and whitelisted execution
Use cases of Laravel Kick
- Monitor application health and system resources via natural language
- Debug errors by querying log files with filters
- Manage Laravel queues, including retrying failed jobs
- Run whitelisted Artisan commands (e.g., cache:clear) through conversation
- Access the same functionality programmatically via the REST API
FAQ from Laravel Kick
What does Laravel Kick do that alternatives don't?
It provides direct MCP integration into a Laravel app, allowing an LLM to inspect health, logs, queues, and run commands — all through natural conversation, without additional infrastructure.
What are the runtime requirements for Laravel Kick?
PHP 8.4+ and Laravel 12.
How does authentication and security work?
Disabled by default. Token-based authentication with scopes, an Artisan command whitelist, path traversal protection, and automatic PII scrubbing from logs.
Is Laravel Kick only available via MCP?
No — the same functionality is also available as a REST API, with endpoints for health, stats, logs, and commands, all requiring the same Bearer token.
What transports are supported for MCP?
The README shows an http-only transport via mcp-remote, with the Authorization header passed as an environment variable.
