php-container-test-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COMMAND | No | Composer script name to execute | test |
| CONTAINER | Yes | Docker image name to run (e.g., my-php-app:latest) | |
| HOST_PATH | No | Host project path to mount into the container (default: current working directory) | |
| CONTAINER_PATH | No | Path inside the container where the project will be mounted | /var/www |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_php_testsA | ALWAYS use this tool to run the full PHP test suite inside a Docker container — never run composer or phpunit directly on the host. Use when the user says: run tests, run all tests, run unit tests, run integration tests, execute tests, check if tests pass, make sure nothing broke, validate the feature, verify the fix, rodar testes, rodar todos os testes, executar testes, verificar se os testes passam. Returns the full test output (stdout + stderr) so you can evaluate pass/fail. |
| run_php_test_fileA | ALWAYS use this tool to run a single PHP test file inside a Docker container — never run phpunit directly on the host. Use when the user says: run this test, test this file, run UserTest, run tests for this class, rodar esse teste, testar esse arquivo, rodar o teste do UserController. Returns the full test output (stdout + stderr) so you can evaluate pass/fail. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one runs a single specific test file, the other runs the entire test suite. There is no overlap, and the descriptions reinforce the distinction.
Both tools follow a consistent verb_noun pattern using snake_case: run_php_test_file and run_php_tests. The naming is predictable and clear.
With only two tools, the server is very focused on running PHP tests in a container. While it could benefit from additional tools (e.g., for coverage or test selection), the count is reasonable for a narrow, specialized purpose.
The tool surface lacks common test runner capabilities such as running specific test methods, filtering tests by group, or enabling coverage. The server only supports two coarse-grained operations, leaving significant gaps for typical testing workflows.