静的解析を通じてPHPコードベースの決定論的なナレッジグラフを提供し、AIエージェントが呼び出し、ルート、およびアーキテクチャを理解するのを支援します。
別名 hbenabdallah/phpgraph
- スター
- 3
- ツール
- 8
- ダウンロード数(30日間)
- —
- 最新バージョン
- 2.1.0
- 最終コミット
- 2026年11月15日
- ライセンス
- MIT
phpgraph MCPとは
静的解析を通じてPHPコードベースの決定論的なナレッジグラフを提供し、AIエージェントが呼び出し、ルート、およびアーキテクチャを理解するのを支援します。 8個のツールを提供しており、overview, query_graph, outlineなどがあります。
プロジェクトのREADMEから生成された概要
phpgraph MCP server について
複雑なPHPコードベースに取り組む開発者は、phpgraphを使用して、プロジェクト全体の決定論的なナレッジグラフをAIコーディングエージェントに提供できます。このツールは、ファイル検索や推測に頼るのではなく、静的解析を用いてアプリケーションの異なる部分がどのように相互作用するかをマッピングします。ローカル環境で動作するためコードのプライバシーが確保され、stdioを介してClaude Code、Cursor、Codex、SherpaなどのMCPクライアントに接続します。
このサーバーは、コールグラフ、依存性の注入(DI)の構成、HTTPルート、およびSymfonyやLaravelなどのフレームワーク向けのメッセージハンドラーを含む、特定のアーキテクチャの詳細を特定します。抽出された事実、推論された関係、および曖昧な推測を区別し、解決できない事項については明示的に報告します。impact_ofやoutlineなどのツールを使用することで、エージェントはすべてのファイルをマニュアルで読み込むことなく、コード変更の影響や機能の構造的な概要を理解できます。
できること
- 1機能の実行パスの追跡HTTPルートから最終的なコマンドハンドラーに至るまでの一連の呼び出しを特定します。
プロジェクトの README から作成されています。すべてのユースケースは、その引用と照らし合わせて確認されています。
phpgraph MCPのインストール方法
フォーマット検証日 2026年11月10日Cursor に追加Gooseに追加Claude Codeにphpgraph MCPをインストール
$ claude mcp add phpgraph -- docker run -i --rm ghcr.io/hbenabdallah/phpgraph:2.1.0Cursorにphpgraph MCPをインストール
~/.cursor/mcp.json
{
"mcpServers": {
"phpgraph": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/hbenabdallah/phpgraph:2.1.0"
]
}
}
}VS Codeにphpgraph MCPをインストール
.vscode/mcp.json
{
"servers": {
"phpgraph": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/hbenabdallah/phpgraph:2.1.0"
]
}
}
}VS Code CLIにphpgraph MCPをインストール
$ code --add-mcp '{"name":"phpgraph","type":"stdio","command":"docker","args":["run","-i","--rm","ghcr.io/hbenabdallah/phpgraph:2.1.0"]}'Claude Desktopにphpgraph MCPをインストール
claude_desktop_config.json
{
"mcpServers": {
"phpgraph": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/hbenabdallah/phpgraph:2.1.0"
]
}
}
}Codexにphpgraph MCPをインストール
$ codex mcp add phpgraph -- docker run -i --rm ghcr.io/hbenabdallah/phpgraph:2.1.0Codex config.tomlにphpgraph MCPをインストール
~/.codex/config.toml
[mcp_servers.phpgraph] command = "docker" args = ["run", "-i", "--rm", "ghcr.io/hbenabdallah/phpgraph:2.1.0"]
Gemini CLIにphpgraph MCPをインストール
$ gemini mcp add -s user phpgraph docker -- run -i --rm ghcr.io/hbenabdallah/phpgraph:2.1.0Gemini settings.jsonにphpgraph MCPをインストール
~/.gemini/settings.json
{
"mcpServers": {
"phpgraph": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/hbenabdallah/phpgraph:2.1.0"
]
}
}
}phpgraph MCPツール 8
READMEから検出overviewquery_graphoutlineget_nodeget_neighborsimpact_ofshortest_pathgod_nodes
| overview | — | |
| query_graph | — | |
| outline | — | |
| get_node | — | |
| get_neighbors | — | |
| impact_of | — | |
| shortest_path | — | |
| god_nodes | — |
自動チェック
実行日 2026年11月13日完全なレポート →自動チェックに合格しました。これはセキュリティ監査ではありません。コードを読み、サーバーに必要最小限のアクセス権を与えてください。 チェックの仕組み
- ソースリポジトリがリンクされており、アクセス可能合格
- オープンソースライセンス (OSI)合格
- 過去1年以内にコミットまたはリリースあり合格
- パッケージ名が有名なパッケージに酷似していない未チェック
- リモートエンドポイントがHTTPSを使用未チェック
- 破壊的なツールがラベル付けされている合格
- モデルへの隠れた指示がない合格
- パッケージおよびその依存関係に重大な勧告なし未チェック
README
GitHubで見るWhy 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のよくある質問
phpgraph MCPをClaude Codeに追加するには
ターミナルでclaude mcp add phpgraph -- docker run -i --rm ghcr.io/hbenabdallah/phpgraph:2.1.0を実行します。すべてのプロジェクトで利用するには--scope userを追加します。
phpgraph MCPをCursorに追加するには
~/.cursor/mcp.jsonを開き、上記のインストールセクションに示すCursor設定を使ってmcpServersの下にサーバーを追加します。
phpgraph MCPが提供するツールは
8個のツールを提供しており、overview, query_graph, outline, get_node, get_neighborsなどがあります。
phpgraphはLLMやembeddingsを使用しますか?
いいえ、LLM、ネットワーク、embeddingsを使用せず、静的解析による決定論的な事実を使用します。
phpgraphを使用する場合、コードのプライバシーは守られますか?
はい、コードがマシンから外部に出ることはありません。このツールはコードを実行することなく解析のみを行います。
コードが変更された際、グラフの再構築にはどのくらいの時間がかかりますか?
増分的に再構築されます。8,400個のファイルを持つプロジェクトでは、1回の編集につき約3秒です。