For most people, a website is something you open a dashboard to change. For anyone who built their site with AI, that’s a step backwards - you were just talking to your computer in plain language. Why stop now?
What MCP changes
MCP (the Model Context Protocol) is an open standard that lets an AI assistant use tools. Connect Yetty over MCP and your AI - Claude Code, Cursor, Windsurf, Codex, or Claude and ChatGPT via connectors - gets more than thirty tools it can call on your behalf. Setup is a URL and a key; nothing to install.
After that, running your site sounds like this:
- “Put my site online.”
- “Add a blog post about our Thursday special.”
- “Connect my domain example.com.”
- “How many visits this week? Which page is hottest?”
- “Roll back yesterday’s change.”
Why it’s safer than it sounds
Letting an AI touch your live site would be alarming if changes were irreversible. They’re not. Every change is saved as a version with a plain-language summary of what happened, so you can roll back to any earlier state in one click. Nothing is applied silently, and nothing is ever lost.
You still get a dashboard
Prefer clicking? The dashboard does everything the AI does - edit content, read leads, manage your domain, see analytics. MCP doesn’t replace it; it just means you’re never forced into a dashboard to make a small change. Whichever you reach for, it’s the same site underneath.
That’s the point of building with AI in the first place: you shouldn’t have to become a webmaster to keep your own website current.