GUIDE · 1 NOVEMBER 2026
WordPress and MCP: what works today
The Model Context Protocol (MCP) lets an AI agent use a system through a defined set of tools. WordPress now has an official way to expose itself to agents over MCP. Here is what it does, and when moving to a CMS built for agents is the simpler path.
What MCP is
MCP is an open protocol that connects AI clients such as Claude, Codex and Cursor to external systems. A server describes the tools it offers; the client lets the model call them with the user's permission.
For a website, that means an agent can read and change content through the CMS rather than by editing files or clicking through an admin interface.
The official WordPress MCP Adapter
The WordPress MCP Adapter is part of WordPress's AI Building Blocks initiative. It bridges the WordPress Abilities API to MCP, over HTTP or STDIO.
- Abilities are private until a plugin opts them in for MCP (
meta.mcp.public). - The default server exposes meta-tools to discover, describe and execute abilities at
/wp-json/mcp/mcp-adapter-default-server.
What that means in practice
An agent can do what the installed plugins expose as abilities. What it can do with site building and themes depends on what is exposed on that site.
When to connect WordPress, and when to move
Keep WordPress and connect it if its plugins and ecosystem matter to the site. Move to a CMS built for agents if the goal is that agents build and maintain whole sites, while people edit in a visual editor.
Moving with an agent
Typeroll's WordPress migration is run by the same kind of agent over MCP. It imports content through the WordPress REST API or a helper plugin, rebuilds pages as editable blocks, moves media into your own storage and keeps every URL working.
START BUILDING
Try Typeroll Cloud for 30 days.
Free during the beta. No payment card. After the beta, USD 39 per month, or USD 29 per month billed annually.