No PHP? Use Docker#
This page shows how to point your MCP client at Docker to run ADVISOR when PHP is not on your PATH.
Point the client at Docker#
If PHP is not on your PATH, point the client at Docker instead. Run it from the project root, the folder that holds vendor/, with a hand-written .mcp.json like this:
{
"mcpServers": {
"advisor": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--network",
"none",
"-v",
".:/app:ro",
"-w",
"/app",
"-e",
"ADVISOR_ENABLED=1",
"-e",
"ADVISOR_PROJECT_ROOT=/app",
"-e",
"ADVISOR_GROUPS=stack",
"-e",
"ADVISOR_READ_ONLY=1",
"composer:2.11.1@sha256:8de2184c6de224f4689e8f80ed5f5edaf0030b6b8b7839a22a2bcb6722ac87d0",
"php",
"vendor/bin/advisor",
"mcp"
]
}
}
}
What the config does#
The container has no network, and the project is mounted read-only. ADVISOR_GROUPS=stack keeps the tools that start programs (proctor, upgrade_path) off, because those need the app's own PHP. Some clients want an absolute path in place of . for the mount; give them one. Advice comes in; nothing goes out.
Where to run it#
Run the client from the folder that holds vendor/. If it starts somewhere else, set ADVISOR_PROJECT_ROOT.
Keep it out of git#
This file is written by hand, so keep it out of git like the generated one. install never replaces a different existing advisor entry unless you pass --force, keeps your other servers, and warns when the file is not in .gitignore.