What this does
With the Snapy connector, Claude can take a page or file it just created and publish it, then give you a live link. You ask Claude to build something and host it, and it comes back with a URL like resume.snapy.page. Claude is good at writing whole HTML pages, small apps, and artifacts, but that output normally lives inside the chat. The Snapy MCP tool turns it into a real address you can open, send, or post.
The tool is named publish. When Claude calls it, Snapy hosts the content as a static page and returns the live url, a private stats_url for analytics, and a token for managing the link. Claude hands you the url and you are done.
How to connect it
Snapy provides an MCP server. In your Claude client (for example Claude Desktop), add it to the MCP settings. A typical entry looks like this:
{
"mcpServers": {
"snapy": {
"command": "npx",
"args": ["-y", "snapy-mcp"]
}
}
}
After you restart the client, Claude has a publish tool from Snapy. The npx command fetches and runs the connector, so you need Node installed on the machine running the Claude client. No API key, no login, and no Snapy account are required, because the publish endpoint is open and free.
If you would rather not run a local connector, you can skip the MCP setup entirely and have Claude call the plain HTTP API instead. The call is a POST to https://api.snapy.host/api/publish with a JSON body, and the developer docs cover every field.
How to use it
Ask Claude something like:
Make a small HTML resume for me and publish it with Snapy.host, then share the link.
Claude builds the page, calls the Snapy publish tool, and replies with a link like resume.snapy.page. You can steer the address by naming it in the prompt, for example "publish it as my-cv," which Claude passes through as the name field to produce my-cv.snapy.page when that name is free.
Other prompts that work well:
Build an interactive quiz in a single HTML file and host it on Snapy.host.
Take the artifact you just made and publish it, then give me the link.
Turn these notes into a clean shareable page and publish it.
Common uses
- Sharing a Claude artifact as a real link instead of a screenshot or pasted code.
- One-page sites, resumes, event pages, and simple portfolios.
- Interactive widgets and small games written as a single self-contained HTML file.
- Formatted documents (proposals, FAQs, changelogs) you want to send as a clean page.
- Quick previews you hand to someone for feedback.
Snapy serves static files only. Anything that needs a live backend, a database, or server-side login will not run on Snapy, so keep what Claude builds to self-contained HTML, CSS, and client-side JavaScript.
Troubleshooting
- The publish tool does not appear. Confirm the config entry is valid JSON and fully restart the Claude client. The tool only loads on a fresh start.
npxfails to run. Make sure Node andnpxare installed and on the system path for the account running the client.- No link came back. The tool needs content to publish. Ask Claude to "publish the full HTML you just wrote," so it passes real content rather than an empty body.
- The name was taken. Pick another name, or drop the name so Snapy assigns a random address.
- You want to host a PDF or image. Binary files must be base64 encoded and sent as
content_base64. The Python guide shows that pattern.
Good to know
- Free, no account, no API key.
- You also get a private analytics link for each page.
- Prefer not to install anything? Any assistant or script can still use the plain publish API over HTTP.
See the full developer docs, browse the other integrations, or read how to share an AI-generated page. Using ChatGPT too? The ChatGPT guide sets up the same thing as a custom GPT action.
Connect it once and everything Claude builds can become a link in the same breath.
