Nippy

host.nippyPublished by nippy.hostOfficial publisherv1.1.0Updated Oct 24, 2026

Let Claude and ChatGPT publish real websites — iterate in previews, keep the good one.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Nippy is a remote MCP server that lets Claude and ChatGPT publish real websites, iterating in previews and keeping the version you like.

What you can do
Publish real websites from an AI assistant conversation, according to the provider description. Iterate on site versions in previews before settling on one. Keep the version you prefer rather than starting over. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to turn a conversation into a live website and refine it through previews before publishing. Suited to people who prefer iterating on drafts rather than editing files and deploying by hand.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's API host. OAuth authentication is required, so you need a Nippy account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
OAuth grants the server access to your Nippy account, so review the scopes requested during sign-in. Publishing creates publicly reachable websites, so check what content and data end up in a preview before making it live. The manifest lists no tools, so confirm what actions the server can take before connecting.

Installation

In SourceWeft

  1. Open Nippy in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/host.nippy%2Fnippy/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.