Connect an AI Assistant to WordPress

Connecting an AI assistant to WordPress is not one universal procedure. The exact path depends on the client, the connector, the WordPress environment and the actions exposed by that environment. A complete setup has at least four independent layers: client configuration, transport or MCP server, WordPress authentication and WordPress authorization.

These guides separate the layers so a failure can be diagnosed without replacing the entire stack or bypassing the intended permission boundary.

Already seeing an error message?

Do not restart the entire setup or switch to an administrator account. Identify the exact failing layer in the troubleshooting hub and repeat one small known request.

Choose the connection only after the task

A public-page review does not need authentication. A content inventory may use the REST API. A tool-oriented workflow may use MCP. Local development may use repository and command-line access. The connection method should follow the job, not become the job.

Claude Code and Codex are clients, not WordPress permissions

Claude Code and Codex can be configured to use tools and MCP servers, but this does not automatically create a WordPress identity or grant a WordPress capability. The client can discover a tool while WordPress correctly refuses the requested action.

REST, Application Passwords and MCP

WordPress Application Passwords are per-application credentials intended for API access over HTTPS. MCP can provide a standardized tool interface. The official WordPress MCP Adapter connects registered WordPress abilities to MCP clients. These components solve different layers and should be documented separately.

Verify the smallest known action

After configuration, list available tools or endpoints, run a limited read, confirm the authenticated identity, attempt a known-forbidden write and revoke the credential. Do not begin with a site-wide mutation.

Featured guides

A simple way to get useful results

Get structured site information and inspect selected published pages after connecting. No temporary task is needed for this public reading. You can also browse public pages without the plugin; Agent Control adds structured access and a path toward authorized WordPress work. Authorize a draft task and select any reference content. The assistant can create and revise drafts created by that task. Existing references remain read-only, even when a reference is itself a draft. Review the result in WordPress. Approving a content change does not authorize publication. Solo, Pro or Agency must also have a publication task that covers the still-valid approval. Check the published result yourself.

Continue

First read Analyzing a Website with AI vs Connecting AI to WordPress. If a connection is required, choose the lowest suitable boundary in Which WordPress Access Level Should You Give an AI? before following a client guide.