Publish from Claude with the MCP server
Updated 3 July 2026
Claude can publish websites directly once it is connected to Nippy over MCP, the open protocol assistants use to call outside tools. On claude.ai in the browser the connection is one URL: add https://api.nippy.host/mcp as a custom connector, approve access on the consent screen, and asking for something like “put this page online” is enough — nothing to install. Claude Desktop, Claude Code and Cursor connect with one command instead: npx nippy-mcp. Either way, the assistant sends the files it just wrote, and back comes a live link such as my-thing.nippy.site that can be shared immediately and never expires.
Updates work the same way, in conversation: ask for a change and the site is edited in place, so the address stays stable however many times the page is revised. The free plan covers one live site with 25 MB of space — far more than a typical artifact or generated page needs. Access is a scoped, revocable token: the assistant can create, update and list sites, but it can never delete a site, change billing, or touch account settings. Those stay in the dashboard, by design, no matter what the assistant is asked to do. Every way of connecting — including ChatGPT and the terminal — is collected at nippy.host/mcp.
Step by step
- 1
On claude.ai: add the connector
In Claude, open Settings → Connectors, then Add → Add custom connector. Name it Nippy and paste https://api.nippy.host/mcp as the Remote MCP server URL. A Nippy consent screen opens — pick your workspace and approve. The connection appears under Settings → API & MCP in the Nippy dashboard, revocable any time. No install, no token to copy — skip straight to step 3.
- 2
On Claude Desktop, Claude Code or Cursor: run the installer
Run npx nippy-mcp for Claude Desktop, or add --client claude-code or --client cursor for those tools, and sign in when asked (or paste a token from Settings → API & MCP in the dashboard). It writes the MCP server entry into the assistant’s config; restart Claude Desktop to pick it up.
- 3
Ask Claude to publish
Say “publish this as a website”. The assistant calls the publish_site tool with the files it wrote and replies with the live address — pick a name in the request (“call it demo-day”) or let one be suggested.
- 4
Iterate at the same address
Ask for changes and the update_site tool edits files in place — the URL never changes. Revoke the connection any time from Settings → API & MCP; the assistant loses access within one request.
Common questions
Which assistants does this work with?
claude.ai in the browser and ChatGPT connect with the remote connector URL (https://api.nippy.host/mcp) — nothing to install, though ChatGPT’s custom connectors need a paid plan with Developer mode turned on. Claude Desktop, Claude Code, and Cursor have one-line installers via npx nippy-mcp. Anything else that speaks MCP over stdio can run the same server with: npx @nippyhost/cli mcp serve. The full list, with setup steps for each, lives at nippy.host/mcp.
Do I need a paid plan?
No — the free plan hosts one live site with 25 MB and a small banner, which suits a shared artifact or generated page. 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 Claude updates the site?
No. Updates are applied in place, so the address you shared keeps working — it simply serves the new content within seconds.
What can the assistant not do?
Tokens carry scopes for deploying, reading, managing site settings, and reading analytics only. Deleting sites, billing, and account or member management are not grantable to a token at all — they always require signing in to the dashboard.
Is giving Claude access safe?
Access is always a scoped token, never your password or session. The claude.ai connector mints one through an OAuth consent screen; the local installer stores one in the assistant’s config on your machine, sent only to the nippy.host API. The dashboard shows each connection’s last use, and revoking one takes effect immediately.
Ready to do it?
Hosting for AI buildersMore guides
- Deploy from the terminal or CI
- Get your first site online
- Share photos as an online gallery
- Connect a custom domain
- My custom domain is taking a while to go live
- Password-protect a site
- Understand site analytics
- Edit your site in the browser
- Share a Claude Artifact at your own link
- Publish a page made with ChatGPT
- Open a Keynote file without a Mac
- Open a Pages file on Windows
- View Word and PowerPoint files in the browser
- How the free trial works
Still stuck?
Our team is happy to help with anything Nippy.