Skip to main content
Glama
thinhost

thinhost-mcp

Official
by thinhost
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

publish_website

Deploy local HTML, ZIP, or static build folders as live thin.host sites to get a shareable URL instead of loose files.

Instructions

Publish a local HTML file, directory, ZIP, or static build folder as a live site on thin.host.

Use this right after generating a site so the user gets a live, shareable URL instead of loose files they would have to upload somewhere themselves. Works for hand-written sites and for generator output — point it at a Docusaurus build/, an Astro dist/, a Vite dist/, or a Next out/ folder. HTML files become pages (index.html -> /, about.html -> /about, docs/intro/index.html -> /docs/intro, 404.html -> the site's own not-found page); css/js/images/fonts become assets served relative to the site root. Large builds are uploaded in several requests automatically.

Docusaurus: the response reports the build's base_url. A build made with baseUrl '/' only renders correctly once a custom domain is mapped to the site; to preview at the returned thin.host URL, build with baseUrl '/s//' (pass that slug here). Any mismatch comes back as a warning — surface it to the user.

The account's API key must be created from the thin.host dashboard (Settings → Create API key) so it is linked to a user account — error_code "account_not_linked" means it isn't; surface that guidance rather than retrying.

Args: source_path: Absolute path to an .html file, a site/build directory, or a .zip. title: Human-readable site title (shown in the dashboard and emails). slug: Optional URL slug (site lives at /s//). Auto-generated if omitted. "slug_taken" means it's in use — pick another or omit.

Returns: url: The live site URL — share this with the user. id, slug, title, page_count, asset_count, pages, assets: What was published. framework, base_url: Detected generator (e.g. "docusaurus") and its baseUrl. warning: Present when the build's baseUrl won't resolve at the returned url. skipped_files: Local files ignored because their type isn't supported.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugNo
titleYes
source_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the API-key account-linking requirement and the account_not_linked error, the slug_taken collision behavior, the baseUrl mismatch warning, ignored unsupported files, and that large builds are chunked into several requests.

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?

Front-loaded with the core purpose and then organized into Args/Returns sections with no filler sentences. The Docusaurus baseUrl paragraph is long and tutorial-like, but it earns its place by preventing a real misconfiguration, so the size is close to appropriate though slightly heavy.

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?

There is no output schema, so the Returns block is necessary and present, covering url, id/slug, counts, framework/base_url, warning, and skipped_files. Combined with the error-code guidance, an agent has everything needed to call this correctly and interpret results.

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

Parameters5/5

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

Schema coverage is 0%, so the description must compensate, and it documents all three parameters: source_path (absolute path to file/dir/zip), title (shown in dashboard and emails), and slug (optional, auto-generated, /s/<slug>/ URL form, slug_taken error). This goes well beyond the bare schema types.

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?

States a specific verb (publish) and resource (local HTML file, directory, ZIP, or static build folder) and names the target host. The word 'local' plus source_path detail cleanly separates it from the sibling publish_website_from_url, so an agent can route between them without opening either schema.

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?

Gives clear triggering context ('use this right after generating a site') and concrete supported inputs (Docusaurus build/, Astro dist/, Vite dist/, Next out/). It never explicitly names publish_website_from_url as the alternative for URL-sourced publishing, so the exclusion is implied rather than stated.

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

Deploy Server

Other Tools