Anatomy of an ask: how an agent builds a WordPress site on your Mac
A walk through the 40 seconds between 'spin up a site for the Aurora launch' and a shared, running WordPress install, tool call by tool call.
The hero animation on our landing page isn’t a metaphor — it’s a trace. Here’s what actually happens when you ask Claude to “spin up a WordPress site for the Aurora launch and share it with the team.”
1. The ask becomes tool calls
Your MCP client sees ReDock’s tool surface on localhost:47200: site creation, lifecycle, databases, sharing, deploys, status. The agent plans: create_site → wait for Running → share_site. No YAML, no docker-compose, no sudo.
2. The dock provisions
ReDock creates the site against its own toolchain — PHP pinned per site, a MySQL database created for the install, Caddy fronting it at https://aurora.test with a locally trusted certificate. Nothing touches your system runtimes. The status pill goes Provisioning… → Running only when the process tree is actually alive — honest state is enforced at the API layer, so agents can’t be lied to either.
3. The share
share_site opens a Cloudflare tunnel and binds it to a subdomain — aurora.redock.xyz. The agent gets the URL back and replies to you with it. Your teammate in another timezone clicks it while the site runs on your laptop.
4. The crew keeps going
Because n8n and Remotion dock the same way, the same conversation can schedule the launch post and render the launch video. That’s the part that still feels like a magic trick — but it’s just tools, honestly reported.
Want the full tool list? It’s in the docs.