WordPress REST API vs MCP: which one your AI should use

If an AI tool needs to read or edit your WordPress site, you have two realistic options: the built-in REST API secured with an Application Password, or an MCP plugin that talks OAuth. The right pick depends on how much trust you’re willing to hand over and for how long, according to a comparison published by Themeisle on 10 November 2026.

Two very different keys to the same door

Application Passwords have shipped inside WordPress core since version 5.6. You generate one from Users > Profile, copy it once, and it authenticates REST API requests as that user. The catch, as Themeisle puts it, is that the credential is unscoped: it inherits whatever role the account has, and it keeps working indefinitely until someone manually revokes it. The only record of its use is a "Last Used" date and an IP address.

MCP (Model Context Protocol) plugins sit on top of the same WordPress APIs but add a permissions and token layer. The official WordPress MCP Adapter, now past its 0.7.1 maintenance release following the 2 October 2026 protocol version, has already passed 60,000 active installs according to the plugin directory. Connecting an MCP client still means installing the plugin, creating an Application Password or your own OAuth layer, and pointing the AI client at a single endpoint — roughly a ten-minute job on WordPress 6.9 or newer, per setup guides reviewed for this piece.

What actually changes for the person managing the site

The practical gap shows up in three places:

Themeisle’s own warning is blunt: treat an Application Password "with the same care as the account’s real password," since it grants full REST API capability the moment it’s copied somewhere insecure.

When each one actually makes sense

Reach for the plain REST API with an Application Password when you’re running a fixed, predictable automation on a dedicated low-privilege account, when you can’t install another plugin, or when the integration is a direct, code-based request you’ve already tested. It’s simpler, and simplicity is a feature when nothing needs to change on short notice.

Reach for an MCP plugin when you’re giving temporary AI access to a writer, a virtual assistant, or a client who shouldn’t have standing admin rights; when you’re running a WooCommerce store and want to stop an assistant from overwriting categories or prices by mistake; or when you need to revoke access cleanly without resetting anyone’s password. If you’re still getting familiar with how the adapter itself works, the earlier look at the WordPress MCP Adapter covers the setup in more detail.

The bigger security picture

Either credential is only as safe as the account behind it and the server it lives on. A full WordPress security checklist is worth running through before handing any AI tool standing access, and sites still on an older core version should weigh that against the access question too — the compatibility notes around WordPress 6.5 are a reminder that credential systems and core updates move together.

None of this requires a complicated decision tree. If the job is narrow, repeatable and yours, an Application Password on a scoped user account still does the work. If the job involves someone else’s hands — even an AI’s — on your site, the extra ten minutes to set up MCP buys a cleaner way to pull the plug later.

Priya Nair

Priya covers hosting, performance, security and backups. She reads changelogs and pricing pages so readers don't have to, and flags what changed since the last update.

Updated on November 11, 2026