About Laravel Kick
Laravel Kick is an MCP server and REST API for Laravel 12 applications, aimed at developers who need to inspect and operate an app. It exposes health, logs, queues, system stats, and whitelisted Artisan commands, with token scopes and log PII scrubbing.
Key features
- 01Check database, cache, storage, and Redis health
- 02View CPU, memory, disk, and uptime stats
- 03List and filter application logs
- 04Inspect queues and retry failed jobs
- 05Run whitelisted Artisan commands
Use cases
- 01Check service connectivity when diagnosing an outage
- 02Find error entries in application logs
- 03Review failed queue jobs and retry them
- 04Clear a cache using an allowed Artisan command
MCP support
Connects an MCP client to a Laravel application and exposes health, stats, logs, queue, and Artisan tools. Access is controlled by token authentication and scopes.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://your-app.com/mcp/kickclaude mcp add --transport http laravel-kick https://your-app.com/mcp/kick{"mcpServers":{"laravel-kick":{"type":"http","url":"https://your-app.com/mcp/kick"}}}Open in Cursor{"servers":{"laravel-kick":{"type":"http","url":"https://your-app.com/mcp/kick"}}}Open in VS Code{"mcpServers":{"laravel-kick":{"type":"http","url":"https://your-app.com/mcp/kick"}}}{"mcpServers":{"laravel-kick":{"serverUrl":"https://your-app.com/mcp/kick"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://your-app.com/mcp/kickAuth requiredTools
Details
From the project READMELaravel Kick
MCP server and REST API for Laravel application introspection.
Connect your MCP client directly to your Laravel app. Check health, read logs, inspect queues, run commands - all through natural conversation.
Installation
composer require stumason/laravel-kick
Add to .env:
KICK_ENABLED=true
KICK_TOKEN=your-secure-random-token
MCP Setup
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"my-app": {
"command": "npx",
"args": [
"mcp-remote@latest",
"https://your-app.com/mcp/kick",
"--transport",
"http-only",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer your-kick-token"
}
}
}
}
Then ask the LLM:
- "Check the health of my app"
- "Show me the last 20 ERROR entries in the logs"
- "What's failing in the queue?"
- "Clear the config cache"
Available Tools
| Tool | Description |
|---|---|
kick_health | Database, cache, storage, redis connectivity |
kick_stats | CPU, memory, disk, uptime |
kick_logs_list | List log files |
kick_logs_read | Read logs with filtering |
kick_queue_status | Queue overview, failed jobs |
kick_queue_retry | Retry failed jobs |
kick_artisan_list | List available commands |
kick_artisan_run | Execute whitelisted commands |
REST API
The same functionality is available via HTTP:
curl -H "Authorization: Bearer $TOKEN" https://app.com/kick/health
curl -H "Authorization: Bearer $TOKEN" https://app.com/kick/stats
curl -H "Authorization: Bearer $TOKEN" "https://app.com/kick/logs/laravel.log?level=ERROR"
curl -X POST -H "Authorization: Bearer $TOKEN" -d '{"command":"cache:clear"}' https://app.com/kick/artisan
See the API documentation for all endpoints.
Security
- Disabled by default (
KICK_ENABLED=false) - Token-based authentication with scopes
- Artisan command whitelist
- Path traversal protection
- Automatic PII scrubbing from logs
Requirements
- PHP 8.4+
- Laravel 12
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.