Not long ago a unique website meant one of two things: weeks with WordPress and a pile of compromises, or paying a developer and then worrying about who maintains it in two years. With Hostinger web hosting and Claude Code connected to it through Hostinger's MCP server, the whole thing becomes a conversation. In the video I go from an empty plan to a live personal site on its own domain, with a newsletter signup feeding an email marketing tool, in plain English.
Disclosure: Hostinger sponsored the video this guide is written
from. The Hostinger links below are my referral link, and the code
LAMBERT10 gives you an extra discount at checkout. Prices and
discounts are what the checkout showed when I recorded in October 2026; they
change, so check the current ones on the page.
Two things:
The Hostinger MCP server connects the two. It is free and takes one command to add.
Open hostinger.com/lambert and scroll down to the plans. The one to look at is Unlimited Web Hosting (02:24). When I recorded, it was 79% off, and it covers:
A VPS (04:26) gives you a whole virtual server, and with it the whole job: logging in over SSH, configuring and hardening it, keeping the web server running, setting up a database and keeping that running too.
TL;DR: if you just want a website and not the technical tinkering, a VPS is too complicated and unnecessary. Web hosting leaves you only the parts you care about: how the site looks, which pages it has, and its domain name.
Click Choose plan and the checkout opens (05:15).
.shop, .org, .store and
.tech all showed as free for the first year. Not decided yet? You
can claim it later. I did, from Claude Code, further down.LAMBERT10 and click Apply.With the coupon, a year of Unlimited came to about $65 in total, free domain included.
Two ways in (06:43):
hostinger), cd into it and run claude.
For the AI to talk to Hostinger and the hosting you just bought, add the MCP server
(07:28).
Hostinger's instructions have a line for Claude Code (and for VS Code, Cursor,
Antigravity, Codex and others): copy it, paste it into the terminal, press Enter, and
Claude Code confirms it added the hostinger MCP server. That runs the
server locally (it needs Node.js 24 or newer):
npm install -g @hostinger/mcp
claude mcp add hostinger -- hostinger-api-mcp
If you do not want to install anything, Hostinger also runs a hosted server you can add instead:
claude mcp add --transport http hostinger https://mcp.hostinger.com
Commands from Hostinger's api-mcp-server README, checked 2026-11-16.
Start claude in your project folder and run /mcp to check it
worked. hostinger should be listed with three tools: search API
operations, execute an API operation, and execute API operations in sequence. Those
three are how Claude reaches everything in your account.
Before building anything, ask a simple question to prove the connection (08:31):
Do I have a web hosting subscription on Hostinger?
The first time Claude uses the Hostinger tools, a browser page opens and asks you to sign in to your Hostinger account. Click Allow, close the tab when it says authentication succeeded, and go back to the terminal. No API token to copy.
Claude answered with my Unlimited Web Hosting plan, the date it started, the yearly price, that it was active and that auto-renew was off. It also spotted the KVM 2 VPS on the same account. If you get an answer like that, Claude has everything it needs.
Then the actual site (09:35). My prompt, roughly:
Create a website on my Hostinger web hosting. It's a personal brand
website for Dmitry Lambert - you can find information about me on
dmitrylambert.com, my company's website. For now I want a Home page
with the latest videos from my YouTube channel, and an About me page
with a paragraph about who Dmitry Lambert is. Give me the link to
access the website.
Claude read dmitrylambert.com for information about me, built the pages and published them to the hosting through the MCP server. The reply: your website is live, on a temporary Hostinger address, since I had not claimed my free domain yet. Fine for testing, not something to give customers.
The site worked first time: a home page with my latest videos, and an About page. One lesson, though: Claude had pieced the About text together from what it could find online. For a real site, give it the real information you want on the page instead of letting it guess.
Normally, a domain means finding a registrar, buying the name, filling in the registration and then pointing your hosting at it. Here I asked Claude to do it (11:30):
I haven't used the free domain that's included in my plan.
Can you set up dmitry-website.org?
Claude checked the name was available, then stopped: registering a domain needs an owner contact, and the account did not have one yet. It asked for full name, email, phone number and street address. Give it those, and it registers the domain and connects it to the site.
Wait for DNS. It took 5 to 10 minutes for the new domain to start opening the site. That is normal DNS propagation, not a failure, so give it time before you change anything.
The first version worked, but I did not like the design, so I pasted the URL back into Claude with what I wanted changed (12:50):
I don't really like the design. Focus on purple tones. Add some
animations on the homepage, highlight only six YouTube videos, and
completely redesign the About page - right now it looks cheap.
After a hard refresh it looked far more professional: purple, animated, six videos with hover effects, and a proper About page. Then the check people forget: the phone. A site that looks fine on a laptop and terrible on a phone is a very common problem. This one worked properly on mobile without me asking.
Next, a way for visitors to leave their email so I can tell them about new things (14:59):
On the homepage, at the top, add an option for users to subscribe
to news - basically enter their email.
Any public email form attracts bots and spam. Claude dealt with that without being asked, and tested it: an invalid email is rejected, signing up twice shows "already subscribed", and a hidden trap field catches spam bots and silently drops their signups. Signups were saved to a subscriber CSV file on the hosting.
A list is only useful if you can email it. The plan includes AI email marketing free for a year, so I asked Claude how to use it with the signups from my site (16:10). The steps it gave me:
hpanel.hostinger.com), open
Email marketing and start the Starter free trial,
free for one year: up to 100 subscribers and 200 emails a month.
It picks up your website automatically. Continue into Reach.About pasting tokens into the prompt. I did it on camera because it was a test token with a one-month expiry. For a real site, give it a short expiry, store it as a config value on the hosting rather than in your chat history, and revoke it in Reach if it leaks.
Newsletters should come from an address on your domain, like
[email protected], not a generic sender. In email marketing, click
Connect next to your domain and verify the email. I used a separate
subdomain for sending, mail.dmitry-website.org, and let
Set up automatically create the DNS records. After 5 to 10 minutes of
propagation everything turned green. Click auto setup, make a coffee, come back.
Everyone who subscribes on the site appears under Audience → Contacts, and newsletters go out from Campaigns (19:50).
If you have 50 subscribers and no idea what to send them, this is where the "AI" in AI email marketing earns its place. Campaign ideas suggests newsletters based on your website. For mine it came up with "Welcome to the Observability Community", "Master advanced Zabbix monitoring and Grafana" and "Book your observability consulting with Dmitry Lambert". A sensible starting point to edit, rather than a blank page.
That is a real starting point: a personal site on its own domain, redesigned to taste, fine on a phone, with a protected signup form feeding a newsletter tool that can suggest what to send. Every step was a plain-English request, and nothing needed SSH, FTP or a page builder.
If you want to try it, the deal is at
hostinger.com/lambert.
Use LAMBERT10 at checkout.
Twenty-one minutes from choosing a plan to a live site with its own domain and a working newsletter.
If your site is turning into something people depend on and you need to monitor it, automate around it, or build the tool that does not exist yet, that is worth a conversation.