Troubleshooting
HTTP 401 with the right password
Section titled “HTTP 401 with the right password”- Check that the Application Passwords section appears in your profile. WordPress hides it on sites without HTTPS, and some security plugins and hosts turn it off.
- Some servers drop the
Authorizationheader before it reaches WordPress. On Apache, re-saving Settings → Permalinks restores the rule that passes it through. On other servers, ask your host. - Use an Application Password, not the user’s login password.
HTTP 403
Section titled “HTTP 403”The user can’t use the MCP server: by default it needs the edit_pages capability (Editor or Administrator).
HTTP 404
Section titled “HTTP 404”WP_API_URL is wrong or the plugin isn’t active.
“redirects to …”
Section titled ““redirects to …””WP_API_URL points to an address your site redirects, for example http:// to https://, or no www to www. Use the final address.
spawn npx ENOENT or env: node: No such file or directory
Section titled “spawn npx ENOENT or env: node: No such file or directory”The client can’t find Node.js. On macOS and Linux this can happen with apps opened from the Dock or the app menu, because they don’t load the PATH set in your terminal. Set the command to the full path that which npx prints, and add PATH with the folder that contains node to the environment variables, for example "PATH": "/opt/homebrew/bin:/usr/bin:/bin".
The AI says a tool is disabled
Section titled “The AI says a tool is disabled”An administrator turned it off in RealMCP → Tools. See Managing tools.
A change in Tools doesn’t show up in the client
Section titled “A change in Tools doesn’t show up in the client”Clients cache the tool list for up to 5 minutes. Reconnect the client.
content_conflict
Section titled “content_conflict”The page changed since the AI read it, or the AI didn’t send the hash. It’s expected: the AI should read the page again with get-page and retry.