v0.4.1

Bug Fixes

• fix: query SQLite directly to prevent OOM on large databases

  The previous fix (v0.4.0) still caused OOM because previous() hydrates full Clockwork Request objects before we can extract index fields. This fix adds a direct SQLite query path that fetches only metadata columns, completely bypassing PHP object hydration for list operations.

  How it works

  • Detects if Clockwork uses SQLite storage via Laravel config
  • If SQLite: queries the database directly using sqlite3 CLI, fetching only index columns
  • Falls back to PHP method for non-SQLite storage or if direct query fails

  This fix resolves memory exhaustion on databases 2.7GB+ that was still occurring after the initial fix.

Full Changelog: https://github.com/fridzema/clockwork-mcp/commits/v0.4.1

v0.4.0

What's New

This release adds 16 new MCP tools for deeper Laravel application debugging.

Traces & Execution Flow

• get_call_graph - Hierarchical execution tree from timeline events
• get_query_stack_trace - Source location for a database query
• get_log_stack_trace - Source location for a log entry

Profiling (Xdebug stubs)

• get_xdebug_profile - Xdebug profiling data (stub)
• get_xdebug_hotspots - Xdebug hotspots (stub)

Queue Jobs

• list_queue_jobs - List queue jobs with filtering
• get_queue_job - Full queue job details

Test Execution

• list_tests - List test executions with filtering
• get_test - Full test execution details

Request Context

• get_auth_user - Authenticated user for a request
• get_session_data - Session data for a request
• get_middleware_chain - Middleware chain for a request
• get_route_details - Route details for a request

Multi-Request Analysis

• analyze_exceptions - Group exceptions by message pattern
• analyze_route_performance - Route performance with percentiles (p50/p95/p99)
• detect_memory_issues - Detect high memory usage and growth patterns

New Usage Examples

• "Show me exception patterns from the last hour"
• "Which routes are slowest? Show p95 response times"
• "Are there any memory issues?"
• "List failed queue jobs"
• "Show failed tests"

Full Changelog: v0.3.0...v0.4.0

Full Changelog: v0.3.0...v0.4.0

v0.3.0

Full Changelog: v0.2.4...v0.3.0

v0.2.4

Full Changelog: v0.2.3...v0.2.4

v0.2.3

Full Changelog: v0.2.2...v0.2.3

v0.2.2

Full Changelog: v0.2.1...v0.2.2

v0.2.1

Full Changelog: v0.2.0...v0.2.1

v0.2.0 - Multi-Storage Backend Support

What's New

This release adds support for all Clockwork storage backends by using php artisan tinker to leverage Clockwork's own storage classes.

Supported Storage Backends

• File (default)
• SQLite
• MySQL
• PostgreSQL
• Redis

How It Works

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. No additional configuration required.

New Environment Variables

Variable	Description
CLOCKWORK_STORAGE_DRIVER	Force storage driver (artisan or file)
CLOCKWORK_PHP_PATH	Custom PHP binary path

Full Changelog

Added

• Multi-storage backend support via php artisan tinker
• Unified Storage interface for consistent data access
• Auto-detection of Laravel project and storage driver
• Integration tests for artisan storage driver

Changed

• All tools now use the unified Storage interface
• Improved storage auto-detection (prefers artisan driver when Laravel project found)

---

⚠️ npm publish pending - requires NPM_TOKEN secret configuration

Full Changelog: https://github.com/fridzema/clockwork-mcp/commits/v0.2.0