phpgraph
Health Warn
- License — License: MIT
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 6 GitHub stars
Code Fail
- rm -rf — Recursive force deletion command in install.sh
Permissions Pass
- Permissions — No dangerous permissions requested
No AI report is available for this listing yet.
Knowledge graph of PHP codebases for AI coding agents (Claude Code, Codex, Cursor) over MCP. Static analysis, no LLM.
Ask your agent "what breaks if I change this?" in a PHP codebase, and get the callers grep can't see:
through interfaces, the service container, message buses and routes.
English · Français
In PHP, the code that runs a method is rarely the code that names it. Callers hold an interface, the container
decides which class they get, a bus carries the message to its handler, a route string reaches a controller.
A coding agent searching names with grep has to rebuild that chain file by file, and sometimes guesses.
phpgraph parses the project once and answers from a graph, over MCP, in one call.
Example: Sylius, OrderPromotionProcessor::process(). Searching for the class name finds two files: the class
and its service definition. No caller names it: they all hold OrderProcessorInterface, and the container gives
them a composite that runs the promotion processor among others. One impact_of call (phpgraph impact prints the same):
21 classes up to 3 relations away, 0 routes, 0 more through the state; 43 tests, 0 through the state; 1 helpers.
Direct dependents:
OrderPromotionCodeAssigner (Sylius\Bundle\ApiBundle\Assigner) [through OrderProcessorInterface::process()]: assign L41
BlameCartHandler (Sylius\Bundle\ApiBundle\CommandHandler\Cart) [through OrderProcessorInterface::process()]: __invoke L63
OrderModifier (Sylius\Component\Order\Modifier) [through OrderProcessorInterface::process()]: addToOrder L32; removeFromOrder L39
… 5 more, then 13 classes 2 or 3 relations away and the tests to run
ProcessOrderListener holds the same interface but is not listed: the configuration gives it the payment processor.
Demo

A 68-second video, the same question to Claude Code with and without phpgraph, one real run each:
youtu.be/Cv4ULkN3FF0.
No LLM, no network, no embeddings: your code never leaves your machine, and phpgraph parses it without running it.
Every fact says how sure it is (EXTRACTED, INFERRED or AMBIGUOUS), and what phpgraph could not link is reported.
Where it helps and where it doesn't
Akeneo PIM (8,416 PHP files), task: list every class that must change whenGetCategoryInterface::byCode() takes a second parameter. Claude Code 2.1.325 with Sonnet, 15 November 2026:
phpgraph 2.3.0, 6 runs; without phpgraph, 3 runs:
| With phpgraph | Without | |
|---|---|---|
| Correct answers | 6/6 | 3/3 |
| Tokens per run, median | 110,254 | 170,660 |
| Tokens per run, range | 87,643 to 181,273 | 127,193 to 176,783 |
| Time per run | 15.9 to 27.9 s | 15.9 to 26.8 s |
Where it helps: the same answer for 35 % fewer tokens (median) on the largest project; 3 runs out of 6 answered fromimpact_of alone, the others checked it with one to three searches. Where it doesn't: on the 6 impact tasks of the benchmark,
with 2.2.0, phpgraph gave more right answers (17/18 against 15/18) but used 9.8 % more tokens in total, from −30 % to
+36 % per task, and time was not better. Results vary from run to run: with 2.2.0 the same Akeneo task took 87,000 to
222,000 tokens.
Every result, grouped by version, with the method: docs/BENCHMARKS.md.
Quick start
1. Install the executable (Linux, macOS; it carries its own PHP, none needed):
curl -fsSL https://raw.githubusercontent.com/alpine-ronin/phpgraph/main/install.sh | sh
It checks the SHA-256 and installs to ~/.local/bin. Windows, Composer, PHAR and Docker:
docs/INSTALL.md.
2. Connect Claude Code. From your project directory:
phpgraph mcp-config claude
It prints a claude mcp add phpgraph -- ... command with the paths filled in (run it), an .mcp.json to share
with the team instead, and a line for CLAUDE.md telling the agent to call phpgraph before grep. Codex, Cursor,
Sherpa and other MCP clients: phpgraph mcp-config codex|cursor|sherpa|json.
3. Ask. The graph is built on the first call, then kept up to date as you edit.
What you can ask
- What breaks if I change this method?
impact_oflists every dependent, nearest first, callers through the
interface it implements included, the routes reaching it and the tests to run. - How does this feature work?
outlinegives the classes, the routes running into them, the behaviour read in
their bodies, the wiring and the tests in one answer, so the agent reads only the files with non-obvious logic. - Which handler receives this message, which controller serves this route? Senders, messages and handlers are
linked for Symfony Messenger, Laravel, Ecotone, PrestaShop, WordPress hooks and your own buses; routes to their
controllers, HTTP calls to the routes they reach. - Who calls this, in a large or old codebase? Receivers are typed from return types, docblocks, generics,
branches and the signatures ofvendor/, and PHP 4 and 5 syntax is parsed.
What it is not
- Not a runtime tool. It reads code and configuration, never runs them: services built at runtime (compiler
passes, ids computed at runtime) and dynamic calls ($this->$name(),__callwithout@method) stay unresolved. - Not every framework. Symfony, Laravel, Ecotone, PrestaShop and WordPress conventions are recognised, plus
generic ones (handler attributes,*Handler,*Bus); others get the call graph only. Only PHP files are read. - Better with
vendor/. Without installed dependencies, call chains stop at the first one. - PHP versions. The project you analyse can be any PHP version, PHP 4 syntax included, and its PHP does not need
to be installed. phpgraph itself needs no PHP as an executable or in Docker, and PHP 8.5 or newer with Composer or
the PHAR.
The full list: docs/LIMITATIONS.md.
Documentation
- Install: every method, every agent
- MCP tools: the 8 tools, 4 listed by default
- Command line:
build,impact,outline,check,serveand their options - Graph schema and confidence levels: relations,
EXTRACTED/INFERRED/AMBIGUOUS, how it works - Architecture rules: layers,
phpgraph checkin CI,phpgraph.yaml - Frameworks: what is recognised, microservices, XML action routing
- Benchmarks: agents with and without phpgraph, other code graphs, the measurement corpus
- Limitations and FAQ
- Contributing, code architecture,
library providers, stability, changelog - The previous README, kept unchanged
License
MIT.
Reviews (0)
Sign in to leave a review.
Leave a reviewNo results found