Skip to main content
Glama

Server Details

Publish HTML, Markdown, and multi-file sites as shareable URLs instantly via MCP.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation5/5

Each tool serves a clear, distinct function: get retrieves metadata/content, publish creates single-page artifacts, publish_site creates multi-file sites from ZIPs, and versions lists history. There is no overlap that would cause an agent to pick the wrong tool.

Naming Consistency2/5

The naming pattern is inconsistent. 'get' and 'publish' are bare verbs, 'publish_site' follows a verb_noun pattern with underscore, and 'versions' is a noun. A more consistent scheme would be 'get_artifact', 'publish_artifact', 'publish_site', 'list_versions'.

Tool Count5/5

With only 4 tools, the server is lean and well-scoped for the artifact publishing domain. Each tool covers a distinct core operation without unnecessary bloat.

Completeness2/5

The surface lacks essential operations for artifact lifecycle management. There is no way to list all artifacts or delete/update an artifact, which are common expectations. The 'versions' tool requires an artifact ID, but without a list operation, discoverability is a significant gap.

Available Tools

4 tools
getAInspect

Get artifact metadata. Set include_content to true to also return the full HTML content.

Inputs: id (required), include_content.

publishAInspect

Publish HTML or Markdown content as a shareable URL. Pass content byte-for-byte from the source — do not retype, reformat, minify, summarize, or 'clean up' the input; even one stray character can break inline scripts on the published page. If the content is too large to copy verbatim through the model, use the REST endpoint POST /v1/artifacts (or /v1/artifacts/upload for ZIPs) instead. For Markdown, optionally include images as base64-encoded data.

Inputs: format (required), content (required), title, images, +1 more.

publish_siteAInspect

Publish a multi-file HTML site from a base64-encoded ZIP file. The ZIP must contain an index.html at its root. For sites larger than ~10MB — or whenever you have the file on disk — prefer the REST API /v1/artifacts/upload endpoint to avoid base64 overhead and to guarantee byte-faithful upload.

Inputs: zip_base64 (required), title, visibility.

versionsBInspect

List version history of an artifact

Inputs: id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources