Building a WordPress site over MCP
Four tools, one gateway, and a catalog of abilities that the site owner controls. Here is how the connection is shaped.
Delta exposes four permanent tools over MCP. Everything else is an ability, reached through a gateway. The list of abilities is not fixed in the client.
Why a gateway
If every ability were its own tool, the tool list would change each time the site owner enabled or disabled one. Clients cache tool lists. A change on the server would break sessions that were already open.
A gateway moves that list into data. The agent calls discover-abilities at the start of a session and learns what this site can do today. The site owner keeps control, and the connection stays valid.
Orientation first
The first call is always the same. The agent asks for a brief, and gets back the layers, the rules, and the order of operations. It then reads the design context before it writes anything.
This costs one round trip. It saves the agent from inventing a workflow that the site does not support.