How I manage 104 client websites alone with Claude and Hostinger MCP
I manage 104 client websites with no team. Here's the exact setup: one folder per site, strict AI rules, and Claude connected to Hostinger MCP.
On this page
Most freelancers hit a wall at around 15 or 20 client websites. After that, updates, broken pages, renewals and client emails eat the whole day.
I manage 104. On my own. No developers, no support team. Not because I work harder, but because Claude does the repetitive work for me, directly on my servers, through the Hostinger MCP connector.
In this post I'll show you the whole system: the setup, the safety rules, what it costs, and the things I never let the AI touch. It works whether you manage 20, 50 or 100+ sites.
Watch the video

▶ Watch "How I Manage 104 Client Websites Alone With Claude × Hostinger MCP" on YouTube
Step 1: Give every site its own folder in VS Code
If you manage many sites, you probably have a spreadsheet: domain, client, platform, hosting renewal date. That's a start, but your AI can't work from it efficiently.
Instead, I keep one folder per client website in Visual Studio Code. Don't let VS Code scare you. It's just a file editor. You open folders and edit what's inside, and by opening them in VS Code you let Claude read every one of them.
Each folder has a markdown file with that site's details and instructions: the domain, the platform, the renewal dates. So when I ask Claude "Which domains expire this month?", it reads those files first, before going anywhere on the web, and comes back with a list after running a single command.
You stop hunting for files. You just tell the AI what you want.
Step 2: Write the rules before you give AI access
This is the part most people skip. Before Claude touches a single site, it reads a short rules file. I share mine free in the video description. It has three levels.
Never, no exceptions, even if I ask in a hurry:
- Never delete a website, database or files
- Never change DNS records or nameservers, and never transfer a domain
- Never touch billing: no buying, canceling or upgrading
- Never read, print or save passwords
- Never touch payments or customer order data on e-commerce sites
- Never contact clients
Wait for me to type "approved":
- Anything on a live website: updates, restores, renewals
- Database edits, subdomains and email forwarders
Do without asking:
- Read-only checks, reports and summaries
- Work on staging and drafts
About passwords: AI can now read whatever is on your computer, including password files if they exist. I keep mine offline, on paper. It doesn't scale, but I'm not taking that risk.
Step 3: Pick hosting that can carry the load
I host on Hostinger's Cloud Professional plan, which gives me 200 GB of NVMe storage. When you choose hosting for many sites, look at storage, CPU and RAM. Right now more than 100 sites use about 7% of my resources while serving 5,000 to 7,000 visitors a day. My Hostinger link with a discount is in the video description.
The sites are a mix of PHP, plain HTML/CSS and WordPress. I didn't hand-build them. I built them with this same AI system, including the WordPress sites.
Step 4: Connect Claude to Hostinger MCP
- Open the Claude app and go to Connectors → Browse connectors.
- Search for Hostinger and pick the official connector.
- Click Connect, sign in, and allow access.
- In VS Code, type / and open MCP servers to confirm the Hostinger connector is there.
In Manage connectors, you choose whether each action needs approval or runs automatically. I use allow all, because the rules file is my safety layer. If you're not confident in your rules yet, keep approvals on.
What it looks like day to day
Deploying a site. I had a one-page dashboard prototype in a client folder and asked Claude to deploy it to Hostinger on a temporary subdomain. Because of the rules file, it asked for my approval first. A minute later the site was live, and it showed up in my Hostinger panel as created one minute ago. I didn't click anything.
Checking a site. Next prompt: Is the site secure? Is SSL installed? How much traffic did it get? Claude came back with a report confirming SSL was active.
Choosing the model. For simple jobs like these I use Sonnet 5.5. For harder problems, like a site that's down for some visitors but not others, I switch to Opus 5.5.
My morning check. Every morning I ask Claude to go through my Hostinger account and tell me whether everything is working and what needs attention. A typical report flags plugins with updates available (for example, a Yoast SEO update on one site) and housekeeping like unused default themes. You can set this up as an automation so it runs on its own.
If you build with Node.js or want version control, add GitHub: Claude pushes the project to GitHub, then deploys it to Hostinger from there.
What it costs
The core of this setup is a $20/month Claude subscription. You can move to the $100 plan for more headroom, but $20 has been enough for me to run more than 100 sites with Claude and Hostinger MCP.
The bigger point
The market for web developers and designers is changing fast, and doing every repetitive task by hand won't keep up. The answer isn't longer hours. It's learning AI, putting it to work, and doing things at scale. Managing 50 or 100 sites alone is now realistic, and it's a skill clients pay for.
When your sites need UI fixes after launch, here's how I use visual feedback for AI coding so Claude can fix them. And if you want to learn this system with me, step by step, join AI Engineer Academy. Here's what's inside.
Follow along
- YouTube: @AgenticAli
- LinkedIn: Ali Amin
- X: @AgenticAli
- Instagram: @agenticali
- Skool: AI Engineer Academy
Keep building.
Ali Amin