Connect your AI
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.
Give Claude the power to publish.
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”.
Free on Nippy.
Give ChatGPT the power to publish.
Connects over the web — nothing to install.
Custom MCP connectors require a paid ChatGPT plan (Plus, Pro, Business, or Enterprise/Edu), enabled under Developer mode. Some advanced capabilities are only on Business and Enterprise.
- 1 In ChatGPT, open Settings → Connectors and turn on Developer mode.
- 2 Add a custom connector, then paste this as the MCP server URL:
https://api.nippy.host/mcp - 3 Approve access, then say “publish this as a website”.
Free on Nippy — the paid plan is ChatGPT’s requirement, not ours.
Run one command.
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.
Free on Nippy.
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.
Iterate in previews, keep the good one
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 a preview: 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.
- 1
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.
- 2
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.
- 3
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.
No assistant needed
Deploy with the CLI
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 What your assistant can — and can't — do
A connected assistant can
- Publish and update sites, and list them
- Read files back and check name availability
- Discard a preview it made — previews are temporary by design
- With the optional scopes: change site settings like passwords and search indexing, or read visitor analytics
No connection can ever
- Delete a site, or transfer one
- Spend money or touch billing
- Manage your account, team or members
These aren't grantable to a token at all — they always require signing in to the dashboard, no matter what the assistant is asked.
FAQ
Questions, answered.
Which AI tools can connect to Nippy?
Anything that speaks MCP. claude.ai on the web and ChatGPT connect with the remote connector URL (ChatGPT needs a paid plan with Developer mode on); Claude Desktop, Claude Code and Cursor have one-line installers via npx nippy-mcp; any other stdio MCP client can run npx @nippyhost/cli mcp serve.
Is it safe to let an assistant publish to my account?
Access is a scoped, revocable token — never your password or session. The assistant can create, update and read sites, discard its own temporary previews, and optionally manage site settings or read analytics. Deleting sites, billing, and account or member management are not grantable at all: they always require signing in to the dashboard. Every connection is listed under Settings → API & MCP with its last use, and revoking takes effect within one request.
What is a preview?
A temporary address for drafts. Assistants iterate, and most attempts are throwaway, so a draft publishes to a preview that expires 24 hours after its last update, stays out of search, and does not use up one of your sites. When one is worth keeping, the assistant can make it permanent at a name you choose — and the preview link then redirects to the finished site instead of breaking. Free accounts hold five active previews; paid plans are unlimited.
Do I need a paid plan?
Not for Nippy. The free plan hosts one live site with 25 MB — plenty for an AI-generated page or artifact — and connecting an assistant is free. (ChatGPT itself only exposes custom connectors on its own paid plans; Claude does not.) Paid Nippy plans add more sites, custom domains, password protection and visitor analytics, and the assistant’s tools can use those features too.
Will the link change when the assistant updates the site?
No. Updates are applied in place, so an address like my-thing.nippy.site keeps working however many times the page is revised — it simply serves the new content within seconds.
What’s the difference between the connector URL and npx nippy-mcp?
The same core tools, different transport. The connector URL is Nippy’s hosted MCP server — the only path claude.ai web and ChatGPT support, with nothing to install, plus large-file upload tools. npx nippy-mcp configures a local server for desktop tools that run MCP over stdio, like Claude Desktop, Claude Code and Cursor.
Do I have to use AI at all?
No — this page is the optional layer. Dragging files onto nippy.host, or pasting HTML into the “Create text file” editor, publishes the same way it always has, no setup at all.
Rather skip the setup? Paste the HTML in yourself — same result, no connection needed.
Connect once. Publish forever.
Free to start — no card required, and your sites never expire.