Nippy

by Nippy

Recommended SSE

2k downloads

Not rated

GitHub Website

Cloud Service

About

Details

Author: Nippy
Downloads: 2,032
Transport: SSE
Categories: Cloud Service

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below

Plugin Name Nippy

Command (node, npx, python, etc.)

Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "nippy": {
            "nippy": {
                "type": "http",
                "url": "https://api.nippy.host/mcp"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "nippy": {
            "nippy": {
                "type": "http",
                "url": "https://api.nippy.host/mcp"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "nippy": {
            "nippy": {
                "type": "http",
                "url": "https://api.nippy.host/mcp"
            }
        }
    }
}

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

{
    "mcpServers": {
        "nippy": {
            "nippy": {
                "type": "http",
                "url": "https://api.nippy.host/mcp"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "nippy": {
            "nippy": {
                "type": "http",
                "url": "https://api.nippy.host/mcp"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "nippy": {
            "nippy": {
                "type": "http",
                "url": "https://api.nippy.host/mcp"
            }
        }
    }
}

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "nippy": {
            "nippy": {
                "type": "http",
                "url": "https://api.nippy.host/mcp"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "nippy": {
            "nippy": {
                "type": "http",
                "url": "https://api.nippy.host/mcp"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "nippy": {
            "nippy": {
                "type": "http",
                "url": "https://api.nippy.host/mcp"
            }
        }
    }
}

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

{
    "mcpServers": {
        "nippy": {
            "nippy": {
                "type": "http",
                "url": "https://api.nippy.host/mcp"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "nippy": {
            "nippy": {
                "type": "http",
                "url": "https://api.nippy.host/mcp"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "nippy": {
            "nippy": {
                "type": "http",
                "url": "https://api.nippy.host/mcp"
            }
        }
    }
}

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "nippy": {
            "nippy": {
                "type": "http",
                "url": "https://api.nippy.host/mcp"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "nippy": {
            "nippy": {
                "type": "http",
                "url": "https://api.nippy.host/mcp"
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "nippy": {
            "nippy": {
                "type": "http",
                "url": "https://api.nippy.host/mcp"
            }
        }
    }
}

From the repository

{
  "mcpServers": {
    "nippy": {
      "type": "http",
      "url": "https://api.nippy.host/mcp"
    }
  }
}

`publish_site`

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_site`

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_upload`

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_revision`

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.

`finalize_upload`

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_upload`

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_sites`

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

`get_site_files`

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

`read_site_file`

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_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_preview`

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.

`promote`

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_preview`

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_site_name`

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

`set_site_meta`

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

`set_site_password`

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

`remove_site_password`

Remove a site's password protection.

`set_search_indexing`

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

`get_site_analytics`

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

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "nippy": {
            "nippy": {
                "type": "http",
                "url": "https://api.nippy.host/mcp"
            }
        }
    }
}

McpServers

{
    "nippy": {
        "type": "http",
        "url": "https://api.nippy.host/mcp"
    }
}

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.

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Details

Jump to

Setting up with Highlight

From the repository

publish_site

update_site

start_upload

start_revision

finalize_upload

abort_upload

list_sites

get_site_files

read_site_file

publish_preview

update_preview

promote

discard_preview

check_site_name

set_site_meta

set_site_password

remove_site_password

set_search_indexing

get_site_analytics

Claude Desktop / Cursor

McpServers

Install

More like this

Aws Kb Retrieval Server

AWS MCP Servers

container-use

container-use

Cloudflare

MCP Gateway

`publish_site`

`update_site`

`start_upload`

`start_revision`

`finalize_upload`

`abort_upload`

`list_sites`

`get_site_files`

`read_site_file`

`publish_preview`

`update_preview`

`promote`

`discard_preview`

`check_site_name`

`set_site_meta`

`set_site_password`

`remove_site_password`

`set_search_indexing`

`get_site_analytics`