{
"mcpServers": {
"laravel-kick": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server and REST API for Laravel application introspection.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
MIT. View license →
Is it maintained?
Last commit 6 days ago. 2 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
An open-source AI agent that brings the power of Gemini directly into your terminal.
The full-stack TypeScript framework to build, test, and deploy production-ready MCP servers and AI-native apps.
Open-source persistent memory for AI agent pipelines (LangGraph, CrewAI, AutoGen) and Claude. REST API + knowledge graph + autonomous consolidation.
MCP Security Weekly
Get CVE alerts and security updates for Laravel Kick and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
composer require stumason/laravel-kick
Add to .env:
KICK_ENABLED=true
KICK_TOKEN=your-secure-random-token
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:
| 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 |
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.
KICK_ENABLED=false)MIT