Publish from Claude with the MCP server
Updated 2 July 2026
Claude can publish websites directly once it is connected to Nippy over MCP, the open protocol assistants use to call outside tools. Run npx nippy-mcp once, paste an API token from the dashboard, and the connection is configured — after that, asking for something like “put this page online” is enough. 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. Tokens are scoped and revocable: 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.
Step by step
- 1
Create an API token
In the dashboard, open Settings → API & MCP (nippy.host/settings/api-tokens) and create a token with the “Deploy” preset. Copy it when it is shown — that is the only time the full token appears; only a hash is stored.
- 2
Run the one-line installer
Run npx nippy-mcp for Claude Desktop, or add --client claude-code or --client cursor for those tools, and paste the token when asked. 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 token any time from the same settings page; the assistant loses access within one request.
Common questions
Which assistants does this work with?
Claude Desktop, Claude Code, and Cursor have one-line installers. Anything else that speaks MCP over stdio can run the same server with: npx @nippyhost/cli mcp serve.
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, and managing site settings 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 a token safe?
The token is stored in the assistant’s local config on your machine and sent only to the nippy.host API. The dashboard shows each token’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.