PAGUP Agent ControlWordPress access for AI assistants
Start free trial

MCP Is Connected but No WordPress Tools Appear

An MCP transport can be connected while the server exposes no WordPress tools to that client. Tool listing depends on server capabilities, plugin registration, version compatibility, scope and client refresh. WordPress authentication is a separate later layer.

Likely causes

  • The client is connected to an MCP server that does not declare or expose the expected tools capability.
  • The server or plugin intentionally exposes only a subset of tools for the active identity or configuration.
  • A tool name, namespace or input schema changed between versions.
  • The client calls the wrong domain, base path, REST route or MCP endpoint.
  • The documentation or support answer describes a different plugin, client or version.

Diagnostic sequence

  1. Record WordPress, plugin, client, connector and server versions before changing anything.
  2. Request the MCP tool list and record the names and schemas actually exposed by the server.
  3. Compare the requested tool name and inputs with the schema returned by the active MCP server.
  4. Confirm the exact scheme, host, base path and endpoint configured in the client.
  5. Compare the installed version with the plugin’s official changelog and corrected releases.
  6. Compare the authenticated user’s WordPress capabilities with the action required by the route or tool.

Apply the smallest correction

  1. Enable or register only the WordPress tool required by the approved workflow.
  2. Correct the client endpoint, transport, tool name or credential reference without broadening WordPress permissions.
  3. Replace stale instructions with documentation tied to the installed client, plugin and version.
  4. Select the lowest WordPress access level that can complete the approved action.
  5. Escalate with sanitized, versioned evidence when the behavior remains specific to the plugin.

Verify the result

  • The active MCP server lists the expected WordPress tool and current input schema.
  • The authenticated request resolves to the intended dedicated WordPress user.
  • The approved narrow read succeeds with a reproducible response.
  • A deliberately forbidden write remains refused.

What not to do

  • Do not grant administrator access merely to make a connection test pass.
  • Do not confuse successful authentication with permission to perform every WordPress action.
  • Do not treat every 403 as a broken connection; it may be the correct permission refusal.
  • Do not publish claims about remote data use, consent or permissions that have not been verified against the exact version.
  • Do not jump from a limited identity to Full Power without a separate approved workflow, staging and rollback.

Frequently asked questions

Does a connected MCP server guarantee WordPress access?

No. It proves only that one protocol layer is reachable. The server must expose the tool, the client must discover it, WordPress must authenticate the user and the requested action must pass permission checks.

Sources and verification

This page was checked against the following primary sources. Last source review: .