chorus.host

Publish website

publish_site

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.

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	No	Optional. Subdomain to publish to (3-63 lowercase letters, digits and hyphens). Leave empty for a random one. To update an existing site, pass its slug together with its claim_token.
`files`	Yes	Every file of the site. Each call makes a new version with exactly these files; earlier versions are kept.
`title`	No	Optional human-readable title saved with the site.
`password`	No	Optional. Put the site behind a browser login prompt (HTTP Basic Auth). Works without an account. Give the user the URL, username and password; send the password separately from the link.
`expires_at`	No	Optional. When the site should be deleted: RFC 3339 (2026-10-08T00:00:00Z) or a duration from now (90m, 2h, 7d). Without an API key it can only be earlier than the default 24 hours; with one, any future time.
`claim_token`	No	The claim_token (ctk_...) returned when the site was first published. Required to update an anonymous site.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Live URL of the site root.
`slug`	Yes
`updated`	Yes	True when an existing site got a new version.
`file_url`	No	Direct link to the file when exactly one file was published, e.g. https://<slug>.beacon.host/report.pdf. Paste this one into chat apps so images and PDFs preview.
`page_url`	Yes	URL to open: the site root, or the only HTML page when there is no index.html.
`warnings`	No
`anonymous`	Yes	True when the site is not owned by an account and will expire unless claimed.
`claim_url`	No	Link for the user to keep the site: they open it and sign in with their email.
`expires_at`	No	When the site will be deleted (RFC 3339), unless claimed.
`file_count`	Yes
`next_steps`	Yes	Notes for you, the agent.
`version_id`	Yes
`claim_token`	No	Secret needed to update this anonymous site later. Save it; never put it on the page.
`total_bytes`	Yes
`tell_the_user`	Yes	Plain-English message to relay to the user.
`password_protected`	No	True when visitors must enter the username and password you set.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026

changedOutput schema / properties / file_url / description

Previous value: -"Direct link to the file when exactly one file was published, e.g. https://<slug>.chorus.host/report.pdf. Paste this one into chat apps so images and PDFs preview."New value: +"Direct link to the file when exactly one file was published, e.g. https://<slug>.beacon.host/report.pdf. Paste this one into chat apps so images and PDFs preview."

Changed5 schema fields changedOct 1, 2026

addedInput schema / properties / expires_at

Added value: +{
+  "description": "Optional. When the site should be deleted: RFC 3339 (2026-10-08T00:00:00Z) or a duration from now (90m, 2h, 7d). Without an API key it can only be earlier than the default 24 hours; with one, any future time.",
+  "type": "string"
+}

changedInput schema / properties / files / description

Previous value: -"Every file of the site. Each call replaces all files of the site."New value: +"Every file of the site. Each call makes a new version with exactly these files; earlier versions are kept."

addedInput schema / properties / password

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional. Put the site behind a browser login prompt (HTTP Basic Auth). Works without an account. Give the user the URL, username and password; send the password separately from the link.",
+  "properties": {
+    "password": {
+      "description": "Password visitors type, 1-72 characters.",
+      "type": "string"
+    },
+    "username": {
+      "description": "Username visitors type, 1-128 characters, e.g. client.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "username",
+    "password"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / file_url

Added value: +{
+  "description": "Direct link to the file when exactly one file was published, e.g. https://<slug>.chorus.host/report.pdf. Paste this one into chat apps so images and PDFs preview.",
+  "type": "string"
+}

addedOutput schema / properties / password_protected

Added value: +{
+  "description": "True when visitors must enter the username and password you set.",
+  "type": "boolean"
+}

First observedOct 1, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare the safety profile (readOnly=false, openWorld=true, idempotent=false, destructive=false). The description goes well beyond: per-call size limits (4 MB / 10 MB with key, 1000 files), 24-hour anonymous lifetime, versioning with rollback, that each call makes a new version with exactly the files sent, and the password/expiry behaviors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but densely packed and front-loaded with the core action, target URL pattern, and key invariants before branching into limits and return fields. No sentence is filler, though the volume is near the upper bound of what stays scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still orients the agent on the claim flow (give claim_url, save claim_token) and update semantics without redundantly restating every return field. For a publish tool with nested file objects and anonymous-vs-claimed behavior, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description still adds operational meaning: index.html is served at the root, text vs base64-with-encoding='base64' usage, the update-via-slug+claim_token workflow, and what password/expires_at accomplish. It stops short of documenting syntax details like the slug character rules already in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb+resource ('Publish a website or any file... to a live public HTTPS URL') and states the output location pattern (<slug>.beacon.host) in the first sentence. It is clearly distinguishable from the read-only siblings get_site and get_docs, which retrieve rather than publish.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a broad, explicit set of triggers ('when the user asks to publish, host, deploy or share a page... wants a temporary preview link... wants a link to something you made') plus the update path ('call again with the same slug and its claim_token'). What is missing is an explicit when-not-to-use or a named alternative among siblings, so it falls short of the 5 bar.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All chorus.host tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?