Deploy a Website or Web App to Hostinger Directly From Claude Code

Get Hostinger Hosting

This guide deploys to Hostinger, so you need an active plan on the account you are about to connect.

Get Hostinger Web App Hosting

Deploy your project to Hostinger directly from Claude Code.

USED IN THIS TUTORIAL

https://www.hostg.xyz/SHJyP

Already have Hostinger hosting? Continue below.

Add the Hostinger Connector

Run this once in your terminal to add Hostinger Connector to Claude Code.

claude mcp add --transport http hostinger https://mcp.hostinger.com

A browser window opens. Sign in to Hostinger and approve the access — there is no API key to create or paste.

Confirm the Connection

Open Claude Code in your project folder and use this prompt before anything else.

Check the Hostinger Connection

Confirm that Claude Code can access Hostinger and show which hosting services are available for this project.

Check the Hostinger connection available in this Claude Code session. Confirm that you can access my Hostinger account and identify the hosting services available for deploying this project. Do not deploy or change anything yet. Only report: - Whether Hostinger is connected - Which relevant hosting options are available - Whether this project can be deployed using the current Hostinger setup Do not modify the project.

If Hostinger is not connected, run the command above again and finish the browser sign-in.

Let Claude Inspect the Project

Claude reads the project itself, so you do not need to look anything up. This only prepares the project — it does not deploy it.

Prepare the Project for Hostinger

Inspect the project, identify how it should run in production, and fix only what is required for deployment.

Inspect this project and prepare it for deployment to Hostinger. Identify: - The framework or project type - The package manager - The correct build command - The production start command, if one is required - The build output directory - Whether this should run as a static site or a web app - Any environment variables required in production Check for deployment-blocking issues and fix only what is necessary. Do not redesign the project. Do not add new features. Do not change working functionality. When finished, summarize the deployment configuration you identified. Do not deploy yet.

Read the summary it gives you before moving on. The next step reuses it.

Send the Project Live

Claude now creates the deployment on Hostinger for you using the settings it just identified.

Deploy the Project

Deploy the prepared project to Hostinger using the connected Hostinger tools and report the live result.

Deploy this project to Hostinger using the connected Hostinger tools. Use the deployment configuration you identified in the previous step. Requirements: - Use the appropriate Hostinger hosting type for this project. - Apply the correct build and production settings. - Add only the environment variables required by the project. - Do not expose secrets in public or client-side code. - Do not change unrelated project files. Complete the deployment and wait for the result. If the deployment fails, inspect the deployment or build logs, fix only the actual deployment issue, and try again. When finished, give me: - Deployment status - Live URL - Hosting type used - Any production settings that were added or changed

Keep the live URL it reports — you need it for the next step.

Open the Live URL Yourself

Spend a minute on the live version before asking Claude to check it.

Homepage loads

Main navigation works

Core app feature works

Page refresh works

Mobile layout

Have Claude Check the Deployment

Now let Claude verify the same deployment and fix anything real it finds.

Check the Live Deployment

Check the live deployment for real production problems and fix only issues that prevent the app from working correctly.

Check the live Hostinger deployment of this project. Focus only on real production issues. Verify: - The site loads correctly - Main routes work - The core application flow works - Required environment variables are available - Server-side functionality works if the project uses it - There are no obvious deployment or runtime errors If something is broken, inspect the relevant Hostinger deployment or runtime information and fix only the real issue. Do not redesign the app or add new features. When finished, report what you checked and whether the deployment is healthy.

Make a Small Change

Ask Claude Code to change one visible thing in the project — a headline or a button label is ideal. Pick something you will spot immediately on the live site.

Publish the Change

You can use the same Hostinger connection to update the existing deployment.

Update the Live App

Deploy the latest project changes to the existing Hostinger app and confirm that the update is live.

Deploy the current project changes to the existing Hostinger deployment. Update the existing app rather than creating a separate unrelated deployment. Keep the existing production configuration unless a real change requires otherwise. After deployment: - Confirm that it completed successfully - Check that the live app shows the change I just made - Report the live URL Do not make any additional changes to the project.

Open the live URL and confirm you can see the change. Use this prompt every time you want the live version to catch up with your project.