Skip to content

MCP 0.4.2 / Support

Troubleshoot MCP

Diagnose authentication, discovery, missing tools, blocked commands, and approvals.

1 min read / Updated August 28, 2026

  • Client cannot connect: verify HTTPS, exact server URL, redirect URI, PKCE S256, proxy headers, and system clock.
  • Administrator receives 401/403: verify the WordPress account, Application Password, capability, and REST authorization header.
  • Tool is missing: confirm its owning add-on, current capability, registration, scope, and Free/Pro profile.
  • Command is blocked: inspect the owner’s remote classification; unknown and browser-only commands cannot be forced through MCP.
  • Approval expired or changed: begin a new call and approve its new exact request.
  • Revoked client still appears active: purge only misconfigured caches, confirm refresh-token rotation, and retest with the revoked credential.

Use Activity timestamps to correlate failures without collecting raw arguments or tokens.

Was this documentation helpful?Your response helps us improve this page.