Snapy.host

What the Snapy MCP server does

Snapy turns a file or page into a link. The MCP server brings that into your AI assistant. After you connect it, the assistant gets a publish tool. When it builds something, an HTML page, a chart, a small static site, it can host it on Snapy and return a live URL, with no copy-paste and no manual upload.

This is built on the Model Context Protocol (MCP), the open standard for giving an AI assistant new tools. So it works with any MCP client, including Claude Desktop and Cursor.

Add the Snapy MCP server to your AI client

In your MCP client config (for example Claude Desktop's config file), add a Snapy entry:

{
  "mcpServers": {
    "snapy": {
      "command": "npx",
      "args": ["-y", "snapy-mcp"],
      "env": { "SNAPY_API_KEY": "snapy_live_your_key_here" }
    }
  }
}

The server is open source, so you can also run it straight from the repository instead of npx: set command to node and args to the path of the server's index.js. Either way, restart your client and the publish tool appears.

The publish tool

Once connected, the assistant can call publish:

• content (required): the text or HTML to host.
• name (optional): a custom link name, like launch for launch.snapy.page.
• filename (optional): defaults to index.html.

It returns the live link and a private analytics link. So you can say "build a landing page and publish it," and the assistant hosts it and gives you the URL.

No MCP client? Use the publish API (any AI agent)

Any AI tool, agent, or script can publish to Snapy over plain HTTP, no MCP required. This is the simplest way to let an automation or a custom GPT host files and pages.

POST https://api.snapy.host/api/publish
Content-Type: application/json
Authorization: Bearer <your free key>

{ "content": "<h1>Hello</h1>", "name": "my-page", "filename": "index.html" }

The response includes the live url and a private stats_url. There is a machine-readable OpenAPI schema at https://api.snapy.host/openapi.json and https://snapy.host/openapi.json, so you can wire it into a ChatGPT custom GPT action or any agent that reads OpenAPI.

What you can publish

• An HTML page or landing page the AI generated.
• A file you want shared as a link.
• A static site (HTML, CSS, JavaScript) zipped together.
• A chart, a report, a one-pager, or any artifact your assistant produces.

Why this is useful

The hard part of AI-generated work is sharing it. A chat link often needs the other person to log in, and the output is stuck inside the tool. Snapy gives it a clean public link that opens for anyone, on any device, instantly.

New to Snapy? See how Snapy works with Claude and ChatGPT, the developer and AI guide, or just host an HTML file free.

The API key

Publishing needs an API key, whatever the format. Create one in your snapy dashboard under API keys and set it as SNAPY_API_KEY in the config above. The key is free — a confirmed email address is all it asks for.

⚠️ Connector versions before 1.1.0 published without a key and no longer work. The publish API used to accept an anonymous call for anything that was not a web page; that has been closed, because the website has always asked for a confirmed email before a link goes live and the API should not have been the exception.