Nippy

Your AI writes it. Nippy puts it online.

Connect once and Claude or ChatGPT publishes what it just built as a real website — a permanent link like my-thing.nippy.site — then updates it in place when you ask. Pick your tool and follow three steps.

Works with claude.ai on the web — nothing to install.
- 1 In Claude, open Settings → Connectors, then Add → Add custom connector.
- 2 Name it Nippy and paste this as the Remote MCP server URL:
https://api.nippy.host/mcp
- 3 Approve access, then say “publish this as a website”.Full Claude guide

For Claude Code, Claude Desktop & Cursor.
- 1 Run this in your terminal — add --client claude-code or --client cursor; the default targets Claude Desktop. It signs you in through the browser and writes the config.
npx nippy-mcp
- 2 Claude Desktop and Cursor pick up Nippy on restart; Claude Code sees it immediately in the current project.
- 3 Say “publish this as a website” — the live link comes back in the conversation.[Full Claude guide

Nippy speaks MCP — the open protocol AI assistants use to call outside tools. Once connected, your assistant sends the files it just built and back comes a permanent link; ask for changes and the same address updates in place, so the link you shared keeps working. Access is a scoped, revocable token: an assistant can create and update sites, but it can never delete one, touch billing, or change your account.

Assistants rarely get it right first time, and most attempts are throwaway — so drafts don't have to become permanent sites. Ask for a draft and it publishes to apreview: a temporary address that expires 24 hours after its last update, is never listed in search, and doesn't use up one of your sites. Free accounts hold five at a time; every paid plan is unlimited.

Drafts are free— A preview lands at its own temporary address you can open and share while you work on it. Asking for changes updates that same preview and resets its clock.

Keep the one you like— Say the word and the assistant makes it permanent — a real site at a name you choose, with no expiry, or replacing the contents of a site you already have.

Shared links survive— If you sent someone the preview link before making it permanent, it keeps working — it redirects to the finished site rather than breaking.

The same publish pipeline is a one-liner from any terminal, and a NIPPY_TOKEN environment variable away from running in CI.

npx @nippyhost/cli deploy ./my-site --site my-site