Publish HTML, static sites and files to .chorus.host, and deploy Cloudflare Workers backends to .worker.chorus.host, from any agent.
Scored across 3 tools
Each tool targets a clearly distinct resource and action: get_docs retrieves documentation, get_site inspects a site's status, and publish_site deploys content. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern: get_docs, get_site, publish_site. The use of 'get' for reads and 'publish' for writes is predictable and readable.
Three tools is on the low end but appropriate for a focused publishing service; each has a clear purpose. However, the lack of additional lifecycle tools like delete or list makes it slightly under-scoped.
The surface covers create/update (publish_site), read/status (get_site), and documentation (get_docs). A delete operation is missing, but versioning and expiration provide workarounds for most use cases.
Return the full beacon.host documentation as Markdown (the same text as https://beacon.host/skill.md): the REST API, the beacon CLI, accounts and API keys, claiming sites, password protection, and Workers, which run server-side JavaScript at .worker.beacon.host for APIs and webhook receivers (GitHub, Stripe), including Hono apps, with no Cloudflare account needed. Read it before building a backend, when the user asks about accounts or limits, or when a task needs something publish_site can't do. Setup for every MCP client: https://beacon.host/mcp
Check a beacon.host site: whether it is live, its URL, whether it has a password, and when it expires. With the site's claim_token (or an API key that owns the site) it also returns the file list, total size, live version and claim link. Use it to confirm a publish worked, to see when an anonymous site expires, or to see what is published at a slug.
Inputs: slug (required), claim_token. Returns: url, slug, files, title, +13 more
Publish a website or any file (PDF, image, HTML, CSS/JS) to a live public HTTPS URL at .beacon.host in one call. Files keep their content type, so PDFs and images open in the browser. No account or API key needed. Use it when the user asks to publish, host, deploy or share a page, website, landing page, report, dashboard, mini app, portfolio, game or demo, wants to share an HTML file or report as a link, wants a temporary preview link that expires on its own, or wants a link to something you made. Send every file with its path (index.html is served at the root) and its content: plain text for HTML, CSS, JS, SVG, JSON and Markdown, or base64 with encoding='base64' for images, PDFs, fonts and other binary files. For a single file, the direct link is https://.beacon.host/. Each call makes a new version live containing exactly the files you send; the previous version is kept and can be rolled back, so nothing is lost. Pass password to put the site behind a username/password prompt (works on anonymous sites too), and expires_at to make the link expire on schedule. Limits: 4 MB of file content per call without an API key, 10 MB with one, and 1,000 files. Anonymous sites stay live for 24 hours. Returns url, page_url, file_url, claim_url, claim_token and expires_at: give the user the claim_url so they can keep the site for free, and save the claim_token. To update a site, call again with the same slug and its claim_token.
Inputs: files (required), slug, title, password, +2 more. Returns: url, slug, updated, file_url, +12 more
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.