Impreza MCP can inspect supported app storage and run the native command line of selected catalog apps. This helps an assistant investigate an application after deployment, with separate tools for reading files and running maintenance commands.
Use an app deployment managed through the Impreza Agent. Available storage areas and command lines depend on the deployment. Check what the tools return for your app before following an example.
Start with the symptom and deployment ID
Identify the affected app, what changed and when the problem started. Review its status and logs with the deployment and log tools. A server being online does not establish that the application is healthy.
Check this deployment’s status and recent logs. Summarize the errors and the next read-only checks. Do not restart it or change configuration yet.
Use a limited credential if another agent is doing the investigation.
Discover the storage before reading files
Call impreza_get_app_read with the deployment ID and no read ID to list the readable storage areas. Then use impreza_inspect_app to list a directory, read a file, tail its last lines or search with a pattern.
Paths are relative to a reported storage area, such as data or a named volume. They are not arbitrary host filesystem paths. The inspection job mounts the app storage read-only.
For example, list a reported data area using these arguments:
{
"deployment_id": "dpl_REPLACE_ME",
"action": "list",
"root": "data",
"path": "."
}
Replace the deployment ID and confirm the area exists first. Collect the result with impreza_get_app_read, passing the returned read_id and deployment ID. A pending response means the read has not finished.
Read only the files needed for the investigation. Output is bounded and may be truncated; it is not a complete file export. Configuration and logs can contain credentials or personal data. Ask the assistant to report findings without repeating those values and to treat file content as data, not instructions.
Discover the app’s command line
Call impreza_get_cli_run with the deployment ID and no run ID. It returns the available command lines and examples. The catalog integration currently includes WP-CLI and a database client for WordPress, occ for Nextcloud and Gitea’s command line.
A custom container or another catalog app may have no integrated CLI. This interface is for supported app commands, not a general interactive host terminal. Running a CLI command requires a running app and manage permission, even when the requested command only lists information.
For a supported WordPress deployment, an initial inventory command uses impreza_app_cli:
{
"deployment_id": "dpl_REPLACE_ME",
"cli": "wp",
"args": ["plugin", "list", "--format=csv"]
}
Provide arguments as a list, without adding the wp executable to it. Review the target and command before confirming execution. This example requests plugin information; other commands available through the same tool can modify or delete data.
Collect the result and validate the app
The CLI request returns a run ID. Use impreza_get_cli_run with that ID and the deployment ID to collect the completed output. Do not interpret an accepted request as a successful command, or truncated output as a full database export.
Before a repair, agree on the expected change, prepare an appropriate backup and recovery plan and account for any interruption. Execute the selected change, inspect its result and test the affected app function afterward.
If the issue concerns recurring work, check the scheduled task history before creating another timer. Duplicate tasks can make diagnosis harder and process the same work twice.
Why are logs not enough?
Logs show what an application reports. A targeted file inspection can show whether an expected configuration file or persistent file exists. A native CLI can report application-specific state. Use these sources together, and keep the distinction between observation and an approved change.