How to Deploy a Website with Claude Code (No GitHub)

Build the site into dist/, connect Wibe as a remote MCP server, authorize it with /mcp, then ask the AI coding agent to publish that folder. A static website can reach a live URL without a GitHub handoff or a second hosting dashboard.

1. Step 1BuildCreate dist/index.html
2. Step 2ConnectAuthorize the Wibe MCP
3. Step 3DeployPublish and check the URL

Before you deploy: make sure it is a static site

Claude Code is an AI coding agent, not a hosting service. You can use Claude Code to build a website, a React frontend, or a full-stack application. The tool name does not decide which hosting model the result needs. The output does.

A static website works from files that a browser can download. A landing page, portfolio, documentation site, or client-side calculator usually fits. A web application needs application hosting when it owns authentication, a database, server routes, background jobs, or private API keys.

Ask Claude Code to classify the project before it changes anything:

Inspect this project without changing it. Tell me whether it can run entirely as a static site after a production build. Check for server routes, a database, background jobs, authentication logic, and private server-side environment variables. Also list every local binary image, video, PDF, or font the built site needs. End with either "Ready for the Wibe static publish workflow" or a clear explanation of what blocks it.

Never copy private keys into JavaScript; anything shipped to a browser is public. If the project needs server-side behavior, use application hosting. For the full decision rule, read the difference between a simple site and an application.

Step 1: Build the site into dist/

Wibe receives finished browser files, not the dev server or source repo. Configure the project root to produce a dist directory with dist/index.html as its entry point. CSS and JavaScript can live below it with relative paths preserved.

You do not need to remember whether this website project uses npm run build, Vite, Astro, or another static-site generator. Tell Claude to inspect the package and run its real production command:

Prepare this project for a Wibe deployment. First inspect the existing package scripts and framework configuration. Run the correct production build without changing frameworks. Make sure the final browser files are under dist/ and that dist/index.html exists. Check that asset and internal-link paths will work from a hosted URL, not only the local dev server. Do not publish yet. Report the build command, the files in dist/, and any static-hosting blocker.

A working dev server is not proof that the production bundle exists. Check the actual dist/ directory.

Step 2: Connect Wibe to Claude Code

Add the Wibe connector as a remote HTTP MCP server from the CLI. Run this inside the project folder for project-only scope:

claude mcp add --transport http wibe https://birta.dev/mcp

Use user scope to make the connector available in every project:

claude mcp add --transport http --scope user wibe https://birta.dev/mcp

Start the CLI with claude, run /mcp, choose wibe, and select Authenticate. OAuth opens in a browser. Sign in with the emailed one-time code and allow access. There is no key to paste into the repository.

Verify the connection with claude mcp list, or ask Claude to list your projects. The official Anthropic Claude Code MCP documentation explains remote HTTP and OAuth. Wibe's current Claude Code connection guide remains the current command reference.

Step 3: Publish the Claude Code website

Create a project in the Wibe dashboard if needed. Ask the AI agent to list projects and use the exact chosen name. Every successful publish creates a new version at the same live address.

Use one explicit publish prompt:

Use the connected Wibe tools to list my projects. Ask me to choose if there is more than one plausible project. Re-check that dist/index.html exists and that every file you send is text. Publish the text files under dist/ to the chosen project with the version description "Initial website publish". Do not omit nested CSS or JavaScript files. Return the live URL, version number, preview URL, and every warning exactly as Wibe reports them.

Wibe validates the package before it changes the live site. A missing entry point or other blocking violation rejects the files and leaves the current version unchanged. Success returns a public URL, version number, and preview. Open the URL to check the result.

Check the live site before sharing it

Publish success does not prove that the design, AI-generated client code, links, and browser behavior are correct. Test the live site like a visitor without your local files or sessions.

1. Open the live site in a private browser window and hard-refresh it.
2. Check the home page and every internal route on desktop and mobile.
3. Click navigation, buttons, mail links, and external links.
4. Confirm that CSS, JavaScript, images, and fonts load without 404 errors.
5. Inspect the browser console and network panel for failed requests.
6. Make sure no private API key or secret appears in the built files.

Missing binary assets need a public URL or supported binary upload path; repeating the same text-only publish will not add them.

Add a custom domain

The first publish is live at the standard Wibe project address. You can share that URL immediately or connect a branded domain afterward. In the project dashboard, enter a root domain such as example.com or a subdomain such as www.example.com. Add the exact DNS record shown by Wibe, then click Verify.

A root domain uses the displayed A record; a subdomain uses the displayed CNAME. With Cloudflare, switch the record to DNS only for verification. The custom-domain guide covers the steps. The standard URL keeps working throughout.

Update or roll back without rebuilding the workflow

Iterate in the same local folder. After an edit, build again and publish dist/ to the same project. Add a useful description so the version history explains what changed.

Rebuild the static site and verify dist/index.html. Check that the files are text-only and review the diff in the built output. Publish dist/ to the same Wibe project with the description "Update: [summarize the visible change]". Return the live URL, new version number, preview URL, and warnings. Then list the latest versions so I can see the rollback point.

If the result is wrong, list versions and roll back to the known-good one. This changes which stored version is live without deleting the newer version or altering your local repository.

List the versions of my Wibe project, including which one is live. Do not roll back until you show me the choices. After I choose a version, roll back to it and return the live URL and restored version number.

Do you still need GitHub, Vercel, or Cloudflare?

You do not need them to move a compatible static website from the AI coding tool to Wibe. No repository connection or build settings screen stands between the finished directory and the live site.

GitHub remains useful for source history, pull requests, backups, and team review. Vercel, Netlify, and Cloudflare Pages fit when repository-based continuous deployment or wider platform features matter. A server-backed application needs real backend hosting.

For websites using Claude Code, choose from the output: a small static site can use this direct path; an application or team-owned repository may need conventional Git and cloud infrastructure.

Common Claude Code deployment problems

Wibe reports a missing entry point

The publish payload does not contain dist/index.html. Build from the project root, inspect the configured output directory, and place the finished static files under dist/.

The development server works, but the build fails

Local development can hide server-only routes or broken production imports. Ask Claude Code to fix the build. If it still needs a runtime, use application hosting.

Images or fonts are missing on the live site

Check paths and filename case. PNG, JPEG, WebP, PDF, WOFF, and WOFF2 files cannot travel through this text-only remote tool; use a public asset URL or supported upload path.

Claude cannot see the Wibe tools

Run claude mcp list. If wibe is disconnected, open /mcp and authenticate again. Confirm that the endpoint matches the current guide and its scope includes this project.

Claude selected the wrong project

Stop before publishing. Run list_projects, compare names and addresses, and use the exact chosen name.

Frequently asked questions