MCP.so
登录

Nippy MCP Server已验证已精选

@Nippy

基本信息

传输方式

Streamable HTTP

认证方式

OAuth

分类

云与基础设施

作者

Nippy

提交者

Jamie Street

关于 Nippy MCP Server

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.

连接信息

https://api.nippy.host/mcp

接入方式

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

Nippy MCP Server 工具

19

Publish files as a new PERMANENT website on nippy.site — returns the live URL, no expiry. Use only when the user clearly wants a lasting result; for drafts, iterations, or unclear intent, publish_preview is the right verb (cheap to discard, easy to keep). For a single-page artifact, pass one file named index.html. Small binaries (images, PDFs) go inline with encoding="base64"; anything bigger via start_upload. The free plan hosts 1 live site (25 MB); errors state limits honestly — relay them.

Update files on an existing site in place — the URL stays the same. Only the listed files change; pass deletePaths to remove files. Small binaries go inline with encoding="base64"; bigger ones via start_revision.

Start publishing a NEW site with files of any type and size (binaries included): declares the files and returns presigned PUT URLs to upload the bytes directly. The PUT URLs point at Cloudflare R2 storage (hosts under r2.cloudflarestorage.com) — sandboxed environments must allow egress to that domain. For small text or base64 files, publish_site is simpler. Complete with finalize_upload, or abandon with abort_upload.

Start updating an EXISTING site with files of any type and size: returns presigned PUT URLs for the declared files; deletePaths removes files in the same revision. Complete with finalize_upload, passing the same siteId there.

Finish a start_upload or start_revision batch after every file has been PUT. Verifies each declared file landed at its exact size; failures list what is missing or mismatched, and a rejected batch must be started again.

Abort a pending batch from start_upload or start_revision — nothing is published and the staged bytes are cleaned up. Use when an upload went wrong instead of leaving the batch to time out (15 minutes). Pass previewId for a preview batch.

List everything published from this Nippy account, in two groups: permanent sites (no expiry) and temporary previews (expiry times shown).

List the files currently on a site (siteId) or a preview (previewId) — pass exactly one.

Read a text file (≤1 MB) from a site (siteId) or a preview (previewId) — pass exactly one. Useful before editing with update_site / update_preview.

Publish files as a TEMPORARY preview at a random <slug>.preview.nippy.site address. It serves for 24 hours; every update_preview resets the clock and keeps the same URL — prefer updating an existing preview over minting a new one, unless the user asks for a fresh address. Use this for drafts, iterations, and unclear intent: when unsure between site and preview, a preview is the cheap mistake — tell the user how to make it permanent, or ask. Free accounts hold up to 5 active previews; paid plans have no cap.

Update files on an existing preview — same URL, and its 24-hour clock resets. Only the listed files change; pass deletePaths to remove files. Prefer this over publishing a new preview when iterating.

Make a preview permanent. Pass name to mint a NEW site from its files (slot-gated), or siteId to replace an EXISTING site’s content wholesale (address and settings unchanged) — exactly one of the two. The preview URL keeps working as a permanent redirect to the site. Works on live previews and on expired ones still in their grace window.

Discard a preview immediately — its URL stops serving and its files are deleted. Previews also expire on their own after 24 hours, so this is only needed to free a cap slot early or retire a shared link.

Check whether a site name (subdomain of nippy.site) is available.

Set the SEO title/description of a site (paid plans).

Password-protect a site (paid plans). Visitors need the password to view it.

Remove a site's password protection.

Allow or disallow search engines indexing a site (opt-out is a paid feature).

Visitor analytics for a site over an ISO date range (paid plans).

概览

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.

常见问题

1

Nippy 远程 MCP 服务器是什么?

Nippy 的远程 MCP 服务器是一个托管的 Model Context Protocol 端点,地址是 https://api.nippy.host/mcp,AI 助手无需在本地安装或运行任何东西即可连接。

2

怎么连接 Nippy 的 MCP 服务器?

把端点 https://api.nippy.host/mcp 添加到任意支持 MCP 的客户端,比如 Claude Code、Cursor 或 VS Code。本页的接入代码块可以一步配置好每个客户端。

3

Nippy 的 MCP 服务器需要认证吗?

需要。Nippy 使用 OAuth——第一次连接时,你的 MCP 客户端会打开浏览器窗口登录并授权,之后会复用这个凭证。

4

Nippy 的 MCP 服务器用的是哪种传输方式?

Nippy 暴露的是 Streamable HTTP 端点,这是远程 MCP 服务器普遍使用、主流客户端都支持的传输方式。

评论