What is the Query Monitor MCP server?
The Query Monitor MCP server from AcrossAI lets Claude, ChatGPT, Cursor and any other MCP client profile a page, read the environment and check the object cache on your WordPress site. It runs inside WordPress through the free Abilities Manager and MCP Manager plugins, and works through Query Monitor itself — with no third-party relay in between.
Looking for another plugin? Browse all WordPress MCP integrations or the Developer Tools integrations.
What your AI can do with Query Monitor
Query Monitor is the developer panel that shows what one request actually did — its queries, HTTP calls, PHP errors and template. These abilities hand that same view to an AI assistant, so it can profile a page, read the environment and check the object cache without you opening the admin bar.
Profile any page
See a URL’s slowest and duplicated database queries, outbound HTTP calls, PHP errors, the template that rendered it, and its generation time and peak memory.
Read the environment
Get the PHP version and loaded extensions, the MySQL server variables, the WordPress version and active constants, and the server software — without SSH.
Check the object cache
See whether a persistent object cache is connected, which backend and drop-in it uses, and its hit ratio.
Turn Query Monitor on or off
Enable or disable Query Monitor on the site from your assistant, without hunting through the plugins list.
Troubleshooting
Page slow or throwing errors? Three places it hides.
Each of these can slow a page or break it quietly while the page still loads.
The same query runs dozens of times
A duplicated query inside a loop adds up silently. profile-url lists the duplicates and how often each one ran.
An external API stalls the request
One slow wp_remote call blocks the whole page. profile-url reports each outbound call with its time and status.
A silent PHP notice
Notices and doing it wrong calls never reach visitors but still fire. profile-url surfaces them for the page.
Try asking
Paste one into Claude, ChatGPT or Cursor once your site is connected.
“Profile the home page and show me its slowest database queries.”
“Are there any duplicated queries on the blog archive?”
“Which page template renders the shop page?”
“What PHP version and extensions is this site running?”
“Is a persistent object cache connected, and what’s the hit ratio?”
“Turn on Query Monitor so I can debug this page.”
Query Monitor + AI questions
Is there an MCP server for Query Monitor?
Yes. AcrossAI turns your WordPress site into an MCP server with dedicated Query Monitor abilities, so Claude, ChatGPT, Cursor or a local model can profile pages and read diagnostics directly. It’s free on WordPress.org.
Can ChatGPT or Claude profile a page for me?
Yes, once your site is connected over MCP. Ask in plain English and your AI calls the profile-url ability, which fires one same-host request to the page and returns its queries, HTTP calls, errors, template, time and memory.
Is the Query Monitor integration free?
Yes. All of its abilities ship in Abilities Manager, which is free on WordPress.org.
Does it need the Query Monitor plugin installed?
Yes. The abilities read Query Monitor’s own data, so Query Monitor must be active. When it isn’t, each ability returns a clear “not active” message instead of failing.
Who can run these abilities?
Only administrators. Profiling fires a single-use, short-lived session as the administrator running it, so the result reflects that logged-in admin view of the page.
Does it change anything on my site?
No, apart from the on/off toggle. Profiling, the environment snapshot and the object-cache check are all read-only.
Which AI assistants work with it?
Any MCP client: Claude, ChatGPT, Gemini, Grok, Cursor, Claude Code, and local runtimes such as Ollama, LM Studio and Open WebUI.
Does my site data pass through AcrossAI’s servers?
No. Your WordPress site runs the MCP server and your AI client connects to it directly. There is no hosted gateway in the middle.
Is AcrossAI affiliated with Query Monitor?
No. AcrossAI built and maintains this integration independently, using Query Monitor’s public data and WordPress’s own APIs.
