No CMS logins. No dev tickets. You ask in plain language, Claude makes the change through an MCP server, and Cloudflare ships it to the world — usually in seconds. Watch it happen below.
A simulation of a real request — same steps we'd run on your live site.
Plain language, in chat
Edits files, commits, deploys
Global redeploy in seconds
Visitors see it instantly
…then Claude reads the analytics back through MCP and suggests the next change. The loop closes — insight → action → insight.
Each of these is a single message. The MCP server does the rest.
New section written, styled to the brand, and published.
Copy updated and deployed — ready for an A/B read.
A new testimonial or page scaffolded from your notes.
Claude reads analytics via MCP and answers in plain English.
Git history makes any change instantly reversible.
Titles, meta and headings refined and shipped.
Claude connects to a handful of MCP servers — each one a small, permissioned bridge to a system.
# ~/.claude/mcp.json — the bridges Claude is allowed to use { "mcpServers": { "filesystem": { // reads & edits the site's source "scope": "public/**/*.html, /assets/*.css" }, "git": { // versions every change — instant rollback "actions": ["commit", "push", "revert"] }, "cloudflare": { // ships it worldwide "deploy": "pages deploy public --project metamorphosis" }, "analytics": { // closes the loop with real data "reads": ["pageviews", "top_pages", "exits"] } } }
This entire page — the layout, the live demo, the copy — was built and deployed to Cloudflare through exactly the loop it describes. The request was one sentence: "build a page showing how websites can be managed via Claude and MCP."
We'll set up the MCP loop on your site — with the guardrails your team is comfortable with.
Book a 60-minute consult