Jamie Street

Posted on Jul 28

Ask Claude to Publish a Website. Get a Permanent Link.

#mcp #ai #claude #webdev

I gave Claude one prompt. Claude wrote a web page and published it. The page is live at a permanent URL. I did not open a dashboard. I did not run a build.

This article shows the full procedure. You can complete it in less than five minutes.

Disclosure: I run Nippy, the hosting service in this article.

What makes this possible

MCP (Model Context Protocol) is an open standard. It lets an AI assistant call external tools. A tool can read data. A tool can also do work in the real world.

Nippy is a static hosting service. You give it files. It gives you a live URL that does not expire. Nippy has an MCP server. When you connect it, Claude gets one new ability: it can publish websites.

The result is a very short path from an idea to a live page:

prompt → Claude writes the files → one tool call → live URL

Set up the connector

There are two paths. Use the one that matches your setup.

Path A: claude.ai in the browser

Open claude.ai.
Go to Settings → Connectors.
Add Nippy as a connector.
Approve the connection.

Path B: Claude Desktop, Claude Code or Cursor

Run the MCP server with one command:

npx nippy-mcp

Add it to your client configuration. For Claude Desktop, the entry looks like this:

{
  "mcpServers": {
    "nippy": {
      "command": "npx",
      "args": ["nippy-mcp"]
    }
  }
}

Restart the client. The Nippy tools are now available.

The Nippy help center has a full guide for each client.

Publish a page

Give Claude a prompt. This is the prompt I used:

Make a small demo page and publish it with Nippy.

Claude then does three things:

Claude writes the HTML file.
Claude calls the Nippy MCP server with the file.
Nippy returns a live URL.

The tool call is simple. This is its shape:

{
  "name": "published-by-claude",
  "files": [
    { "path": "index.html", "content": "<!DOCTYPE html>..." }
  ]
}

The response came back in a few seconds:

{
  "url": "https://published-by-claude.nippy.site",
  "status": "live",
  "note": "Live now. The link does not expire."
}

That page is real. Claude published it while I wrote this article. You can open it here: published-by-claude.nippy.site.

Update the page

A site is not frozen after the first publish. Ask Claude to change it:

Add a dark mode toggle to the demo page and publish the update.

Claude revises the files and publishes again. The URL does not change. Your shared links stay correct.

Why this is useful

Think about the things you make and throw away:

A prototype for a client call.
A chart from one analysis.
A landing page for one event.
A gallery of photographs for your family.

Each one needs a URL for ten minutes of glory. None of them deserves a repository, a pipeline and a deploy configuration. With an MCP connection, the publish step costs one sentence.

There is also a larger point. AI agents can now produce complete artifacts: reports, dashboards, small applications. An artifact that only exists in a chat window is trapped. A permanent URL sets it free. Hosting that agents can operate is the missing piece, and MCP is the interface for it.

Other ways in

The MCP route is one of three. Nippy also accepts:

Drag and drop. Drop a folder on the page. Pick an address. The site is live.
The CLI. One command: npx @nippyhost/cli deploy. CI deploys use a NIPPY_TOKEN secret.

The first publish confirms your email. There is no password.

Try it

Connect the Nippy MCP server with Path A or Path B.
Ask Claude to make a page and publish it.
Open the URL. Share it. It does not expire.

If you publish something interesting, post the link in the comments. I would like to see it.

DEV Community