A
licenseB
qualityC
maintenanceA Claude Code MCP server that connects to Laravel Clockwork to provide insights into application performance, database queries, errors, and request flow.
38
12 npm
4
MIT
clockwork-mcp-remote
by ahmedbally
Related Servers
Alternatives to clockwork-mcp-remote
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceExposes Laravel development tools (artisan, migrations, config, schema, logs) as MCP tools for use with compatible clients.233 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables debugging Symfony applications by inspecting profiler data through a standalone MCP server.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to introspect a Laravel application's routes, models, controllers, migrations, and more through the Model Context Protocol, running locally via php artisan commands and filesystem scanning.8 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server that exposes Symfony profiler runtime data (requests, queries, logs) to AI agents like Claude Code for debugging and optimization.MIT
- AlicenseNot gradedqualityDmaintenanceA Laravel-based web application that provides robust backend services for Model Context Protocol (MCP) operations. Features RESTful API endpoints, user authentication, and scalable architecture for MCP service integration.MIT
TDQS
B3.2/5.0
Scored across 39 tools
Disambiguation4/5
Most tools target a distinct Clockwork data type (queries, cache, logs, views, middleware, etc.), so an agent can generally select the right one. A few high-level analysis tools like get_performance_summary, get_timeline, explain_request_flow, and get_call_graph have overlapping purposes and could cause misselection. The two Xdebug stub tools are also nearly identical in availability, but their names make the intended difference clear.
Naming Consistency5/5
Tool names follow a very consistent verb_noun pattern, mostly built on get_, list_, search_, analyze_, detect_, compare_, and explain_. All names are snake_case and predictable. connect_clockwork is the only outlier, but it represents a distinct setup action and does not break the overall pattern.
Tool Count2/5
39 tools is excessive for an MCP server surface and exceeds the 25-tool threshold where coherence degrades. Many getters for individual request components could be grouped or parameterized (e.g., a single get_request_data tool). Each tool is individually narrow, so the set feels more like an API dump than a curated toolset.
Completeness4/5
The server covers almost every Clockwork domain: requests, queries, cache, Redis, logs, events, views, HTTP calls, queue jobs, tests, commands, auth, session, middleware, route, exceptions, and performance. The only real gaps are the two Xdebug stub tools that are explicitly unavailable, creating minor dead ends. Overall this is a near-complete read-only profiling surface.
Maintenance
ActivityMaintained
ResponsivenessNo issues