Erstellt durch statische Analyse einen deterministischen Knowledge Graph von PHP-Codebases, damit AI Agents Aufrufe, Routen und die Architektur verstehen können.
Auch bekannt als hbenabdallah/phpgraph
- Stars
- 3
- Tools
- 8
- Downloads, 30 Tage
- —
- Neueste Version
- 2.1.0
- Letzter Commit
- 15. Nov. 2026
- Lizenz
- MIT
Was ist phpgraph MCP?
Erstellt durch statische Analyse einen deterministischen Knowledge Graph von PHP-Codebases, damit AI Agents Aufrufe, Routen und die Architektur verstehen können. Er stellt 8 Tools bereit, etwa overview, query_graph, outline.
Zusammenfassung generiert aus dem README des Projekts
Über phpgraph MCP server
Entwickler, die mit komplexen PHP-Codebases arbeiten, können phpgraph nutzen, um AI Coding Agents einen deterministischen Knowledge Graph ihres gesamten Projekts zur Verfügung zu stellen. Anstatt sich auf Dateisuchen oder Vermutungen zu verlassen, nutzt dieses Tool statische Analyse, um abzubilden, wie verschiedene Teile einer Anwendung interagieren. Es läuft lokal auf deiner Maschine, wodurch dein Code privat bleibt, und verbindet sich via stdio mit MCP Clients wie Claude Code, Cursor, Codex und Sherpa.
Der Server identifiziert spezifische architektonische Details, einschließlich Call Graphs, Dependency Injection Wiring, HTTP-Routen und Message Handler für Frameworks wie Symfony und Laravel. Er unterscheidet zwischen extrahierten Fakten, abgeleiteten Relationen und mehrdeutigen Vermutungen, während er explizit meldet, was er nicht auflösen kann. Durch den Einsatz von Tools wie impact_of und outline können Agents die Auswirkungen einer Codeänderung verstehen oder eine strukturelle Zusammenfassung eines Features erhalten, ohne jede Datei manuell lesen zu müssen.
Was du damit machen kannst
- 1Ausführungspfade von Features nachverfolgenFinde die Sequenz der Aufrufe von einer HTTP-Route bis hin zum finalen Command Handler.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du phpgraph MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenphpgraph MCP in Claude Code installieren
$ claude mcp add phpgraph -- docker run -i --rm ghcr.io/hbenabdallah/phpgraph:2.1.0phpgraph MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"phpgraph": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/hbenabdallah/phpgraph:2.1.0"
]
}
}
}phpgraph MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"phpgraph": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/hbenabdallah/phpgraph:2.1.0"
]
}
}
}phpgraph MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"phpgraph","type":"stdio","command":"docker","args":["run","-i","--rm","ghcr.io/hbenabdallah/phpgraph:2.1.0"]}'phpgraph MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"phpgraph": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/hbenabdallah/phpgraph:2.1.0"
]
}
}
}phpgraph MCP in Codex installieren
$ codex mcp add phpgraph -- docker run -i --rm ghcr.io/hbenabdallah/phpgraph:2.1.0phpgraph MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.phpgraph] command = "docker" args = ["run", "-i", "--rm", "ghcr.io/hbenabdallah/phpgraph:2.1.0"]
phpgraph MCP in Gemini CLI installieren
$ gemini mcp add -s user phpgraph docker -- run -i --rm ghcr.io/hbenabdallah/phpgraph:2.1.0phpgraph MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"phpgraph": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/hbenabdallah/phpgraph:2.1.0"
]
}
}
}phpgraph MCP tools 8
Erkannt aus dem READMEoverviewquery_graphoutlineget_nodeget_neighborsimpact_ofshortest_pathgod_nodes
| overview | — | |
| query_graph | — | |
| outline | — | |
| get_node | — | |
| get_neighbors | — | |
| impact_of | — | |
| shortest_path | — | |
| god_nodes | — |
Automatisierte Checks
Geluften am 13. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbarBestanden
- Open Source Lizenz (OSI)Bestanden
- Commit oder Release im letzten JahrBestanden
- Package-Name ähnelt keinem populären PackageNicht geprüft
- Remote Endpoint nutzt HTTPSNicht geprüft
- Destruktive Tools sind markiertBestanden
- Keine versteckten Anweisungen an das ModellBestanden
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenNicht geprüft
README
Auf GitHub ansehenWhy phpgraph?
An AI agent dropped into an unfamiliar PHP project reads files one by one and greps for names. It misses what matters most in a real codebase: who calls what, which handler receives a message, which controller serves a route, what breaks if a method changes, and which layer depends on which.
phpgraph parses the whole project once (with nikic/php-parser, docblocks with phpstan/phpdoc-parser) and answers those questions from a graph:
- Deterministic facts, not guesses. Every relation is
EXTRACTED(read in the code),INFERRED(resolved from declared types) orAMBIGUOUS(a guess, labelled as such). - It says what it does not know. Unresolved calls, missing
vendor/, messages without handlers: the gaps are reported, so the agent knows when to read the code itself. - Built for DDD and hexagonal architecture, then microservices, then PHP in general: Symfony, Laravel, Ecotone, PrestaShop, WordPress, or plain PHP.
- Private by design. Your code never leaves your machine, and phpgraph never executes it: it only parses it.
Features
- Call graph with type inference: return types, chained calls (
$a->b()->c()), local variables, docblocks (@return,@var), and signatures of yourvendor/dependencies, so chains go through Doctrine, Symfony or Laravel APIs. - Architecture: DDD and hexagonal layers, bounded contexts, layer rules checked in CI (
phpgraph check), and impact analysis (impact_of): what depends on a class or method, and which tests to run. - Messages and events: sender → message → handler for Symfony Messenger, Laravel jobs and events, Ecotone, PrestaShop CQRS, WordPress hooks, domain events and your own buses, from attributes, service configuration (YAML, XML, PHP) or code shape.
- HTTP: routes (Symfony attributes, YAML and PHP routing files, API Platform resources, Laravel route files, controllers named by container service id) linked to controllers, and HTTP calls linked to the routes they reach. A route whose controller class exists neither in the project nor in
vendor/is reported with its routing file. - Dependency injection: what the Symfony container configuration injects beyond constructor types, every service of a tag (
tagged_iterator,#[AutowireIterator]) or a service named by id, from PHP, YAML or XML configuration, including helpers called with literal arguments (Wiring::wire($services, 'sales', ...), evaluated, never run): a validator is linked to the rules it receives. A rule declaring what it accepts (supports(object $input): bool { return $input instanceof CreateEstimateQuery; }, alsocanHandle,accepts…) is kept out of the use cases passing another input to the shared pipeline, the classes the input's properties hold included. An input typed by an interface is any project class implementing it and the parameter types it is passed on to (QueryInterface $querygiven tosetUp(CreateEstimateQueryInterface $query): aCreateEstimateQuery); a guard it cannot read, or a rule running for some of these classes only, is kept, markedsupports() not resolved. - Microservices: one id space per service, and links between services through their contracts: shared message classes, routing keys, HTTP routes.
- API schemas: the operations of OpenAPI (Swagger) documents linked to the routes implementing them, or, for a document of another API, to the HTTP calls of its client; the rpcs of protobuf services linked to the classes implementing their generated interface. What is documented and not implemented, and the routes no document describes, are reported.
impactlists the operations behind a change (the contract its clients rely on),outlinethose a feature serves. - Zero-configuration MCP server: built on first use, rebuilt incrementally when the code changes (about 3 s per edit on an 8,400-file project).
Quick start
1. Install. A single executable, no PHP needed (Linux and macOS on x86_64 and ARM, Windows on x86_64):
curl -fsSL https://raw.githubusercontent.com/hbenabdallah/phpgraph/main/install.sh | sh # latest release
curl -fsSL https://raw.githubusercontent.com/hbenabdallah/phpgraph/main/install.sh | sh -s -- 0.2.0 # a given release
curl -fsSL https://raw.githubusercontent.com/hbenabdallah/phpgraph/main/install.sh | sh -s -- dev-main # the main branch
irm https://raw.githubusercontent.com/hbenabdallah/phpgraph/main/install.ps1 | iex # Windows
$env:PHPGRAPH_VERSION = "dev-main"; irm https://raw.githubusercontent.com/hbenabdallah/phpgraph/main/install.ps1 | iex
The script downloads the binary, checks its SHA-256 and puts it in ~/.local/bin (Windows: %LOCALAPPDATA%\Programs\phpgraph, added to the PATH); PHPGRAPH_INSTALL_DIR changes the directory. Run it again to update. dev-main is rebuilt on every push to main (the edge pre-release). The binary is a static PHP runtime with phpgraph inside, built with static-php-cli.
With PHP 8.5+ installed, or with Docker:
composer require --dev hbenabdallah/phpgraph # or: composer global require hbenabdallah/phpgraph
curl -LO https://github.com/hbenabdallah/phpgraph/releases/latest/download/phpgraph.phar
docker pull ghcr.io/hbenabdallah/phpgraph # nothing else to install
2. Connect your agent. mcp-config prints a ready-to-paste configuration with the paths filled in (vendor/bin/phpgraph when installed with Composer):
phpgraph mcp-config sherpa # Sherpa: a `sherpa mcp add` command, one declaration for every project
phpgraph mcp-config claude # Claude Code: a `claude mcp add` command, or .mcp.json
phpgraph mcp-config codex # Codex: ~/.codex/config.toml
phpgraph mcp-config cursor # Cursor: .cursor/mcp.json, shareable with the team
phpgraph mcp-config json # any other MCP client over stdio
Agents reach for grep first, even with phpgraph connected. mcp-config also prints a line for the instructions file of the project (CLAUDE.md, AGENTS.md) telling the agent to call phpgraph before grep or reading files; the MCP instructions of the server say it too.
With Sherpa, a terminal coding agent, one declaration serves every project: Sherpa starts its MCP servers from the project it runs in.
sherpa mcp add phpgraph -- ~/.local/bin/phpgraph serve
In a Sherpa session, /mcp add does the same, and the tools are there at once. Both write ~/.config/sherpa/mcp.json.
With Claude Code (absolute paths, as mcp-config prints them):
claude mcp add phpgraph -- /home/you/.local/bin/phpgraph serve /path/to/project
3. Ask your agent something like "Give me an overview of this project", "How does an order get placed?" or "What breaks if I change OrderRepository::save?". The graph is built on the first call, then kept up to date.
MCP tools
| Tool | Use it to |
|---|---|
overview |
Start here: Composer stack, namespace tree with layers, bounded contexts, layer-rule violations, messages, HTTP routes (each with method, path, controller and file up to 30, else grouped by path prefix), services, and what the graph cannot see. |
query_graph |
Find the code about a topic when you do not know the class names, by the words of their names (validated finds Validator), with the classes of the feature around the ones it names. A question about routes ("mooc courses routes", "GET /courses") returns the matching routes and their controllers. The families of classes around the answer are counted by folder (ContextRuleInterface: 34 in …), injected lists once (ContextValidator receives 34 ContextRuleInterface). |
outline |
Before explaining a feature: its structural outline, enough to read only the few files with non-obvious logic. The classes it is made of, by namespace and layer, with the first sentence of their docblock, their public signatures, constants and enum cases; the interfaces and base classes around it with their implementations by module (0 stated); the routes running into it, chain by chain, through the closures it runs; behaviour read in the bodies (guarded throws, early returns, branches on constants, loop caps, state compared before and after); the container wiring with service ids; its users, tests counted by module, what no test touches and what nothing uses. About 15 KB; a list cut short names the section that has it all (section behaviour, 1 to 9 KB), and a core full at 45 classes names those it left out. A class used by many (the User model) brings nothing in with it: it shows the methods the feature calls and its attributes naming the feature's classes ($log: Log). A method (OrderService::place) gives what it runs instead: the methods it calls, 3 calls deep, each class with those methods only; hubs (called by 20 classes or more, a singleton's getInstance()) counted, not followed; its behaviour nearest first. |
get_node |
Read one class, method, route or channel with all its relations; tests using it are counted by module. |
get_neighbors |
See what uses a node (in) or what it depends on (out). |
impact_of |
Before a change: every class that depends on a class or method, nearest first, with the lines of the calls; callers through the interface it implements; code depending on the state it writes; the routes reaching it, with each chain; and the tests to run, found through test helpers. It flags the classes no test touches and those nothing in the application uses. |
shortest_path |
See how two pieces of code are connected. |
god_nodes |
Find the hubs most of the code depends on. |
The server tells the agent to call overview first. A path, as an agent sees it, on php-ddd-example:
Shortest path (4 hops):
PUT /courses/{id} --handled_by--> CoursesPutController::__invoke()
--dispatches--> CreateCourseCommand --handled_by--> CreateCourseCommandHandler::__invoke()
--calls--> CourseCreator::__invoke()
Command line
phpgraph build [path] # phpgraph-out/graph.json and GRAPH_REPORT.md
phpgraph overview # stack, structure and gaps
phpgraph impact "OrderRepository::save" # what depends on it, and the tests to run (--all, --section tests, --format json)
phpgraph check # layer rules, for CI: exit code 1 on a new violation
phpgraph explain "PlaceOrderHandler" # a node and its relations (-d in|out)
phpgraph path "StockChecker" "DbalOrderRepository"
phpgraph query "how is stock checked"
phpgraph outline "notification validation" # the outline of a feature (--section flow, --format json)
phpgraph serve [path] # the MCP server, over stdio
phpgraph mcp-config claude|codex|cursor|json [--docker image]
build options: -e to exclude paths (repeatable), --no-vendor not to read dependencies, --no-cache to parse every file again. vendor, node_modules, var, .git and the files ignored by the project's own .gitignore files are skipped; a git repository above the project never applies its rules, so a project copied into an ignored directory is still read. When the directory holds PHP files but every one is excluded, build fails and says so, and every MCP answer starts with that warning instead of serving an empty graph. Memory is unlimited by default; PHPGRAPH_MEMORY_LIMIT=2G sets a limit. The files are parsed by one worker process per processor, with PHP's pcntl extension (in the binaries and the Docker image; not on Windows, where they are parsed one after the other): Sylius builds in 10 s instead of 28 s on a 12-thread laptop. PHPGRAPH_WORKERS=4 sets the number of workers, PHPGRAPH_WORKERS=1 parses in one process. With PHP installed, opcache and its JIT make builds about 20% faster: php -d opcache.enable_cli=1 -d opcache.jit=tracing -d opcache.jit_buffer_size=128M vendor/bin/phpgraph build (the Docker image and the commands printed by mcp-config already use them).
phpgraph MCP Fragen
Wie füge ich phpgraph MCP zu Claude Code hinzu?
Führe claude mcp add phpgraph -- docker run -i --rm ghcr.io/hbenabdallah/phpgraph:2.1.0 in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich phpgraph MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Welche Tools bietet phpgraph MCP?
Er stellt 8 Tools bereit, darunter overview, query_graph, outline, get_node, get_neighbors.
Nutzt phpgraph ein LLM oder Embeddings?
Nein, es nutzt deterministische Fakten aus der statischen Analyse ohne LLM, Netzwerk oder Embeddings.
Bleibt mein Code bei der Nutzung von phpgraph privat?
Ja, dein Code verlässt deine Maschine nie und das Tool parst den Code lediglich, ohne ihn auszuführen.
Wie schnell wird der Graph bei Codeänderungen neu aufgebaut?
Er wird inkrementell neu aufgebaut und benötigt bei einem Projekt mit 8.400 Dateien etwa 3 Sekunden pro Änderung.