Connect your AI
Your AI writes it. Nippy puts it online.
Nippy speaks MCP — the open protocol AI assistants use to call outside tools. Connect once and Claude or ChatGPT can publish what it just built as a real website: it sends the files, and back comes a permanent link like my-thing.nippy.site. Ask for changes and the same address updates in place, so the link you shared keeps working.
claude.ai and ChatGPT connect with a single URL — nothing to install. Claude Code, Claude Desktop and Cursor take one command. And 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.
https://api.nippy.host/mcp
Three ways in
Pick your tool, connect once.
No install — claude.ai & ChatGPT
Add Nippy as a connector
The hosted MCP server works with anything that accepts a remote connector URL — claude.ai on the web, ChatGPT, and any other MCP-capable client. One URL, one consent screen, no Node, no token to copy.
- 1
Paste the connector URL
In your AI tool's connector settings (claude.ai: Settings → Connectors → Add custom connector), paste https://api.nippy.host/mcp and save.
- 2
Approve access
A Nippy consent screen opens: pick the workspace and approve. Publishing and reading are always granted; site settings and analytics are optional toggles. The connection appears under Settings → API & MCP, revocable any time.
- 3
Ask for a website
Say “publish this as a website”. The assistant sends the files and replies with a live link like my-thing.nippy.site — ask for changes and it updates the same address.
One command — Claude Code, Claude Desktop & Cursor
Run the local installer
Desktop tools that speak MCP over stdio use the same tools via the CLI package. One command writes the server entry into the right config file.
- 1
Run npx nippy-mcp
Add --client claude-code or --client cursor for those tools; the default targets Claude Desktop. It signs you in via the browser (or paste a token from Settings → API & MCP) and configures everything.
- 2
Restart the client
Claude Desktop and Cursor pick up the new MCP server on restart; Claude Code sees it immediately in the current project.
- 3
Publish from the conversation
The assistant gets the same publish_site and update_site tools as the remote connector — live URL back in the chat, stable across updates.
Scriptable — terminal & CI
Deploy with the CLI
No assistant required: the same pipeline is a one-liner from any terminal, and a NIPPY_TOKEN environment variable away from running in CI.
- 1
Deploy a folder
npx @nippyhost/cli deploy ./my-site --site my-site publishes a folder, single file or zip and prints the live URL. Run it again to update in place.
- 2
Sign in once
npx @nippyhost/cli login opens the browser and stores a scoped token locally; in CI, set NIPPY_TOKEN in the environment instead.
- 3
Script the rest
--json output, exit codes on quota or conflicts, and commands for listing sites and reading files make it CI-friendly end to end.
What your assistant can — and can't — do
Connected assistants get tools to publish and update sites, list them, read files back, check name availability, and — if you granted the optional scopes — change site settings like passwords and search indexing, or read visitor analytics. What no connection can ever do: delete a site, transfer it, spend money, or manage your account and team. Those actions 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; 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, 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.
Do I need a paid plan?
No. The free plan hosts one live site with 25 MB — plenty for an AI-generated page or artifact. Paid 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?
Same tools, different transport. The connector URL is Nippy’s hosted MCP server — the only path claude.ai web and ChatGPT support, and there is nothing to install. 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, no setup, and nothing expires.