clockwork-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOCKWORK_PHP_PATH | No | Custom PHP binary path | php |
| CLOCKWORK_PROJECT_PATH | No | Path to Laravel project root | Auto-detect |
| CLOCKWORK_STORAGE_PATH | No | Direct path to storage (file driver only) | Auto-detect |
| CLOCKWORK_STORAGE_DRIVER | No | Force storage driver (artisan or file) | Auto-detect |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_requestsC | List recent Clockwork requests with optional filtering |
| get_requestA | Get full details of a specific request by ID |
| get_latest_requestB | Get the most recent Clockwork request |
| search_requestsB | Search requests by controller, URI, status, or duration |
| get_queriesC | Get database queries for a request |
| analyze_slow_queriesC | Find slow database queries above threshold |
| detect_n_plus_oneC | Detect N+1 query patterns in a request |
| get_query_statsC | Get aggregate query statistics for a request |
| get_performance_summaryC | Get performance overview for a request |
| get_timelineB | Get timeline events for a request |
| compare_requestsC | Compare two requests side by side |
| get_cache_operationsC | Get cache operations for a request |
| get_cache_statsB | Get cache statistics (hit ratio, totals) |
| get_redis_commandsC | Get Redis commands for a request |
| get_logsC | Get log entries for a request |
| get_eventsC | Get dispatched events for a request |
| get_viewsB | Get rendered views for a request |
| get_http_requestsC | Get outgoing HTTP requests made during a request |
| list_commandsB | List profiled Artisan command executions |
| get_commandC | Get full details of an Artisan command execution |
| get_clockwork_statusB | Check Clockwork storage status and statistics |
| explain_request_flowC | Get high-level summary of what happened in a request |
| get_call_graphC | Build hierarchical execution tree from timeline events |
| get_query_stack_traceB | Get source location for a database query |
| get_log_stack_traceC | Get source location for a log entry |
| get_xdebug_profileA | Get Xdebug profiling data for a request (stub - not available in Clockwork) |
| get_xdebug_hotspotsA | Get Xdebug hotspots for a request (stub - not available in Clockwork) |
| list_queue_jobsC | List queue jobs with optional filtering |
| get_queue_jobB | Get full details of a queue job |
| list_testsB | List test executions with optional filtering |
| get_testB | Get full details of a test execution |
| get_auth_userC | Get authenticated user for a request |
| get_session_dataC | Get session data for a request |
| get_middleware_chainC | Get middleware chain for a request |
| get_route_detailsC | Get route details for a request |
| analyze_exceptionsC | Analyze exceptions across requests, grouping by message pattern |
| analyze_route_performanceC | Analyze route performance with percentile statistics |
| detect_memory_issuesC | Detect high memory usage and growth patterns |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 38 tools
Most tools target distinct debugging aspects (e.g., queries, cache, logs, events), but slight overlap exists between analyze_slow_queries, get_queries, and get_query_stats, as well as between get_request and get_latest_request. Descriptions mitigate confusion.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_*, analyze_*, list_*), making them predictable and easy to navigate.
38 tools is high but acceptable for a comprehensive debugging server. However, two stub tools (get_xdebug_hotspots, get_xdebug_profile) are unnecessary and inflate the count.
The toolset covers most debugging needs (requests, queries, logs, cache, events, performance, etc.). Minor gaps include the missing Xdebug functionality indicated by stubs.