just-publish
Server Details
Publish a static website (HTML, CSS, JS, images) to a live public URL straight from chat.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.7/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of ambiguity between tools.
With a single tool, naming consistency is trivially perfect.
A single tool covering both creation and update is reasonable for a focused static site publishing server, keeping the surface minimal.
The tool covers deploy and update but lacks obvious lifecycle operations like listing or deleting sites, which may cause agent dead ends.
Available Tools
1 tooldeployAInspect
Publish a static site (HTML, CSS, JS, images) to a public URL. First call: omit site_id and edit_token — you'll get back a URL, site_id, and edit_token. Save the edit_token if the user wants to update the same site later. Subsequent calls: pass site_id + edit_token to update the same site in place.
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | Email to associate with the site. Captured unverified at first deploy; verification only required later for custom domains and recovery. | ||
| files | Yes | Files to publish. Must include an index.html at the root. | |
| site_id | No | Existing site id to update. Omit to create a new site. | |
| edit_token | No | Edit token returned at create time. Required to update. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) are present. The description adds context about the two-step flow, token management, email capture unverified, and that verification is only needed for custom domains. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, no wasted words. The action is stated first, then the two call patterns, then the token-saving advice. Very efficient and structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite no output schema, the description mentions the return values (URL, site_id, edit_token). It covers the workflow, prerequisites, and token lifecycle. The tool is simple and the description is complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, baseline 3. The description adds value by explaining the roles of site_id and edit_token (first vs subsequent call) and the email's purpose (unverified, for custom domains later). This goes beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's action: 'Publish a static site (HTML, CSS, JS, images) to a public URL.' It specifies the resource and the verb, and explains the two-step creation/update flow. No sibling tools, but the purpose is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly distinguishes between first call (omit site_id and edit_token) and subsequent calls (pass both to update), and advises saving the edit_token for later updates. This is clear usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
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!