Server Details
Instant web publishing for AI agents. POST HTML, get a live URL. No account needed.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
4 toolsdelete_websiteTry in Inspector
Permanently delete a published website. The site will be immediately inaccessible. Requires authentication via edit_key or api_key, and requires confirm: true as a safety mechanism to prevent accidental deletion. Use this when a user explicitly asks you to remove or delete a site. IMPORTANT: Always confirm with the user before calling this tool — deletion cannot be undone.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The slug of the site to delete (e.g. "hello-world-k3m"). | |
| api_key | No | The user's API key (e.g. "yt_abc123..."). | |
| confirm | Yes | Must be set to true to confirm deletion. This is a safety mechanism — the tool will refuse to delete without explicit confirmation. | |
| edit_key | No | The edit key for this site (e.g. "ek_9c4d2e7f..."). |
get_website_statusTry in Inspector
Get information about a published website including its title, view count, size, expiry date, and whether it has been claimed. No authentication required — this is public information. Use this to check if a site is still live, see how many views it has gotten, or check when it expires.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The slug of the site to check (e.g. "hello-world-k3m"). |
publish_websiteTry in Inspector
Publish HTML content to a live URL instantly. No account or API key required. Returns a public URL that anyone can visit. Sites expire after 24 hours unless the owner claims them. Use this when a user asks you to build, create, or deploy a website, landing page, invitation, portfolio, report, or any HTML content they want to share as a link. Supports bundled assets (CSS, JS, images) and multi-page sites (include additional .html files in assets, accessible at /{slug}/{pagename}). IMPORTANT: After publishing, always share the live URL and the claim URL with the user. The claim URL lets them take permanent ownership of the site. Store the edit_key from the response silently — do not show it to the user — you will need it if they ask you to make changes to the site later. If you lose the edit_key, ask the user to claim the site first (via the claim URL in the page footer), then provide you with their API key from the dashboard — you can use that instead.
| Name | Required | Description | Default |
|---|---|---|---|
| html | Yes | Complete HTML document to publish. Must be a valid, self-contained page. Inline CSS and JS are supported. External resources (images, fonts, scripts) must use absolute URLs OR be included in the assets field with relative references (e.g. href="./style.css" or src="./logo.png"). Maximum total size including assets: 5.0MB (free tier) or 10 MB (Pro/Business). | |
| title | No | Human-readable title for the published page. Used in social sharing previews and the claim page. Optional. | |
| assets | No | Optional map of filename to content for bundled assets. Keys are filenames (e.g. "style.css", "logo.png", "app.js"). Values are either plain text strings (for CSS, JS, SVG, HTML) or data URIs for binary files (e.g. "data:image/png;base64,iVBOR..."). Reference these in your HTML with relative paths like ./style.css or ./logo.png. For multi-page sites, include additional .html files (e.g. "about.html") which become accessible at /{slug}/about. Limits: 10 assets (free) or 50 assets (Pro/Business), 5 MB max per individual asset, but total site size (HTML + all assets) must be under 5.0MB (free) or 10 MB (Pro/Business). |
update_websiteTry in Inspector
Update an existing published website with new HTML content. Requires authentication via edit_key (from the original publish response) or api_key (from the user's dashboard after claiming the site). The html field replaces the entire page — this is a full replacement, not a patch. You can also update assets. Use this when a user asks you to modify, edit, or change a site you previously published. IMPORTANT: You must provide either edit_key or api_key for authentication.
| Name | Required | Description | Default |
|---|---|---|---|
| html | Yes | Complete HTML document to replace the existing page with. Must be a valid, self-contained page. This replaces the entire page content. | |
| slug | Yes | The slug of the site to update (e.g. "hello-world-k3m"). | |
| title | No | Optional new title for the page. | |
| assets | No | Optional map of filename to content. If provided, replaces ALL existing assets. Omit to keep existing assets unchanged. | |
| api_key | No | The user's API key from their dashboard (e.g. "yt_abc123..."). Use this if the user has claimed the site and provided their API key. | |
| edit_key | No | The edit key returned when the site was originally published (e.g. "ek_9c4d2e7f..."). Use this if you still have it from the publish response. |
To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:
The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!