NippyVerifiedFeatured

@Nippy

About Nippy

Nippy is drag-and-drop hosting (nippy.host) with an MCP server: connect it and your assistant can publish HTML, folders of photos, or file downloads to a live *.nippy.site URL — and keep editing the site in place at the same address. Tokens are scoped (deploy/read/manage/analytics) and can never delete sites or touch billing. Free plan: one live site, 25 MB, no card, links don't expire.

#hosting #deploy #websites #static-sites #file-sharing #claude

Connection details

https://api.nippy.host/mcp

Setup

claude mcp add nippy --transport http https://api.nippy.host/mcp

Tools

No tools detected

Fetch the live tool list directly from this server's endpoint using the button above.

Overview

What is Nippy?

Nippy is drag-and-drop hosting for websites, photo galleries and file downloads. Connect the MCP server and your assistant can publish what it just built to a live *.nippy.site URL — then keep editing it in place at the same address, so links you've already shared keep working.

Tools

publish_site / update_site — publish files as a site and update them in place (the URL never changes)
start_upload / start_revision / finalize_upload — presigned uploads for files of any type and size
list_sites / get_site_files / read_site_file / check_site_name — inspect your sites
set_site_meta / set_site_password / set_search_indexing / get_site_analytics — settings and analytics (paid plans)

Access

OAuth 2.1 with PKCE, or a scoped API token from https://nippy.host/settings/api-tokens (a free account works). Tokens are scoped — deploy, read, manage, analytics — and can never delete sites or touch billing. Free plan: one live site, 25 MB, no card, links don't expire.

Frequently asked questions

What is the Nippy remote MCP server?

The Nippy remote MCP server is a hosted Model Context Protocol endpoint at https://api.nippy.host/mcp, so AI assistants can connect to it without installing or running anything locally.

How do I connect to the Nippy MCP server?

Add the endpoint https://api.nippy.host/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

Does the Nippy MCP server require authentication?

Yes. Nippy uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.