Deploy Your Claude Code Project Directly From VS Code

Run a Production Readiness Review

Run a quick production-readiness check before deploying.

Production Readiness Review

Detects the framework, runs the production build locally, and returns a deployment readiness report.

Review this project specifically for production deployment. Identify the framework, project type, package manager, build command, start command if needed, build output directory, Node.js/runtime requirements, required environment variables, and any external services such as Supabase, Stripe, Firebase, authentication, storage, or APIs. Then run the appropriate production build and checks locally. Fix only genuine deployment blockers or production configuration problems. Do not redesign the project or change existing functionality unnecessarily. Do not expose, print, commit, or hard-code secrets or API keys. Do not deploy or change any hosting or domain settings yet. When finished, give me a short deployment readiness report with: - framework and project type - build command - start command if required - output directory - required runtime version - what kind of hosting this project needs, for example static file hosting for a built frontend or a Node.js runtime for a server - environment variable names only - external services that need production configuration - whether the project is ready to deploy

Continue when the production build passes or Claude identifies what still needs fixing.

Get Hostinger Web App Hosting

This guide deploys to Hostinger. Get a compatible hosting plan, then return here to continue.

Get Hostinger Web App Hosting

Deploy your project directly from Claude Code through Hostinger.

USED IN THIS TUTORIAL

https://www.hostg.xyz/SHJyG

Already have Hostinger hosting? Continue below.

Connect Claude Code to Hostinger

Run this command in the VS Code terminal to connect Claude Code to Hostinger.

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

Sign in to Hostinger and approve the connection when the browser opens.

Confirm the MCP Connection

Run /mcp and confirm Hostinger is connected.

/mcp

CLAUDE CODE

Deploy to a Temporary Live URL

Use the connected Hostinger tools to deploy the project to a temporary live URL first.

Deploy the Project

Deploys the current workspace through the connected Hostinger MCP tools, with a plan shown before any hosting change.

Using the connected Hostinger MCP tools, deploy the project in my current workspace to a temporary live URL. Before making any hosting change: - inspect the current project and reconfirm the framework, runtime version, package manager, build command, start command, and build output directory - inspect the Hostinger hosting resources that actually exist in my account - identify which of the available Hostinger targets is compatible with this project - if more than one valid hosting target is available, stop and ask me which one to use - never select, replace, or overwrite an unrelated website, and never reuse an existing site without asking me first - show me a short deployment plan before any significant hosting change During deployment: - deploy this project as the source and preserve the current application behavior - keep this first version on a temporary live URL; do not touch my domain or DNS records - configure the build and runtime settings correctly for this project - handle environment variables securely. If you cannot set them safely, stop and tell me exactly which variable names I need to add myself - never print, log, echo, or otherwise expose secret values If the hosting available in my Hostinger account is not compatible with this project, do not improvise and do not downgrade the project to make it fit. Stop and explain exactly what is incompatible and what would be needed instead. When deployment finishes, report: - the Hostinger hosting target used - the temporary live URL - deployment status - detected framework and runtime - environment-variable status, names only - any build or runtime warnings

IMPORTANT

Review the target Claude selects before approving the deployment. Do not overwrite an existing site you still need.

Run a Production Verification Pass

Verify the live version before connecting your real domain.

Production Verification Pass

Checks routes, assets, APIs, environment variables, HTTPS, and logs, then reports what passed and what needs manual testing.

Perform a production verification pass on the deployed project without making destructive changes. Verify everything you can using the live URL, the available Hostinger deployment/build/runtime information, the logs, and the tools you actually have. Anything that requires browser interaction, private credentials, payments, email delivery, uploads, or another action you cannot actually perform must be listed under "Needs manual testing". Check: - the homepage and important routes - direct URL visits and page refreshes for 404 errors - CSS, JavaScript, fonts, images, and other assets - runtime and server errors - APIs and server-side functionality - required environment variables: whether each one is set, names only, never values - forms - authentication if used - database connections if used - HTTPS - deployment, build, and runtime logs Never claim something passed unless you actually verified it. If you could not verify something, say so and put it under "Needs manual testing" instead of assuming. Return the results under: 1. Passed 2. Needs manual testing 3. Problems found If you find a problem, explain the likely cause and propose the smallest safe fix before changing anything significant.

Manually test anything Claude cannot verify, such as login, payments, forms, uploads, or emails.

Connect Your Production Domain

Connect the real domain after the temporary deployment is working correctly.

Connect the Domain and Launch

Inspects the current domain and DNS configuration, shows the required changes, and waits for your approval before applying them.

I am ready to connect my production domain to this deployment. First inspect the current Hostinger deployment, confirm with me which domain is the intended production domain, and inspect the current domain/DNS state for it. Before changing anything: - show me exactly which DNS or hosting settings need to change, and to what values - warn me if that domain currently points to another website, email service, or other important configuration - preserve unrelated DNS records - wait for my approval before any significant change After I approve: - if Hostinger manages the DNS for this domain and the connected tools support the change, make the change yourself - if the DNS is managed by an external provider, do not claim Hostinger can make that change. Tell me exactly which records or settings I need to change, where, and to what values, then wait while I make them myself and verify the result afterwards when you can DNS changes are not always active immediately — propagation can take time. Do not report the domain as live until it actually resolves to this deployment. Once the domain resolves: - confirm HTTPS/SSL is active - confirm the root domain and the www version behave correctly where that applies - check whether Supabase, Firebase, OAuth providers, Stripe, other APIs, CORS/allowed origins, redirect URLs, or webhooks need the production domain added Finish with a short launch checklist showing what is done, what is still propagating, and anything I still need to configure manually.

DNS changes can take time to propagate.

Verify the Final Launch

The domain works

HTTPS is active

Important routes and features work

Production services are connected

No secret keys are exposed in frontend code

Your Claude Code project is now live.

Keep editing locally in VS Code. When you are ready to publish changes, ask Claude to review, build, test, and redeploy the existing Hostinger project.