clockwork-mcp
Provides debugging and performance analysis for Laravel applications via Clockwork, enabling inspection of requests, queries, errors, cache, and more.
Enables reading Clockwork debugging data stored in MySQL for performance and error analysis.
Enables reading Clockwork debugging data stored in PostgreSQL for performance and error analysis.
Provides tools to inspect Redis commands executed during requests, as well as cache operations and statistics.
Enables reading Clockwork debugging data stored in SQLite for performance and error analysis.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@clockwork-mcpFind slow queries in the last request"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
clockwork-mcp
MCP server for Laravel Clockwork - debug Laravel apps with Claude Code.
What it does
This MCP server gives Claude Code access to your Laravel application's Clockwork debugging data, enabling:
Debugging - Find slow queries, N+1 problems, cache issues, errors
Performance analysis - Track response times, query counts, memory usage
Development insight - Understand request flow, see runtime behavior
Related MCP server: mcp-codex-dev
Installation
Option 1: Claude Code Plugin (Recommended)
/marketplace add github:fridzema/clockwork-mcp
/plugin install clockworkThis installs the MCP server and adds convenience commands:
/clockwork:status- Check storage status/clockwork:latest- Show latest request summary/clockwork:slow- Find slow queries/clockwork:n+1- Detect N+1 patterns
Option 2: Manual MCP Configuration
Add to your Claude Code MCP settings:
{
"mcpServers": {
"clockwork": {
"command": "npx",
"args": ["-y", "clockwork-mcp"]
}
}
}Quick Start
1. Install Clockwork in your Laravel app
composer require itsgoingd/clockwork2. Start debugging
Ask Claude to analyze your requests:
"Show me the latest request"
"Find slow queries in the last request"
"Check for N+1 query problems"
"Compare this request with the previous one"
Or use the slash commands:
/clockwork:status/clockwork:latest/clockwork:slow/clockwork:n+1
Usage Examples
Debugging a Slow Endpoint
You: "The /api/orders endpoint is slow, can you analyze it?"Claude will use the MCP tools to:
Find the latest request to
/api/ordersAnalyze query performance
Detect N+1 patterns
Suggest fixes like eager loading or caching
Investigating a 500 Error
You: "I just got a 500 error on the checkout page, what happened?"Claude will:
Find the latest failed request
Show error logs and exception details
Identify the problematic code path
Optimizing Database Queries
You: "Check if there are N+1 issues on the products page"Claude will:
Analyze recent requests to the products route
Detect repeated query patterns
Suggest eager loading with
->with('relation')
More Natural Language Examples
Performance:
"Compare the last two requests to /api/users"
"Which queries are taking the longest?"
"Show me the cache hit ratio"
Debugging:
"What middleware ran on the last request?"
"Show me all log entries with errors"
"List the events that were dispatched"
Analysis:
"Give me a performance summary of the latest request"
"Show the full request timeline"
"What views were rendered?"
Exception & Error Analysis:
"Show me exception patterns from the last hour"
"What errors have been occurring?"
"Group recent exceptions by type"
Route Performance:
"Which routes are slowest? Show p95 response times"
"Analyze route performance for the past day"
"Compare response times across endpoints"
Memory Issues:
"Are there any memory issues?"
"Detect memory leaks or growth patterns"
"Which requests are using the most memory?"
Queue Jobs:
"List failed queue jobs"
"Show me recent job executions"
"What jobs are pending?"
Test Execution:
"List recent test runs"
"Show failed tests"
"What tests are being skipped?"
Tools
Request Discovery
Tool | Description |
| List recent requests with filtering |
| Get full request details by ID |
| Get the most recent request |
| Search by controller, URI, status, duration |
Database Analysis
Tool | Description |
| Get all database queries for a request |
| Find queries above threshold |
| Detect N+1 query patterns |
| Get aggregate query statistics |
Performance
Tool | Description |
| Response time, memory, query overview |
| Execution timeline events |
| Compare two requests side by side |
Cache & Redis
Tool | Description |
| Cache hits, misses, writes |
| Hit ratio and totals |
| Redis commands executed |
Application Context
Tool | Description |
| Log entries with level filtering |
| Dispatched events and listeners |
| Rendered views |
| Outgoing HTTP requests |
Artisan Commands
Tool | Description |
| List profiled command executions |
| Full command execution details |
Traces & Execution Flow
Tool | Description |
| Hierarchical execution tree from timeline events |
| Source location for a database query |
| Source location for a log entry |
Profiling (Xdebug)
Tool | Description |
| Xdebug profiling data (stub) |
| Xdebug hotspots (stub) |
Queue Jobs
Tool | Description |
| List queue jobs with filtering |
| Full queue job details |
Test Execution
Tool | Description |
| List test executions with filtering |
| Full test execution details |
Request Context
Tool | Description |
| Authenticated user for a request |
| Session data for a request |
| Middleware chain for a request |
| Route details for a request |
Multi-Request Analysis
Tool | Description |
| Group exceptions by message pattern |
| Route performance with percentiles (p50/p95/p99) |
| Detect high memory usage and growth patterns |
Utility
Tool | Description |
| Storage status and statistics |
| High-level request summary |
Configuration
Storage Backends
By default, Clockwork MCP auto-detects your Laravel project and uses php artisan tinker to read Clockwork data. This works with all Clockwork storage backends:
File (default)
SQLite
MySQL
PostgreSQL
Redis
When you configure Clockwork to use SQL or Redis storage in your Laravel app (config/clockwork.php), the MCP server automatically uses the same storage by running PHP commands through artisan tinker. No additional configuration required.
Environment Variables
Variable | Default | Description |
| Auto-detect | Path to Laravel project root |
| Auto-detect | Force storage driver ( |
|
| Custom PHP binary path |
| Auto-detect | Direct path to storage (file driver only) |
Auto-detection
The MCP server automatically finds Clockwork storage by:
Checking
CLOCKWORK_PROJECT_PATHenvironment variableLooking for Laravel project (has
artisanfile) in current directoryTraversing up to find a Laravel project
When a Laravel project is found, the artisan driver is used by default, which supports all Clockwork storage backends. The file driver is used as a fallback when only a direct storage path is available.
Requirements
Node.js 18+
Laravel project with Clockwork installed
Claude Code with MCP support
License
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/fridzema/clockwork-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server