I set up Hostinger MCP by hand in Claude Code, using an API token instead of the one-click Connector extension. I deployed a small Node.js app, broke it on purpose to test recovery, and put Kodee's live chat and knowledge base through a real technical question. Here is what actually held up.
I set up Hostinger MCP by hand in Claude Code, using an API token instead of the one-click Connector extension. I deployed a small Node.js app, broke it on purpose to test recovery, and put Kodee's live chat and knowledge base through a real technical question. Here is what actually held up.
If you are reading this, you are probably trying to answer one specific question: can you actually trust an AI coding agent to manage your live Hostinger account, and what does it take to connect one without relying on a pre-built extension.
That is exactly what I tested. Hostinger MCP is the integration that lets AI tools like Claude Code, Cursor, and Codex connect to Hostinger services through the Model Context Protocol.
Hostinger Connector is one way into that integration, a one-click, OAuth-based VS Code extension. I did not test Connector here. I tested generating an API token directly in hPanel and wiring it into Claude Code by hand, which is the route you will take if you use Claude Code, JetBrains, or any client without a dedicated extension.
I built a small link-shortener app called LinkSnap, connected it to a real Hostinger account, and walked it through account reads, deployment target discovery, a live deploy, a deliberate failure, and recovery.
Our Hostinger Connector review covers how that OAuth-based extension implements the same underlying protocol, with its own separate set of findings.
MCP Hosting Plans with Hostinger
MCP itself costs you nothing extra and works with any Hostinger plan you already have.
Kodee answered a real terminology question correctly
Cons
Config file breaks easily if pasted incorrectly
Deploy tool failed twice, needed a fallback
Every tool call needs your approval first
Tip Generate your API token with a short expiration and a name you will recognize later. You only get to see the token once, so treat that first screen as your only copy.
Rating Breakdown
Here is how I scored Hostinger MCP across the areas that matter if you are deciding whether the manual setup is worth your time: what it costs you, what you actually get access to, how much friction setup involves, whether it executes correctly, and how good support is when you need it.
The manual setup lets you enable tool categories individually, Websites, Domains and DNS, Subscriptions and Payments, Email Marketing, VPS, and Ecommerce, each becoming its own separate connection rather than one bundled permission grant.
Token generation is quick, but you are on your own if your config file already has content in it, and I hit a stale Node version and a leftover global path before I even got that far.
Account reads caught two hosting orders that had silently expired, and target discovery ruled out both existing candidates with real, checkable reasons instead of guessing.
Kodee answered a real two-sided terminology question with real precision, across four exchanges in about two minutes.
Overall
9.0/10
A more transparent, more hands-on way to connect an AI agent to your Hostinger account, with a deploy pipeline that protected a live site during a failure I caused on purpose.
MCP Hosting Plans with Hostinger
Simplify hosting management with Hostinger MCP, a Model Context Protocol solution that connects compatible AI assistants with Hostinger services. It helps automate tasks, access hosting information, and manage websites, domains, VPS, DNS, and other services through AI-powered workflows.
You will not find a pricing page for Hostinger MCP, because there isn’t one. It is not something you buy on its own.
MCP rides on top of your existing hosting plan
No separate MCP subscription or monthly charge
You still need an eligible hosting or VPS plan
Every plan I tested exposed the same tool categories
No MCP-specific refund policy, since it carries no charge
Tip Do not upgrade your hosting plan just to get better MCP access. Pick your plan based on the websites and resources you actually need, not the AI integration sitting on top of it.
Hostinger MCP Features
Website creation, deletion, and file inspection
Node.js, static site, and WordPress deployment
Node.js build management and vulnerability patching
PHP version and extension configuration
Database creation, repair, and remote connections
Cron job creation and output retrieval
Domain, DNS, subdomain, and redirect management
Subscription and order visibility
Email marketing campaign management
VPS and Ecommerce tools, off by default
If you enable the manual setup path, you choose which of these categories your AI client can see before you ever open it, and each one you turn on becomes its own separate connection in your configuration file rather than one large combined tool set.
Hostinger also documents default rate limits on the underlying API: 60 requests per minute and 1,000 per hour, with the current usage returned in the response headers.
For the kind of interactive, one-task-at-a-time work this review covers, I never came close to either ceiling. If you are planning something more automated, a script running unattended rather than an agent waiting on your approval, this is a real number to design around.
MCP Hosting Plans with Hostinger
Manage your Hostinger services more efficiently with Hostinger MCP. By connecting AI tools directly with Hostinger through the Model Context Protocol, users can automate routine hosting tasks, retrieve account and infrastructure data, and streamline website, domain, and server management.
If you are trying to decide whether you can actually pull off the manual setup yourself, it helps to understand why this section looks nothing like a normal Ease of Use review.
Hostinger MCP has no account of its own to create, no signup form, and no dashboard to tour on first login. It sits on top of a Hostinger account and hosting plan you already have. There is no registration step, because there is nothing to register for beyond the account you presumably already hold.
What Ease of Use actually means here is the connection process itself, turning an account you can already log into into something an AI agent can see and act on. That is why this section goes straight to generating access rather than opening on a signup screen.
Manual setup is not tied to one client either. Hostinger lists:
Claude Code
Cursor
Devin Desktop
Antigravity
And Codex as supported options alongside VS Code’s one-click Connector extension, so you have a real choice here
I picked Claude Code because it runs in the terminal rather than an IDE sidebar, and because it has no dedicated Hostinger extension of its own, which meant the manual, token-based path was the only way in and gave me the cleanest test of that path.
One prerequisite sits before Hostinger even enters the picture, and it is specific to whichever client you pick. Claude Code itself needs Node.js version 22 or newer to run at all. My own machine was still on an older version from a prior project, and I hit engine warnings and a broken install before I ever touched hPanel. That is not a Hostinger problem, but it is a real time cost if your development machine is not already current.
1. Generating the API Token
With Claude Code actually running, I turned to hPanel’s API page, which is now built directly around MCP.
It lists six clients across the top, VS Code, Cursor, Devin Desktop, Antigravity, Claude Code, and Codex, with VS Code getting the one-click Connector extension and every other client, Claude Code included, getting a manual path instead.
Generating the token itself asks for very little:
A name for the token
An expiration period, one month by default
No scope or permission fields on the token
That last point matters to you if you care about access control. It does not live on the token. It lives one step earlier, in a separate picker where you choose which tool categories the connection exposes at all, and that is where I went next.
Detail
Result
Fields required to generate a token
Name and expiration only
Scope selection on the token itself
None
Token visible again after leaving the page
No, shown once
Token table tracks
Name, created date, last used, expiration
2. Choosing Tool Categories and Building the Config
Next, before any config file existed, hPanel asked me to choose which categories of tools the connection would expose:
Websites
Domains and DNS
Subscriptions and Payments
Email Marketing
VPS Hosting
Ecommerce
I enabled only Websites, since that covered everything LinkSnap needed. Each category you enable becomes its own separate entry in the generated JSON, with its own command and its own package name, all pointed at the same token. This is where the manual path genuinely beats a single bundled permission screen: you decide the exact shape of what your AI client can touch before it ever opens, not after.
Then came the part that actually cost me time. hPanel hands you a ready-made JSON block and a file path, ~/.claude.json on Linux, and tells you to paste it in.
My file already had leftover entries from an earlier setup attempt. Pasting the new block in without merging it left me with two top-level objects, which is not valid JSON, and Claude Code would not start until I rewrote the file by hand as one object.
Tip Before pasting Hostinger’s generated config into your MCP file, open the file first and check whether an mcpServers object already exists. If it does, merge the new entry into it rather than pasting a second top-level block on top.
3. Connecting Claude Code
With the config file finally valid, the last step was getting Claude Code itself to pick it up. You will need a separate Claude sign-in here, apart from the Hostinger token entirely, since Claude Code runs on a Claude subscription or API billing. That is a real extra step compared to a browser extension that just reuses a session you are probably already logged into.
Once past that, the connection worked cleanly on the first restart. Asking Claude Code directly what Hostinger tools it had access to returned a complete, correctly grouped list matching the one category I had enabled.
Check
Result
Claude Code login required, separate from Hostinger
Yes
Connected on first restart after fixing the config
Yes
Tool list returned matched the enabled category
Yes
Per-tool-call confirmation required by default
Yes, on every call
That last row will shape your whole experience going forward. Every tool call Claude Code makes, listing websites, checking a build, running a shell command, stops and asks for your yes or no first, unless you switch on auto-approve.
I kept individual approval on through the entire test to get an honest read on the real cost, and one deploy-and-recovery cycle alone needed more than a dozen separate approvals from me.
One more thing to know before you commit any real work to this: there is no sandbox. Every command you approve acts on your live account and your live hosting the moment you say yes.
There is no simulated environment sitting between a prompt and a real change, so a mistaken approval is a real one.
Overall Verdict on Ease of Use
Getting this running took real troubleshooting on my end, not because any single step is hard, but because the manual path assumes a clean config file, a current Node version, and a developer willing to fix both when they are not.
The category-level tool picker is a genuine strength, more precise than one bundled permission grant.
Once connected, expect careful rather than fast. Every tool call waits for you, which is exactly what you want if you are watching closely, and exactly what will slow you down if you are not.
MCP Hosting Plans with Hostinger
Boost productivity with Hostinger MCP, an AI-ready integration designed to connect Hostinger services with compatible AI assistants. It enables smarter automation across hosting, VPS, domains, DNS, websites, and other account services, reducing the need for repetitive manual management.
MCP in Action: Testing Hostinger Through Claude Code
You already know a config file can connect. What you actually want to know is whether the thing on the other end does real hosting work correctly, so I built LinkSnap, a small Express app, and ran it through a complete deployment lifecycle.
Test
What I Wanted to Learn
Read account data
Does it report your account accurately?
Find a deployment target
Does it guess, or does it check first?
Deploy LinkSnap
Can it move a real app from local to live?
Verify the live app
Does it trust its own success claims?
Break the app on purpose
What does the platform do with a bad build?
Recover the app
Can it restore a known-good version cleanly?
LinkSnap’s health endpoint mattered later for one reason: a platform can call a build complete while your application never actually starts.
A live endpoint is the only way you can check that independently instead of trusting a status label.
1. Reading Account Data
I asked Claude Code to list every website and active hosting plan on the account, without giving it any hints.
This account has real complexity: seventeen sites under one order, two more under a second, and two additional sites sitting under orders that no longer show as active.
Check
Result
Total websites listed
21, matched hPanel exactly
Active plans identified
2, matched hPanel exactly
Expired-order sites flagged without being asked
Yes, both correctly identified
It did not just list what I asked for. It noticed two sites belonged to orders missing from the active list, flagged them as likely suspended, and I confirmed both independently in hPanel as expired.
That is more than retrieval, that is your account being audited, not just read.
2. Finding a Deployment Target
This is the test that tells you the most about whether you can trust this thing on a live account.
I asked it to figure out whether I had a Node.js site ready for LinkSnap, without naming any domain myself.
Step
What Happened
Result
Checked first existing Node.js site
Found an active deployment already in use
Correctly ruled out
Checked second existing Node.js site
Found it tied to an expired order
Correctly ruled out
Proposed a new site
Under the correct active order
Accurate
Asked before acting
Offered a free subdomain or a custom domain
Passed
I chose the free subdomain. It generated floralwhite-ferret-411142.hostingersite.com and created the site under the right order, which I verified myself in hPanel afterward.
Everything matched.
3. Deploying LinkSnap
With a confirmed target in place, I packaged LinkSnap into a zip archive and asked Claude Code to deploy it.
The primary deploy tool failed on the first attempt, at the upload step.
Instead of retrying blindly, it checked whether the site’s storage was actually reachable, ruled that out as the cause, and fell back to a different method: requesting a direct upload URL, pushing the archive to it, and triggering the build as a separate step.
Step
Result
Primary deploy tool
Failed at upload
Storage reachability check
Passed, ruled out as the cause
Fallback method
Manual upload URL plus separate build trigger
Fallback result
Succeeded
Self-verification after “build complete”
Ran its own live request, confirmed HTTP 200
My independent check
Homepage and health endpoint both responded correctly
The deploy tool failing on the first try is a real weakness, and I want to say that plainly. What kept it from being a bad outcome is what came after: a real diagnosis, a working alternative, and a live check instead of trusting the status badge.
4. Testing Failure Recovery
This is the section you actually came here for if you are wondering what happens when something goes wrong.
I had Claude Code back up the working package.json, then change the start command to point at a file that does not exist.
It could not edit the live app’s files directly, since there is no file-edit tool exposed for a deployed Node.js app.
Rather than working around that silently, it explained the limit, worked from my local archive instead, showed me the exact one-line change, and waited for my confirmation before touching anything.
Test
Result
Backup created before changes
Yes
Exact change shown before applying
Yes
Broken build deployed
Build reported failed
Live app during the failed build
Stayed up, serving the working version
Live app after an explicit restart
Still serving the working version
Restore from backup
Passed
Redeploy of clean version
Completed, after one retry
Final verification
HTTP 200, healthy response confirmed
This is the most important finding in this review. The platform did not silently accept a broken deployment. It rejected the bad build and kept my last known-good version running the entire time, before and after a restart.
The one honest gap: the build logs only showed successful dependency installation, not the actual missing-file error, so you would still need to look elsewhere to find the specific cause of a real failure.
One smaller thing you should know about is partway through this test, Claude Code referenced an unrelated prior project by name that had nothing to do with this session. It did not change the outcome, but I thought it’s important to flag it rather than leaving out.
Overall Verdict on Testing
If you are trusting an AI agent with a live hosting account, this is the test that should reassure you most. Account reads were accurate and self-auditing, target discovery refused to guess, and a deployment I deliberately broke never took your site down.
The clearest weakness is the primary deploy tool itself, which failed on both attempts I made and needed a manual fallback each time.
MCP Hosting Plans with Hostinger
Take advantage of AI-powered hosting automation with Hostinger MCP. Built around the Model Context Protocol, it allows supported AI tools to interact with Hostinger services, making it easier to manage websites, servers, domains, DNS settings, and hosting-related tasks from a connected workflow.
If you get stuck setting this up yourself, here is what actually happens when you ask Hostinger for help.
Support Channels
Channel
Availability
Notes
Live chat (Kodee, AI)
24/7
Runs on the same Model Context Protocol this review covers, and Hostinger documents it as able to take real account actions, not just answer questions
Live chat (human)
Escalation from Kodee
Available on request inside the same chat window
Knowledge Base
Self-service
support.hostinger.com
Testing Kodee
I asked Kodee a question with a real two-sided answer: is Hostinger MCP its own purchasable product, and how does it actually relate to Hostinger Connector.
You cannot answer this by copying a doc paragraph, since it requires correctly separating a protocol from one specific implementation of it.
Question
Kodee’s Answer
Assessment
Is MCP the same as Connector
No, MCP is the broader integration, Connector is one recommended OAuth-based setup method
Correct and precisely scoped
Is MCP itself purchasable
No, not a separate product or subscription
Correct
Where to find the API token
Account, then API or Dev Tools, generate, name it, set expiration, copy immediately
Correct and specific
What environment variable to use
Named the token variable directly, noted Connector as the alternative that skips it
Correct
The full exchange, four questions and four answers, took about two minutes based on the timestamps.
I did not need to push back, rephrase, or escalate once. A lot of AI support tools handle the easy half of a two-part question and go vague on the harder half. Kodee did not do that here.
Knowledge Base
Hostinger’s knowledge base organizes itself into broad categories: Getting Started, hPanel, AI Builder, Domains, DNS, Files Management, Email, MySQL Databases, Website, VPS, Agency Hosting Plans, Reach, SSL, PHP, Profile Management, Billing, Affiliates and Referrals, Features, cPanel, and About Hostinger.
None of them is dedicated to MCP, so if you go browsing by category, you will not find it that way.
However, searching directly for “MCP” gets you there instead. That search returned twenty results, with the two most relevant articles, WordPress-specific MCP setup and local IDE setup, right at the top.
Mixed in below them were several results only loosely connected, mostly other AI-agent products that happen to mention MCP in passing.
I opened the article that matches this review’s setup directly: “How to set up web hosting MCP on Local IDEs.” It is genuinely well built:
Opens with the Connector extension as the recommended path
Walks through manual setup as a separate method
Includes numbered steps and real config file paths
Provides a full JSON configuration example
Shows a second method using your own AI assistant
The one gap you should know about is the manual walkthrough in this article uses Cursor as its worked example, not Claude Code, even though Claude Code is one of the officially listed clients.
In practice this did not slow me down, since hPanel’s own API page generated a Claude Code-specific file path and JSON block directly, and that turned out to be more current than the article’s example.
If you rely on the article alone and use Claude Code, you will need to adapt the Cursor-specific steps yourself.
Overall Verdict on Support
Kodee handled a real, two-part technical question correctly and quickly, and the knowledge base article behind it is thorough once you search for it by name rather than browse for it by category.
The only real gap is that the flagship setup article favors Cursor as its worked example, so if you use Claude Code you get accurate guidance that was not built with you in mind.
MCP Hosting Plans with Hostinger
Automate and simplify your hosting operations with Hostinger MCP, a solution that bridges Hostinger services with modern AI assistants. From accessing hosting data to managing websites, VPS servers, domains, and DNS configurations, Hostinger MCP helps create faster and more intelligent management workflows.
Yes. Not because the setup was smooth, it wasn’t always, but because of what happened when I gave an AI agent real access to a live account and then deliberately tried to break things.
Account reads caught two silently expired hosting orders without being asked. Target discovery ruled out two unsuitable sites for real, checkable reasons instead of guessing. A deploy pipeline rejected a build I broke on purpose and kept your site running the entire time, before and after a restart.
What stood out most across this whole review was not any single feature working correctly. It was the pattern behind all of them: check first, act second, and say plainly when something could not be verified.
That same pattern showed up in support, where Kodee answered a genuinely two-part technical question correctly on the first try, in about two minutes, without needing to be pushed.
That does not mean this is a finished, frictionless product. The primary deploy tool failed outright on both attempts I made, needing a manual fallback each time.
A config file that already had content in it broke silently until I rewrote it by hand. And there is no sandbox anywhere in this process, every approval you give acts on your live account immediately, which raises the stakes on the same carefulness that makes the results trustworthy in the first place.
Hostinger MCP is worth your time if you want an AI agent that checks before it acts and tells you honestly when it hits a limit, and you are willing to accept some rough edges in the tooling around it.
It’s not worth your time yet if you need something polished and frictionless out of the box, or if a deploy tool that fails on the first try is a dealbreaker rather than a rough edge you can work around.
⭐️⭐️⭐️⭐️⭐️ Absolutely the Best Hosting Experience!
We use Hostinger to host our website, EllasAlterations.com, and it has truly been a blessing. After dealing with constant issues from our previous provider, switching to Hostinger was the best decision we made. Everything just works. It's fast, reliable, and super easy to manage—even for non-tech folks. No more headaches, no more downtime. I’d recommend their hosting services to anyone looking for peace of mind and top-tier support. Thank you, Hostinger!
Hostinger MCP is the integration that lets AI coding tools connect to your Hostinger services through the Model Context Protocol. It is not a separate hosting product, and it works with your existing account rather than replacing hPanel.
Do I need Hostinger Connector to use Hostinger MCP?
No. Connector is one setup method, using OAuth through a browser-based extension. You can also configure the connection manually with an API token, which is the path this review tested, and which currently supports clients including Claude Code, Cursor, Devin Desktop, Antigravity, and Codex.
Is Hostinger MCP free?
Yes. There is no separate charge for the MCP integration itself. You still need an eligible Hostinger hosting, cloud, or VPS plan for the tasks you want an AI agent to actually perform.
Does a completed Hostinger build mean my app is actually working?
In my testing, a build I broke on purpose was rejected rather than deployed, which is a good sign. But the build logs did not show the specific runtime error behind the failure, only that dependency installation succeeded. Check your live app or a health endpoint directly rather than relying on the build logs alone.
Can Hostinger MCP deploy Node.js applications without the Connector extension?
Yes. I deployed and later deliberately broke a Node.js app using only a manually configured API token in Claude Code, with no Connector extension involved. The primary deploy tool failed on both of my attempts and needed a manual upload-and-build fallback each time, which worked successfully.
What happens if my API token expires while an agent is mid-task?
I did not test this directly, since my token was set to a one-month expiration and outlived the whole review. It is a real question to plan for rather than one I can answer from testing: set a calendar reminder to rotate your token before it lapses, since any task relying on it would presumably fail once it expires mid-session.
