stephen1137/phpray

Ask why a PHP site is slow, from recorded production traffic rather than source code. Always-on request tracing: every request a site serves is stored with wall time, CPU, memory, SQL queries as fingerprints with the literals stripped, outbound HTTP calls, PHP errors and N+1 patterns; a sample adds per-plugin time attribution. 10 read-only tools: site list, overview, slowest pages, slowest queries, component breakdown, errors, trace search, one trace end to end, before/after compare, and live alerts. The hosted endpoint answers with **no key** from a read-only demo account holding real WooCommerce traffic, so the tools can be tried before installing anything. Runs where PHP usually runs — the extension loads from your own `php.ini` and the WordPress plugin needs neither an extension nor a daemon, so shared hosting without root works. Install: `claude mcp add --transport http phpray https://phpray.dev/mcp`. Transport: `http` (bearer console token, optional) or `stdio`. Registry id `dev.phpray/phpray`. Go/C, Apache-2.0.

Project

Browse this MCP server in the TensorBlock MCP Index.