The situation
Where they started.
Routine hosting operations, account provisioning, DNS changes and deployments, were done by hand through the control panel, one screen at a time. The operator wanted the speed of an agent without the risk of an agent deleting a zone or an account on its own.
What FlatClaw does
What was built.
- A first-party MCP connector for the control panel exposing the operations staff actually perform, with each user's own panel credentials scoped to that user.
- Reads and routine changes run directly; destructive or exposing calls pause in the approval queue for a human.
- Deploying a static site becomes a sentence: build, upload, extract, verify, with the agent reporting what it did.
- Every action, approved or denied, recorded in the audit log.
Results
What changed.
- Operations that took a sequence of screens take one request.
- No unattended destructive action is possible by construction.
- Credentials never shared between users or stored in a prompt.
- The connector pattern reused for the operator's other systems.