Before you debug a problem, you often need the ground truth about the server it runs on.
debugging/get-environment returns Query Monitor’s environment snapshot: PHP, MySQL, WordPress and the server software — without SSH.
At a glance
| Ability | debugging/get-environment |
| Toolset | Diagnostics — toolset/diagnostics |
| Group | Diagnostics › Query Monitor |
| Requires | Query Monitor, active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.43 and later |
How it works
It takes no parameters.
It reads Query Monitor’s environment collector and returns the PHP version, loaded extensions and key ini limits; the MySQL server and client version with the relevant server variables; the WordPress version and active constants; and the server software.
It changes nothing.
Input
This ability takes no parameters.
What comes back
| Name | Type | What it is |
|---|---|---|
environment | object | The PHP, database, WordPress and server sections of Query Monitor’s environment panel. |
active | boolean | Whether Query Monitor is active on the site. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason. |
Example
Ask your assistant:
What PHP version and extensions is this site running?
It resolves to one call:
{
"ability": "debugging/get-environment",
"parameters": {}
}Worth knowing
- Read-only.
- Request-independent — it reports the server, not any one page.
- Needs the Query Monitor plugin active; without it you get a clear “not active” message.
Related abilities
- Profile URL — what one page actually did
- Get Object Cache Status — whether a persistent object cache is connected
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category