WordPress × Model Context Protocol

A WordPress site built by an agent.

AgentShell gives an agent a real WordPress install to work with: a JSON-driven theme, an MCP server that publishes every AgentShell tool, and a change pipeline with staged previews, a durable journal and rollback. This page is not a mock-up. It was written, styled, staged and published over MCP by an autonomous agent that had never seen this site before.

One tool call, end to end
→ tools/call · agentshell_create_page
→ tools/call · agentshell_begin_transaction
→ tools/call · agentshell_set_palette
→ tools/call · agentshell_import_theme
→ tools/call · agentshell_commit_transaction
← { "id": 1004, "result": { "committed": true } }

Every byte on this site arrived through that channel. The agent never wrote to the database, never edited a PHP file and never opened the WordPress admin.

What it is

Three pieces, one channel.

AgentShell is not a page builder with an API bolted on. It is a WordPress theme that keeps its structure in JSON, a plugin that exposes that structure as tools, and a thin daemon that carries JSON-RPC over the wire.

01 · Theme

The shell is data

Three zones — header, main, footer. Header and footer are tri-slot; the main zone is a vertical composition of blocks. Nothing about the layout lives in a template file, so an agent restyles the whole site with a JSON payload instead of a diff against PHP.

02 · Plugin

The tools are the interface

Every agentshell_* tool on one REST endpoint: design tokens, zone composition, widgets, pages, posts, transactions, revisions, snapshots, a content journal, audit history and headless screenshots.

03 · Daemon

The channel is boring

A PHP CLI daemon proxies newline-delimited JSON-RPC from any MCP client to the plugin over authenticated HTTP. WordPress Application Passwords or a static token; no bespoke SDK, no framework, no plugin to install in the client.

The working loop

Six moves, and the tool for each.

This is the sequence the agent that built this site actually ran. It is the same loop for a landing page and for a production change.

01

Observe

Read the live model: zones, widgets, design tokens, content, warnings.

agentshell_inspect
02

Design

Move design tokens, spacing, shape and CSS variables.

agentshell_set_palette
03

Stage

Open a leased transaction; config writes buffer instead of landing.

agentshell_begin_transaction
04

Preview

Diff the staged state against live, then run the doctor on it.

agentshell_preview_transaction
05

Publish

Validate and promote the buffer in one atomic write.

agentshell_commit_transaction
06

Verify

Screenshot the result and read the audit trail.

agentshell_screenshot

Evidence

Numbers from this build.

69MCP tools registered
8pages published
1transaction in the original build, previewed and committed
60 mintransaction lease
0SQL statements by the agent

Nothing here is a screenshot of a mock-up. The palette, the type scale, the header lockup, the navigation menu, every page of copy and both interactive widgets were produced by tool calls against this WordPress install. The pages on this site are WordPress pages and posts, editable by anyone with an admin session — and by any agent that speaks the protocol.

Start here

Point your agent at a WordPress install.

Install the theme and the plugin, point an MCP client at the REST endpoint, and the first call you make is agentshell_inspect. Ten minutes later you have a site you can operate by conversation.