Install the htmldrop MCP server, ask Claude Desktop to publish, and get a live shareable URL back. No build step, no deploy pipeline, no signup to start.
claude mcp add htmldrop \
--env HTMLDROP_API_TOKEN=hsk_live_xxxxxxxxxxxxxxxx \
-- npx -y @htmldrop.app/mcp
{
"mcpServers": {
"htmldrop": {
"command": "npx",
"args": ["-y", "@htmldrop.app/mcp"],
"env": { "HTMLDROP_API_TOKEN": "hsk_live_xxxxxxxxxxxxxxxx" }
}
}
}
{
"mcpServers": {
"htmldrop": {
"command": "npx",
"args": ["-y", "@htmldrop.app/mcp"],
"env": { "HTMLDROP_API_TOKEN": "hsk_live_xxxxxxxxxxxxxxxx" }
}
}
}
{
"mcpServers": {
"htmldrop": {
"command": "npx",
"args": ["-y", "@htmldrop.app/mcp"],
"env": { "HTMLDROP_API_TOKEN": "hsk_live_xxxxxxxxxxxxxxxx" }
}
}
}
npx -y @htmldrop.app/mcp
Get your hsk_live_… token at htmldrop.app/dashboard/settings → API tokens.
Fastest path: click ⤓ Add to Claude Desktop above — it downloads a .mcpb extension bundle that installs the htmldrop server with one double-click, no JSON editing required.
hsk_live_… value (shown only once)..mcpb:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonmcpServers and save.
.mcpb.Open Claude Desktop's chat and try any of these:
Claude Desktop didn't read your token. Verify the HTMLDROP_API_TOKEN env value in claude_desktop_config.json is the hsk_live_… string (not the friendly name you gave the token in the dashboard).
Look for a small 🔌 icon in the bottom-right of the message composer — clicking it lists configured MCP servers. If htmldrop is missing, the JSON config has a syntax error; validate it with cat ~/Library/Application\ Support/Claude/claude_desktop_config.json | python3 -m json.tool on macOS.
You've hit your plan's site cap (3 active drops on Free). Delete a drop in the dashboard or upgrade.
In Claude Desktop chat: "List my htmldrop sites." If the tool is wired up, Claude Desktop calls htmldrop_list and replies with your drops.