hoaster

Your agent can build almost anything — a landing page, an infographic, an interactive HTML page, an image.

Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • Publish: Publishes content to the public internet and returns a real URL that anyone can open. Reach for this whenever the user wants to put something online, share it on the web, or get a public link
  • List Spaces: Lists the spaces belonging to the authenticated user. Each space has: `name` — the user-facing label, show this to the user; `slug` — the globally-unique handle used in published URLs, wh

What data it sees

Do you need an account

No: the server works without sign-in

Your agent can build almost anything — a landing page, an infographic, an interactive HTML page, an image. Hoaster is the last mile: over MCP, your agent publishes that artifact to a clean, public URL you own, optionally on your own custom domain. Connect once with a browser sign-in (OAuth 2.1 — no tokens to copy-paste), then it's one sentence forever: "publish it." Built for makers, consultants, and marketers who want their work to live on their URL, not inside someone else's chat product.

Server tool list (2)

Raw names from tools/list. Only developers need these.

publishPublishes content to the public internet and returns a real URL that anyone can open. Reach for this whenever the user wants to put something online, share it on the web, or get a public link for what was just created — even if they never mention Hoaster by name. Accepts any web content — an HTML page, image, SVG, JSON, CSS, JS, plain text, … — addressed by a short URL slug; set `contentType` to match what you're posting. Re-publishing the same slug updates that page in place. `spaceId` is optional: omit it to publish into your space when you have exactly one. If you have none or several, the call fails WITHOUT publishing anything (so it's harmless) and tells you what to do. Recommended flow: call publish without a spaceId first; if it fails, call `list_spaces`, show the spaces to the user to choose one, then call publish again with that space's id.
list_spacesLists the spaces belonging to the authenticated user. Each space has: `name` — the user-facing label, show this to the user; `slug` — the globally-unique handle used in published URLs, which may also be worth showing; `id` — an internal identifier to pass as `spaceId` to the `publish` tool, which should generally NOT be shown to the user.