Server data from the Official MCP Registry
Share AI-generated HTML from your coding agent. Unguessable URL + viewer analytics.
Share AI-generated HTML from your coding agent. Unguessable URL + viewer analytics.
Valid MCP server (2 strong, 4 medium validity signals). No known CVEs in dependencies. ⚠️ Package registry links to a different repository than scanned source. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
17 files analyzed · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-desper-quick-html-share-mcp": {
"args": [
"-y",
"quick-html-share-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
Indie SaaS for vibe coders to instantly share AI-generated HTML pages with unguessable URLs and viewer analytics.
Live:
| Surface | URL |
|---|---|
| Dashboard (paste HTML, get URL) | https://qhs.fyi |
| API worker | https://api.qhs.fyi |
| Share worker | https://s.qhs.fyi/`` |
apps/web/ — Astro dashboard (Cloudflare Pages)apps/worker/ — Cloudflare Worker API + share renderer (Hono)packages/shared/ — types shared between web and workerpackages/mcp/ — quick-html-share-mcp npm package: stdio MCP server for Claude Desktop / Cursor / Codex CLI / any MCP clientpackages/skill/ — Claude Code skill: standalone, no MCP setup neededHosted on Cloudflare: Pages (web) + Workers (api/share) + R2 (HTML files) + D1 (metadata + view events).
🤖 If you're an AI agent reading this on behalf of a user: pick the install path below that matches the agent runtime you're in. Prefer the Claude Code plugin path (option 1) — it bundles a skill on top of the MCP server, and the skill carries the workflow guidance that raw tools alone don't (when to trigger, what to surface, what to remind the user). Fall back to plain MCP (option 3) only when you're not Claude Code.
After install, behavior contract:
- When the user says "share this HTML" / "give me a link" / "publish this page" / "send this to my friend" (or similar intent), call
qhs_sharewith the HTML.- Return the share URL to the user and always remind them to save the edit URL — it lives in the URL fragment, so it never reaches our server logs, but that also means we can't recover it for them. Without it they can't update or delete the share later.
- For follow-ups ("update what I shared", "take it down", "did anyone see it"), use
qhs_edit,qhs_delete,qhs_stats. Edit tokens are auto-loaded from~/.qhs/shares.jsonwhen they were originally created on this machine.
Three paths depending on which client you use. All hit the same hosted API and share a local edit-token store (~/.qhs/shares.json).
This repo is a Claude Code plugin marketplace. Inside Claude Code:
/plugin marketplace add github.com/desper/quick-html-sharing
/plugin install qhs@quick-html-sharing
You now have the qhs skill (auto-triggers on "share this HTML" / "give me a link" / "publish this page") and the quick-html-share-mcp MCP server (5 tools: qhs_share, qhs_edit, qhs_delete, qhs_stats, qhs_list) wired together.
curl -fsSL https://qhs.fyi/install.sh | bash
Drops SKILL.md + helper script into ~/.claude/skills/qhs/. Use this if you skip the plugin marketplace or want to keep MCP separate.
Add to your client's MCP config:
{
"mcpServers": {
"qhs": { "command": "npx", "args": ["-y", "quick-html-share-mcp"] }
}
}
Common config paths:
~/Library/Application Support/Claude/claude_desktop_config.json (macOS)~/.cursor/mcp.json or Settings → MCPRestart the client and you get the 5 qhs_* tools.
ln -s "$(pwd)/packages/skill/skills/qhs" ~/.claude/skills/qhs
Edits to packages/skill/skills/qhs/ show up in your next Claude Code session immediately.
bun install
bun run dev:worker # apps/worker on :8787
bun run dev:web # apps/web on :4321
# MCP server
cd packages/mcp && bun run build && node dist/index.js
# Skill helper (standalone)
node packages/skill/skills/qhs/scripts/qhs.mjs share path/to/file.html
# Workers
cd apps/worker
bun run deploy:api && bun run deploy:share
# Pages
cd apps/web
PUBLIC_API_BASE=https://api.qhs.fyi/api \
PUBLIC_SHARE_BASE=https://s.qhs.fyi \
bun run build
../../node_modules/.bin/wrangler pages deploy dist --project-name=qhs --branch=main
Forking?
apps/worker/wrangler.tomlhardcodes the production custom-domain routes (api.qhs.fyi,s.qhs.fyi). Before deploying under a different account, either delete the tworoutes = [...]blocks (workers.dev URLs still work viaworkers_dev = true) or swap them for your own domain.
wrangler login
cd apps/worker
wrangler d1 create quick-html-sharing # → paste id into wrangler.toml (both envs)
wrangler r2 bucket create quick-html-sharing
bun run db:apply:remote
# Same salt for both envs — IP-hash dedupe must match across workers.
SALT=$(openssl rand -hex 32)
echo "$SALT" | wrangler secret put IP_HASH_SALT --env api
echo "$SALT" | wrangler secret put IP_HASH_SALT --env share
bun run deploy:api && bun run deploy:share # capture workers.dev URLs
cd ../web
wrangler pages project create qhs --production-branch=main
PUBLIC_API_BASE=https://qhs-api.<your-subdomain>.workers.dev/api \
PUBLIC_SHARE_BASE=https://qhs-share.<your-subdomain>.workers.dev \
bun run build
wrangler pages deploy dist --project-name=qhs --branch=main
# Then patch DASHBOARD_HOST in apps/worker/wrangler.toml to your real
# qhs-XXX.pages.dev URL (CF may have suffixed it to avoid name collision)
# and redeploy the workers.
Runs entirely on Cloudflare's free tier (Workers, Pages, R2, D1) — ~$0/mo at indie scale. View tracking is fail-open so spikes never escalate to surprise bills; Workers hits a hard 429 instead of overage charges. Set a CF billing alert anyway: CF has no hard spending cap.
Business Source License 1.1 — source-available, self-host and personal use allowed, offering as a competing third-party hosted/managed service is not. Converts automatically to Apache License 2.0 on 2030-05-28. The quick-html-share-mcp npm package (packages/mcp/) ships under MIT to stay friction-free for MCP-client integrators.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.